bridge on fonera 2.0g

[marco]

In the fonera 2.0g there isn't the bridge mode (ethernet). Can you add this important feature? It is in the fonera classic (with freewlan addon) and in the fonera 2.0n...

[matthijs]

Due to the different hardware, the bridge mode as implemented for 2.0n cannot be directly converted to the 2.0g. It's not impossible, but it will take some time. It's definately on our radar.

[matthijs]

(In [1820]) fonbase: Unify the config.sh scripts for 2.0g and 2.0n.

There is no a single script for both targets, instead of two highly similar but slightly different scripts. For 2.0n, this doesn't change much (e.g., the script still does more or less the same). For 2.0g, the changes are bigger. Mostly the bridge-mode related changes are available to 2.0g now, as well as some other minor changes (but this does not actually make bridge mode work on 2.0g yet).

References: #836

[matthijs]

(In [1822]) image: Remove uci-defaults/network for 2.0g.

This file sets a few defaults in /etc/network/config and probably comes from the OpenWRT repository. However, /lib/fon/config.sh is perfectly capable of setting all these values and because /etc/init.d/configure (which runs config.sh) is ran before /etc/init.d/uci-defaults (which calls the removed file), the removed file overwrites settings set by config.sh.

This is not a problem when using DHCP mode, but for other modes (in particular bridge mode), this makes that the 2.0g needs an extra reboot after a firmware upgrade.

2.0n does not seem to have a similar file.

References: #836

[matthijs]

(In [1828]) fonbase/ra_esw: Move 2.0n hardware switch config to fon config.sh script.

This mostly reverts r1555, r1556 and r1570, replaces the esw init script with a generic switch init script that calls config.sh and reimplements the switch configuration stuff in config.sh. The new implementation is slightly more explicit, in that it actuall moves the WAN port out of the WAN vlan instead of just adding it to the LAN vlan.

Putting this stuff in one place makes it easier to maintain and also paves the way for using software bridging instead of hardware briding on 2.0g.

Whenever ConfigWan? is called, ConfigFON is called right before (except for in the wizard, where it might be called a few steps before, but I don't think that should matter), so moving the stuff from ConfigWan? to ConfigFON shouldn't matter.

References: #836

[matthijs]

(In [1829]) fonbase: Use software bridging for 2.0g.

This commit makes /lib/fon/config.sh use software bridging for 2.0g (or rather for all devices but 2.0n), which does not (currently) support hardware bridging.

Since the networking configuration scripts have been unified between 2.0n and 2.0g, this is the only real change needed to support bridge mode on 2.0g.

Closes: #836