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 its default settings with router mode and DHCP server. However, I'll need to be using bridge mode for our permanent installations. When I change to bridge mode, I lose all connectivity and cannot reach the LB1120 until I factory reset it. I can see that the Linksys router is getting an AT&T IP address so bridge mode is functioning in some manner.
I'm sure it's something obvious but I'm at a loss. Any ideas?
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
135 Replies
Bridge mode makes the device transparent, it acts like a piece of wire. Is your router DHCP, DNS are enabled?
Thanks for the reply VE6CGX. Yes, DHCP and DNS enabled. Linksys works fine with standard cable modem.
Netgear support also responded and I'll be trying some of their troubleshooting tomorrow when I have access to my ethernet adapter for my laptop and can bypass the Linksys.
Thanks again.
Hi bseright - I have the same problem it seems. When connecting in bridge mode to a laptop, it works fine, but when I connect it to any router, I do get an IP but no traffic. Would love to hear from you when you get this resolved with the Netgear folks...
Thanks
Peter
This is happening because your WISP is not providing you with your own public IP. You are using a private IP address, which your provider does some NAT to a public address which is shared by others, which you cannot bridge. You will need to contact your cellular carrier, request a public IP. Verizon charges $500 for this, not sure what AT&T charges.
In bridge mode the LB1120 is setting the LAN interface to a /32 subnet, this totally confuses the router, clearly a firmware bug in the Netgear.
Others are seeing the same thing, check this over at Ubiquiti forums:
It works in router mode because the LAN interface is set to a subnet that computes, like /24, etc... Frustraring becuse I bought the LB1110 for bridge mode, and it does not work in bridge mode with any of the routers I have tried.
Thank you - this is helpful.
Interesting enough, when I brought the LB1120 to another location that has an EdgeRouter X SFP running v1.9.0 it works like a charm - no scripts needed. The Edgerouter Pro I'm running at v1.9.1.1...
Hope to see a firmware update from either Netgear or Ubiquiti on this...
I have the LB1120 and tried it on my Edgerouter (in bridge mode) with 1.9.1.1 and it did not work... Crazy, but I will try it again, maybe it is a power sequencing thing, or I forgot to reboot the modem.. I also have an LB1121 (PoE) and plan to test that on my setup.
LB1120 been running a few weeks in router mode, very solid, great speeds, but I need bridge mode to do what I want to do with it.
Hope Netgear reads this forum and takes a look at their firmware.
- Just to be clear, its not working on my edgerouter pro with 1.9.1.1 but it is on my edgerouter X with 1.9.0...
Thanks!
I will down grade my Edgerouter X and try it if I have time this weekend.
Also, not working with the Ubiquiti Security Gateway, or the Cisco/TP-Link routers I had laying around. Does work fine in bridge mode on my Mac though.
I too am having the same problem setting up the LB1120 in bridge mode. While connecting a laptop everything works perfectly. When connected to my Airport Extreme I get all sorts of issues. My Airport Extreme seems to get an IP, but has absolutely no connectivity to the outside world.
Following up...
1. Downgraded Edgerouter, did not work in bridge mode.
2. Connect direct to Mac, works fine in bridge mode.
3. Tried every combo of router I own, nothing works when the Netgear LTE is in bridge mode.
I'm having the same exact issue with an ERX v1.9.0
Anyone know of a router that will work with this out of the box? Or an alternative to the LB1120 that is more compatible with devices when in bridge mode?
I have this problem as well.
Has anyone from NETGEAR responded to this issue?
To put it succinctly, this seems like a bug in the LTE Modem. In Bridge mode, one would expect the IP address AND netmask handed out by the ISP to be passed to the connected device rather than the often unusable netmask of 255.255.255.255.
It seems like a relatively simple fix to pass along the netmask provided by the ISP DHCP server and it is the right thing to do in Bridge mode.
Can someone from NETGEAR confirm that this issue has been reported to engineering and provide any status update?
Thanks
I have sent in emails about it, got nothing, there is virtually ZERO support from Netgear.
Pretty sure it is in the turd of a modem design that came when they acquired Sierra's AirCard stuff.
If anyone knows of a good LTE modem design that works in bridge mode please let the group know, I don't care if they cost 2-3x what this NetGear modem cost, as long as it works.
I'm in the same boat. Just set mine up yesterday behind a pfSense firewall. Works fine as a router, no connectivity in bridge mode. Had to reset the modem and set DHCP to hand out just 2 addresses and set my router's IP as a DMZ host.
This is pretty basic functionality one would expect to work right out of the box.
Hello,
I'm on the same boat. Have a LB1120 with a Ting GSM card. For some reason it keeps only wanting to connect to t-mobile APN which is the APN that came up once I started it. I tried to add the 'wholesale' apn and it starts connecting and then disconnects. So I stayed with the t-mobile APN which connects and I have data service but when placed in bridge mode, it keeps assigning a 192.168.5.100 address with the gateway at 192.168.5.2. I tried with a netgear FSV336 router and detects internet service on the WAN interface, but doesn't do any routing to the LAN.
Contacted Ting and they found interesting the private IP assigned. They asked me to reset the modem to defaults to see if it would load the default APN from the SIM as Ting claims the APN for 'wholesale' is supposed to be for phones and such, and they don't have APN for hotspots. Not sure what to do if everything fails.
Just wanted to share my experience and see if there are any new developments. I will certanly try the DMZ option to see if the router likes it.
Below is a snapshot from the logs proving that in bridge mode we don't get the subnet on the dhcp request and a hint on how to adjust for it on the router side (update dhcpd.conf with a subnet for that network adapter). What we really need is Netgear to provide a firmware update that fixes the problem and make sure the dhcp response includes a subnet.
Dec 31 19:01:25 lakehousekok dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared
Dec 31 19:01:25 lakehousekok dhcpd:
Dec 31 19:01:25 lakehousekok dhcpd: No subnet declaration for eth0 (10.130.xx.214).
Dec 31 19:01:25 lakehousekok dhcpd: ** Ignoring requests on eth0. If this is not what
Dec 31 19:01:25 lakehousekok dhcpd: you want, please write a subnet declaration
Dec 31 19:01:25 lakehousekok dhcpd: in your dhcpd.conf file for the network segment
Dec 31 19:01:25 lakehousekok dhcpd: to which interface eth0 is attached. **I've opened a case with Netgear on this. I'll keep y'all up to date.
I opened a case yesterday, two cases actually. I had a terrible first attempt and complained to Netgear. I was promised that the second case would be escalated to an engineer.
During the first case, the rep denied there was any problem at all and refused to even look at this thread. When she asked me to do MAC address cloning I knew it was time to pull the rip cord.
I will be on them like white on rice today.....
Thanks for posting this very useful information.
I got a chuckle reading your post as my SSID is "lakehouse" on the wap I was using for this project.
vronp - LOL - I'm guessing your lakehouse only has horrible DSL or no internet service at all... Hence we need to deal with these things...
I also purchased the NETGEAR LB1120. I've had the same experience as everyone else: when using a laptop, DHCP in bridge mode works fine; when I connect the device to my pfSense router, it does not function. As many have suggested, it appears that the problem is with the DHCP passthrough such that the interface in pfSense gets a netmask of 255.255.255.255. The other values appear fine.
I struggled a bit trying to get pfSense to override the DHCP configuration and use 255.255.255.0 instead. There might be a way to do this, but I didn't find it. So, I changed the interface configuration to static IPv4 and created a standalone gateway object. I pasted the issued IP and gateway values, and it started working properly. I was able to switch from my existing WAN's gateway as default to the one using the LB1120. I got transfer speeds that are acceptable for a failover solution.So, it seems that we're all waiting on a fix from NETGEAR for the DHCP bug. For what it's worth, mine shipped with firmware version M18Q2_v12.09.163431.Here are some details that are unrelated to the problem that might be interesting nevertheless. I'm using a SIM provided by Ting and it uses the T-Mobile carrier in my area. On first powering up the LB1120, it did a scan of the mobile networks and (I assume) created a default APN for the T-Mobile network that it discovered as compatible. I had to delete that and create a new APN for Ting using the string "wholesale" as specified in Ting's documentation for non-phone devices. Until I deleted the automatically created (again, my assumption) APN, the LB1120 would get confused about which one to use. It seems to work fine now from a cold start every time.Something else worth mentioning (in case somebody else has the expectation I did) is that on the T-Mobile network my LB1120 is assigned something like 21.228.0.149. That is not in an allocation of IPv4 given to T-Mobile, and it's not accessible from the public internet. I had hoped that my WAN failover solution using a 4G LTE modem would allow me to connect to my office network during a primary WAN failure using a VPN client. It doesn't look like that's an option. Inside T-Mobile's network, my traffic emerges onto the public internet using an address from 172.32.0.0/11 (which they are the allocation recipient). I assume they're doing big iron NATing for all their wireless customers.Lastly, another tip. When troubleshooting what was going wrong, I found it helpful to put a dumb Ethernet hub between my pfSense router and the LB1120. Using that, I could tap into the frames with another host and see what was going on. Using an Ethernet switch with the port mirroring feature would also have worked, but I didn't have one on hand. When sniffing, it was apparent that packets weren't ever actually leaving the pfSense box.
