Wizard: allow meshing on ethernet ports

[andrenarchy]

Several installations use >1 router which are connected via ethernet (e.g., MABB-supported "Kleinstandorte"). Therefore, we should allow meshing also on at least one ethernet port.

I propose the following solution:

• we add one field to the wizard where one IP can be provided in for ethernet meshing. If this is not wanted, the field can be left empty.
• if an IP was provided in the wizard, a new interface lanmesh is added with this IP and the same ifname as lan. This simply adds another IP address to these ports (see here) and OLSR can be configured on lanmesh (with eth mode).

Thus, DHCP still works on lan and the user can still reach the router easily without wifi.

What do you think?

[cholin]

This is also important for these Überlassungserklärungs setups because they normally connect through a Nanostation with the backbone and extend the network locally with a TP-Link WDR3600.

[andrenarchy]

See also freifunk-berlin/nipap-wizard#18

[booo]

Can someone summarize the ideas we had so far?

[cholin]

I would favor an additional checkbox for mesh on LAN during ip configuration. If the users selects the checkbox he/she can enter an ip address. Technically I would bridge all ethernet ports except wan, configure an ip and add it to olsr. This has the drawback that an unexperienced user can lock him/herself out because of missing dhcp on lan. But with ipv6 and dhcp on the ap he/she should be able to get access again. This solution is as well not as complex as dividing lan ports into dhcp and mesh or stuff like that...

[andrenarchy]

I'm happy with the solution proposed by @cholin.