Posted: Sun Feb 12, 2023 20:24 Post subject: Bridging config does not survive reboot, R7800 Build 51617
Netgear R7800 Build 51617
First only the Interfaces/wlan changes would be saved after a reboot, the eth1.x changes would be missing altogether. Tried adding the bridges in swconfig which resulted in all the interfaces appearing after a reboot but the assignments would be jumbled, as per photo. I had even tried to "Assign to Bridge" in the order the bridge numbers appeared in the drop-down menu.
How can I configure my bridging tables so that they survive a reboot?
Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Sun Feb 12, 2023 21:43 Post subject:
What do you mean by "adding the bridge in swconfig"? I was not aware that swconfig can be used for configuring bridges. Instead you should probably use brctl in your startup script.
I could have worded that better. These are the startup commands:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "4 6"
swconfig dev switch0 vlan 3 set ports "1 6t"
swconfig dev switch0 vlan 4 set ports "2 6t"
swconfig dev switch0 vlan 5 set ports "3 6t"
swconfig dev switch0 set apply
vconfig add eth1 3
vconfig add eth1 4
vconfig add eth1 5
brctl addif br1 eth1.3
brctl addif br1 eth1.4
brctl addif br1 eth1.5
ifconfig eth1.3 up
ifconfig eth1.4 up
ifconfig eth1.5 up
And as mentioned by @Per Yngve Berg, you need to fill in details at 'Network Configuration' of br1, br2 and br3 in 'Networking' tab. Followed by DHCP for each bridge. if not already done so.
Note: Remember to Save then Apply Settings at each step.
If ALL interfaces appear under 'Current Bridging Table' for each corresponding bridge correctly, you should now have it working after a reboot. _________________ Life is a journey; travel alone makes it less enjoyable and lonely.
Joined: 16 Nov 2015 Posts: 6408 Location: UK, London, just across the river..
Posted: Mon Feb 13, 2023 15:05 Post subject:
bridge stuff must be added at last as those interfaces must be created first and up and runnung..
so yes brctl commands are the last and must contain subnet and masck to be precise
but if you want to create those via GUI you wont need those lines in the start up script...
i guess it wont hurt if you have those in both ways...but just to mention you don't need those
as assign interface to br and dhcpd you can make via GUI...
so those lines first those are wrong (as you add those by mistake to the same br1), second you don't need them:
brctl addif br1 eth1.3
brctl addif br1 eth1.4
brctl addif br1 eth1.5
and bridge stuff must be after those lines in general...
ifconfig eth1.3 up
ifconfig eth1.4 up
ifconfig eth1.5 up _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
@DWCruiser: Geez. Rookie mistake. As you said, it does work fine after the changes. Nice catch and thanks!
You and @Per Yngve Berg refer to vlanx and not eth1.x in newer builds, but I only have the eth.1x option when configuring bridges in build 51716. @kernel-panic69 mentioned in a 2021 post that it could be caused by a hardware issue or a config issue. Is there anything I can do to change it?
@Alozaros: Thanks! Thinking back, I first had an issue with eth1.x not showing up in the Interface section of the Current Bridging Table so added brctl to the Startup Commands hoping that would fix it. It did, except that I missed changing the numbers for bridges 2 & 3. So I removed the brctl form Startup Commands and had the same issue. When I put them back all the interfaces appeared where they should be. Now, given I need to add brctl and don't have the vlanx option in Networking/Bridging, do you think there may be a hardware issue?
Joined: 16 Nov 2015 Posts: 6408 Location: UK, London, just across the river..
Posted: Mon Feb 13, 2023 17:43 Post subject:
I just did the check on my R7800 with 4 vlans running 51679 and those show as eth1.3 and ect..not as vlan 3 or similar...but in fact there is a vlan 3 under the network page as well br3 where this vlan 3 belongs (refer to my config) thing is you live the vinas to default and than once those are added to a bridge they go on it..if you unbridge the vlan it should stay alone no bridge assignment needed..but..."with vilan on br you have a better control over it"...(eibgrad) _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
R7800 is a two-armed router meaning there are two dedicated cpu ports, for LAN and WAN Ethernet.
Older routers have only one cpu port requiring use of vlan to utilize both LAN and WAN over the port.
Joined: 16 Nov 2015 Posts: 6408 Location: UK, London, just across the river..
Posted: Mon Feb 13, 2023 19:43 Post subject:
Per Yngve Berg wrote:
vconfig set_name_type VLAN_PLUS_VID_NO_PAD
This is the statement that give you VLAN3 instead of eth1.3
so, this line changes everything..
vconfig set_name_type VLAN_PLUS_VID_NO_PAD
and its the new must...weird couse my config is ok...running "the old way"
In my setup, in order to obtain some balance WAN and LAN are already moved each on different CPU with another line)
Does the CPU gets a better utilization and speed over 2 ports...??
Any other functional difference between both ways ?
Not clear if R7000 needs this line too or in its case its already set...?
vconfig set_name_type VLAN_PLUS_VID_NO_PAD
(on my R7000 i never used vlan CLI way, but the GUI way only)
Thank for the insight... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913