Define a dedicated WAN port for devices that do not have one

[kls0e]

There are some boards like the AVM Fritzbox 7530 that perform great as a tunneldigger uplink, but do not offer a dedicated WAN ethernet port (only LAN 1-4 for example).
At the moment the Wizard does not create a WAN port at all if ran on these boards.

For the tunneldigger uplink usecase I suggest defining LAN1 as WAN on these routers and show a hint in the wizard during setup.

We have a similar situation with routers that sport only one eth port. Currently, it will always be configured as Freifunk DHCP, even if the user decides to use the device as a tunneldigger uplink node.

Other affected devices include TP-Link CPE210/510 V2 & V3, TL-MR3020, Comfast CF-E130N v2, ... – essentially all boards that either lack a labelled WAN port or have only one eth port at all.

[PolynomialDivision]

There is some issue that sometimes the port order is changed. We could make some script that always makes a vlan on port 1 that is used as wan?

[kls0e]

There is some issue that sometimes the port order is changed.

Are you referring to the internal switch port numbering that OpenWrt utilizes vs the numbers on the routers' case?

[PolynomialDivision]

Are you referring to the internal switch port numbering that OpenWrt utilizes vs the numbers on the routers' case?

Yep. ;)

[kls0e]

I will gladly gather the individual mappings for the affected boards, but I don't know how to patch the wizard.

[PolynomialDivision]

We just have to add a vlan untagged on port 1 and add it to wan. Further, we have to remove the lan vlan from port 1.

[Akira25]

Perry wrote in #92:

I am not confortable with automatically setting a LAN port as WAN for routers which have a DSL modem in them. I would prefer to have manual intervention by the user to do this. This will keep the settings inline with openwrt and it will also prevent the user from making an unexpected mistake.

Possibly it would be useful to create a menu entry in the Freifunk menu which handles the WAN port, with options such as using LAN-N. Something similar to the new "Wireless Mesh Settings" page.

I agree on that position, as keeping compability with openwrt is one of our main goals on falter.

[Akira25]

This issue was partly solved via #212. The new default scripts will configure a WAN interface also on devices, that don't have one. Thus you can connect a port to the wan-interface easily on the switch. The ideas for more easy configuration gets addressed in the new wizard.