jsmiddleton4
Very Senior Member
I know, not exactly a router issue. Don't know where to ask and it ties in with my mini-rant about 2.5g capable routers only having one 2.5gb port.
I've switched to the 2.5gb port being a LAN port. I have a new NUC with 2-2.5gb ports. I've connected one to the router's 2.5gb port. The other to a Netgear 1gbs switch. I do not have any 2.5gb clients beyond this one NUC.
I've configured the 2 ports in bridge mode.
I have it working. I'm on the NUC at the moment so obviously connected to the internet. I had trouble with clients connected to the switch that is connected to the bridged 2.5gb ports.
I have them working now but I'm not exactly sure why.
For the IPV4 settings for the network bridge I had to manually enter IPV4 IP, gateway and DNS. The bridged port can't actually see the DHCP server in the AX86U.
I was not able to see the NAS, printer, networked media device attached to the switch though.
After banging on it awhile thought to myself, well if the LAN bridged port requires manual config for IPV4, no idea why IPV6 works, I bet all down stream devices, those attached to the switch, need to be told the same thing. Added manual IP/DNS/Gateway information into the printer, NAS, etc., and bingo, all working and network is quite snappy.
Edit: One thing I've learned is do anything you want or need to do for the network before creating the bridge. Things like mapping drives, etc., after the bridge didn't work. Remove bridge, map drive, create bridge, mapped drives work perfectly.
Tried to install wireless drivers for my Canon printer after bridge in place. Didn't work. The bridged computer couldn't find the wireless device. Take bridge down, installed wireless driver for the printer without issue. Recreate bridge, printer connection just fine.
Whatever the extra layer of information Windows uses/needs to create the bridge makes it blind to other stuff.
Do all the other stuff before the bridge, make the bridge, everything hunky dory.....
I searched on the matter, Windows network bridge mode and attached clients, but didn't find anything beyond how to setup Windows multiple LANs into bridge mode.
Folks here know WAY more than I about these things. If anyone wanted to do the same to take advantage of the 2.5gb port they might want to know as well how to set this up.
2.5gb switches still too expensive. This was a nice middle ground.
I've switched to the 2.5gb port being a LAN port. I have a new NUC with 2-2.5gb ports. I've connected one to the router's 2.5gb port. The other to a Netgear 1gbs switch. I do not have any 2.5gb clients beyond this one NUC.
I've configured the 2 ports in bridge mode.
I have it working. I'm on the NUC at the moment so obviously connected to the internet. I had trouble with clients connected to the switch that is connected to the bridged 2.5gb ports.
I have them working now but I'm not exactly sure why.

For the IPV4 settings for the network bridge I had to manually enter IPV4 IP, gateway and DNS. The bridged port can't actually see the DHCP server in the AX86U.
I was not able to see the NAS, printer, networked media device attached to the switch though.
After banging on it awhile thought to myself, well if the LAN bridged port requires manual config for IPV4, no idea why IPV6 works, I bet all down stream devices, those attached to the switch, need to be told the same thing. Added manual IP/DNS/Gateway information into the printer, NAS, etc., and bingo, all working and network is quite snappy.
Edit: One thing I've learned is do anything you want or need to do for the network before creating the bridge. Things like mapping drives, etc., after the bridge didn't work. Remove bridge, map drive, create bridge, mapped drives work perfectly.
Tried to install wireless drivers for my Canon printer after bridge in place. Didn't work. The bridged computer couldn't find the wireless device. Take bridge down, installed wireless driver for the printer without issue. Recreate bridge, printer connection just fine.
Whatever the extra layer of information Windows uses/needs to create the bridge makes it blind to other stuff.
Do all the other stuff before the bridge, make the bridge, everything hunky dory.....
I searched on the matter, Windows network bridge mode and attached clients, but didn't find anything beyond how to setup Windows multiple LANs into bridge mode.
Folks here know WAY more than I about these things. If anyone wanted to do the same to take advantage of the 2.5gb port they might want to know as well how to set this up.
2.5gb switches still too expensive. This was a nice middle ground.
Last edited: