GitLab

Previously, when an interface (i.e. eth0) was configured as "lan" and "mesh",
it was added to the LAN bridge and, on top of the virtual "br-lan" interface,
the VLAN for the routing protocol was created (i.e. lan_12). This was wrong in
some cases, for example, when another interface was in the bridge but not meant
to be meshing. Now the VLANs are created on the interfaces actually configured
as "mesh".

[qmp-system] Fix /etc/config/mini_snmpd to ensure that br-lan and lan are not both configured, which makes the daemon not boot

[qmp-system] Fix /etc/config/mini_snmpd to ensure that br-lan and lan are not both configured, which makes the daemon not boot

 · Drop community_id and community_node_id and replace it with community_name, mesh_name, device_name and mesh_id when appropriate
 · Revamp qMp easy setup
 · Rename node to device to avoid confusions (node == physical/geographical location, device == router)

[qmp-system] RouterStation Pro is treated as any other device (no target-specific hook in the middle of the code)

Fixes #386

Fixes #387

Conflicts:
	packages/qmp-system/files/etc/uci-defaults/qmp_enable_opkg_feeds

[qmp-system] Add birth hook for routers with two Ethernet devices (e.g. eth0 and eth1) with switched roles (i.e. wan and lan, respectively)