NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
LB1120 Bridge Mode - No Connectivity
Hello, Trying out an LB1120 before installing across three locations as failover devices. Using AT&T and testing behind a consumer Linksys E2500 with default settings. The LB1120 works fine using...
A new firmware has been posted on the update servers that fixes the LB bridge mode issue. To update LB1120, LB1121 or LB2120 to latest Firmware log into the LB web ui and go to Settings àGeneral à Software and Reset once there select check for update and wait then simply follow onscreen instructions to update the Firmware. See below for example of how the LB2120 Firmware Info screen looks like after update. For other device just need to make sure that you are using App Version: NTG9X07C_12.09.05.27
Bridge mode working in pfSense without beta firmware!
The connectivity problem seems to concentrate on a /32 subnet being assigned from the LB1120, and I forgot pfSense has a way to use a user-supplied value in favor of a value by the DHCP server using the supersede modifier.
In pfSense, place a check in "Advanced Configuration" and then enter "supersede subnet-mask 255.255.255.0" in the Option modifiers field. This supersedes the LB1120's supplied subnet mask of 255.255.255.255 and uses 255.255.255.0 instead.
This creates a working bridge mode. This should work with anything that uses dhclient as well (Linux, FreeBSD, OpenBSD, etc).
While I love pfsense that is not what we use in production environments. Also, you state a subnet of /24 which is arbitrary and that value is dependant on the DHCP values and netmask supplied by your provider. You guessed and got lucky. (No offense but that is the exact attitude of Netgear.)
I didn't so much guess the subnet mask as much as I resized it so the gateway I was assigned was inside the subnet. Of course it'll vary depending on who your carrier is. But yeah, I don't expect this to be viable for everyone. Maybe it's possible to script it so it calcluates the right subnet mask when the interface comes up.
Still debating returning it because the fact I have to fiddle with it like this at all is silly.