LibreMesh interface-specific network configuration

If no interface-specific network configuration is present, the general network configuration section is used for all the interfaces.

For more information about the general LibreMesh config file options see The config file page.

For more examples and offline documentation check out /docs/lime-example on the router or lime-example file online.

Specific ethernet interface configuration

If we want to change the default behavior of just one network interface of the many that are present in a router, we can define a specific configuration.

Please make sure to check out how OpenWrt names the physical ports of your router model, for this read the router page accessible from OpenWrt table of hardware.

Ethernet specific options, multiple allowed
config net port5
	option linux_name 'eth1.5'
	list protocols 'wan'

In this case the eth1.5 interface will be used as WAN (so the DHCP client will be enabled).

config net

Do not put any "." in the section name (e.g. port5).

As linux_name, use the actual name of the interface as the system shows (check with ip link show).

Some of the available protocols require the relative package, for example lime-proto-wan, to be installed.

Network interface specific options

Available protocols: bmx6, bmx7, batadv, olsr, olsr6, olsr2, bgp, wan, lan, manual, static, babeld, apbb, client

Note that some of these protocols will require the relative lime-proto-... package being installed, otherwise the protocol entry will be ignored.

proto:vlan_number works too (something like bmx6:13 is supported). If VLAN is 0, no VLAN will be used.

VLAN type defaults to 802.1ad, but it can be set to 80.1q adding another option proto:vlan_number:8021q.

If you use manual do not specify other protocols, may result in an unpredictable behavior/configuration.

WAN autoconfiguration

If the LibreMesh package lime-hwd-openwrt-wan is installed and your node have two or more ethernet ports, LibreMesh might autoconfigure as WAN one of these network ethernet device.

In this case you will find a new specific configuration section like this one:

config net 'lm_hwd_openwrt_wan'
	option autogenerated 'true'
	...

If we want to change the behavior of this specific network interface and stop the automatic rewrite of its configuration, we must set the autogenerated option to false.

Ground routing configuration

For more information on ground routing concept, check out these resources.

Ground routing specific sections
config hwd_gr link1
	option net_dev 'eth0'
	option vlan '5'
	option switch_dev 'switch0'
	option switch_cpu_port '0'
	list switch_ports '4'
config hwd_gr
  • net_dev: Plain ethernet device on top of which 802.1q VLAN will be constructed.

  • vlan: VLAN ID to use for this ground routing link, use little one because cheap switch doesn’t supports big IDs, this will be used also as 802.1q VID.

  • switch_dev: These options regarding switch need to be set only if your ethernet device is connected to a switch chip. If the switch exists you can read its name (like switch0) in /etc/config/network file.

  • switch_cpu_port: Refer to switch port map of your device on OpenWrt ToH to know CPU port index.

  • switch_ports: List switch ports on which you want the VLAN being passed, refer to OpenWrt ToH for correspondence with physical ports.

One section for each ground routing link. With ground routing we mean setups having LibreMesh on a router which is connected via cable(s), eventually through a switch, to some wireless routers running the original firmware in WDS (transparent bridge) Ap/Sta mode. Likely you want to configure as many sections of ground routing with different VLAN numbers or different switch ports as many connected devices in WDS mode.

BGP configuration

Proto BGP specific sections (one section for each BGP peer)
config bgp_peer peer1
	option remoteIP '192.0.2.6'
	option remoteAS '65550'

config bgp_peer peer2
	option remoteIP '2001:db8::c001'
	option remoteAS '65549'

For documentation on BGP configuration see this thesis.

Specific wireless interface configuration