little inconsistences with special "0.0.0.0" for secondary bridges when pure L2 is needed #218
Description
I played today with the "0.0.0.0" special case for br1 to remove the secondary IP/L3 from them.
Two things i noted here:
0.0.0.0 - WITHOUT a Netmask - works as expected
0.0.0.0 - netmask 0.0.0.0 - works only on APs without WAN/NAT
Further more:
When the special case 0.0.0.0 is used, there is still in the admin-menu the option to select br1(x) for management. This makes no sense, when there is no active IP configured any longer - so it should be hidden for all bridges with the special case "L2".
When a netmask is defined in a L2-bridge AND the Router hosts a firewall/default-GW, then this will be no longer working, because of a (unneeded setted netmask) - so a missing help & better documentation for set them quickly. Result: the peer on the WAN-side is no longer reachable by ip4 and ip6 - and no entry in the routing table show that there is a "new" defaultgateway added, means: The actual scripts only check for 0.0.0.0 on the IP-Entry field and ignore the netmask-check (when is setted known or unknown)
One optical thing in der status overview when only set 0.0.0.0 and NO netmask is entered, then this is presented as br1: "0.0.0.0/NaN"
It can make more sense to hide the entire brX config line and add a checkbox: "L2 only" YES/NO, and when YES: hide the entire config line (or gray out) - and on status-Overview the L2-bridge should be shown as "L2" without any IPs, otherweise it looks like a default-gw ;-) - or, when the ip is set to 0.0.0.0 remove/empty any type of (pre) entered netmask and/or DHCP (disable it, when it was enabled before....)
This extra checkes/optimisations becomes helpful, when the device was previous L3-configured and not "NVRAM cleared" initialy. So there are more manually steps to take care of when switch the previous L3 "off".