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
I'm having this same issue with LB1111 (European PoE version) I picked up today and Edgerouter Pro. Any news on the firmware update?
- Still no news on availability
- Hi, just to say I'm having the exact same issue with a LB1110-100EUS 4G LTE (EU version) in bridge mode to the Unifi Security Gateway Router.
Looking forward to the firmware upgrade.......
Will post any solutions / info found here. Thanks for all the effort! Hi! Solved for me using a post earlier in this thread.
My setup is the LB1110 (european version) and the Unifi Security Gateway 3P (USG) and I too was unable to get connection in Bridge Mode.
This is what I did:-
1. Updated the UniFi Gateway to the very latest release, currently VS 4.3.49.5001150
2. Reset the NetGear LB1110 to its Default Settings
3. Connected the LB1110 (switched off) to the UniFI (switched on and connected to my LAN)
4. Switched on the LB1110
5. I now had the hoped for LTE/4G connection served to and from my LAN
6. Whoopee!
7. I then logged into the LB1110 and switched over to Bridge Mode without switching anything of or disconnecting anything (remember I had reset the NetGear to Default Settings)
7. Still working fine!
8. Phew!
9. I run my system 24/7/365 including a UPS and have not dared switching the whole lot off to see if it all starts up again OK, but it should do.
Hope this is of some use until the NetGear FirmWare update arrives.
Count me in for the bridge bug.
I just got this 2 days ago, have 25 more to return it.
Has somebody else get the new firmware ?
What alternatives are on the markjet to replace this ?
Thanks to all.
I have had a ticket open for over a month. There have been at least a dozen back-and-forth exchanges. They DO reconizes the problem. They claim to have a fix through firmware. For the past two weeks they have been asking me to check for an update through the device but no updates are found. I suspect there is fix via firmware out there but netgear support is probably not communicating very well within its own ranks which is causing unneeded delays.
- I believe they are in a testing phase of a fix and would hope to see a release fairly soon.
You'll have seen my solution just above yours on this third page - have you tried this method..... E X A C T L Y ?
Concerning alternatives, there are several, mainly from the marine environment (for yatchts and so forth). Simple internet search will flush them out. The trouble is they are really expensive compared to this product, here in the UK, they start at x3 the cost and rapidly go up above £700GBP. This is because they are designed for a scalable business market and thus have lots of extra capability. I just don't need that capability despite having a decent home network (big home NAS, 4 access points on a UniFi mesh, an internet connected house alarm, multiroom HiFi, home automation (Nest etc), a modest CCTV system with 8 cameras).
Lastly, if you can postpone your purchase (I could not.....), then at the higher prices of other LTE modems, give serious consideration to the 1Gig enhanced LTE standard. There are already a few devices with the new standard and it would get your system ready for next year (or today if you live in Australia).
PS: On the latter point, Samsung's S8 mobile, but not Apple's iPhone X, already have this 1 Gig standard built in to them....
PPS: No apologies for going on and on..... NetGear are giving us loads of time to waste whilst they scale the mighty task of changing one line of code in the firmware........
Similar situation for me, so at least now I don't feel so alone. Today I received a Netgear LB2120 from Amazon. I live in rural SC, have crappy DSL (<4Mb, losing sync frequently), but reasonable 4G LTE (AT&T). So the plan was to use the Netgear to give me DSL when it can, and switch to my limited bandwidth 4G as failsafe. I've spent the day trying to get this working 100%. I am ready to settle for 75%.
I am good at IT, but (regretably) networking remains my main area of ignorance, so for me it's a lot of trial and error (and patience). My naive plan was to connect my old Motorola Netopia 2210-02 DSL modem in bridge mode to my new Netgear LB2120 in bridge mode, and connect that to my Ubiquiti EdgeRouter PoE (firmware 1.80) to handle NAT, DHCP, some local static IPs, and provide WiFi via my two Unifi access points. I wasted half the day trying to get the router to see the LB2120 in bridge mode, came across a post by someone who had it in router mode (which didn't seem right to me), tried that and BAM, the router sees the LB2120. So that sort of works, but not how I thought it should.
What does not work is my DSL with the Netgear. The LB2120 sees the connection, but won't use DSL even though the DSL modem status looks fine. So basically I have an LTE modem working with my EdgeRouter and Unifi access points, but no DSL. For me, the speed of my LTE connection is amazing compared to my substandard unreliable but unlimited DSL, but then there's the LTE bandwidth limitation and threat of throttling. I have a 25Gb shared plan right now (AT&T). I'll probably switch to unlimited, which will most of what I read and hear CAN but rarely throttles after 22Gb unless there's major congestion or TOS abuse (bit torrent, hosting, etc)..
The real solution for me would be AT&T's fixed wireless plan, but it's not yet available to me, despite begging more than once.
I doubt this adds much to the conversation, but just so you know ... no connectivity in bridge mode also occurs with the LB2120 modem.
Thanks to everyone here. It's the little tidbits of information that often make all the difference to me.
Ron
Hope I'm at the right place for a answer, I have the LB1120 on AT&T network with x10 router. Only problem I am having or think I am having is a Velocity hotspot will get 50mbps and the LB1120 will get 25mbps. I have tried it connected through the router as well as directly to pc. Any ideas on why speeds are so different and yes I'm using same simcard in both same location and signal strength. Thanks to anyone who can help.
It appears Netgear isn't willing mention when a firmware update is coming out, so I'll be returning it and buying something else. Bridge mode is the whole reason I bought this unit.
This is [redacted] and I am answering on behalf of the previous Expert. We do not know if a firmware is going to be released for this unit since only our engineering department knows that information. It will be automatically pushed to your unit. Regards, [redacted]
This is extremely disappointing. My next purchases will not be Netgear related.
There's no firmware update for my Nighthawk R8000 either (security related). Every other bit of network gear that I have, even hardware that's older has been patched.
It is ridiculous it is 6 months into it and this problem has not been resolved. It's been a while since I wrote software but I'm pretty sure this fix requires a change to a single line of code.
Shame on you Netgear.
same boat - drops connection in bridge mode
really incredible that netgear won't correct this problem
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 is now working for me on my LB1121 connected to a Ubiquiti USG 3 port. Pretty insane how long it took Netgear to fix this. Better late than never I guess.
After being in contact with support for over a month with nearly 20 back and forth exchanges they sent me a message this morning telling me they have no fix.
This was after numerous contacts telling me they duplicated the problem and had a firmware fix for it. Over the next three weeks several more contacts were made inquiring on when the fix was going available. They told me to update the firmware and the new version would be installed. When that didn't happen its like support returned to the top of the diagnostic menu tree repeating everything over again.
As of now it has been a total waste of time and they appear to be washing their hands of the situation. I will keep my ticket open as long as I can but I suspect they are done with support.Netgear has had the beta FW to fix the LB bridge issues for sometime now so official FW to fix the problem should be availble sometime in the near future. For those of you having issues with LB bridge mode where your router is not able to work with subnet mask 255.255.255.255 that LB uses in bridge mode you need to reach out to DarrenM and provide him with your contact info and your LB model SN and IMEI and Netgear can push the beta fw with fix to your device.
For those of you who have reached out to Netgear and got the beta FW to fix the issue you need to make sure you see the following version numbers:
Firmware Version: M18Q2_v12.09.163431
Firmware Build Date: Unknown
App Version: NTG9X07C_12.09.05.26
Web App Version: LBHDATA_03.03.103.165
Bootloader Version: Bootloader Ver: v1.0.0
Hardware Version: 08
If your device has the same version then you are on the beta FW already and if the problem still persist I would reachout to you router vendors and get the latest FW verison for your router. Most new routers should not have an issue with a connection such as one provided with LB in bridge mode where subnet mask is 255.255.255.255. The reason LB utilzes this subnetmask in bridge mode is becuse a network with a subnet mask of 255.255.255.255 puts each device inside its own subnet, forcing them to communicate with the router before communicating with any other device.
As always if any other issue occur partining to bridge mode after beta FW is applied your best bet is to reach out to the Netgear support team and work with them to get to the bottom of the problem.
Hi Ernest,
Although a /32 (hostroute) mask is valid, I find many if not most modern routers and firewalls do not properly support it. Given that, it is best to avoid using it and saving everyone a lot of grief.
I think part of the problem and that the general rule we use is that the default gateway needs to be on the same subnet as the interface. Using a /32 breaks that logical rule.
I have been using the beta firmware for a while and it has been working fine with both SonicWALL and Cisco firewalls.
We have spoken with support a dozen times now...Engineers are always working on the issue. They already have fix but must be spending 1000's of hours "working" on it. There are several issues at this point with this model that could be fixed in minutes if they actually cared about their customers.
When my GM asked me if we could purchase these units for testing I was extremely hesitant. Knowing how horrible netgear products are and the support that goes with (it's actually worse than the products). I reluctantly allowed him to purchase them in an attempt to replace our existing product (which actually works - who'd think a modem with bridge mode actually bridges the connection!) but is cumbersome to setup. Inital testing everything worked fine and I was shocked to say the least. A Netgear product that worked out of the box and we didn't even have to wait for a firmware update or deal with support. The thought that bridge mode DHCP wouldn't work never even crossed my mind.
We deployed 50 of these to start with on our demo units and order many more. One technician noted a problem by which bridge mode wouldn't work and the subnet was wrong. We blamed the carrier since it worked in house. Waiting for them to fix to the problem we identified the culprit. DHCP just doesn't work on these units if in Bridge Mode. The DHCP from the provider includes the Subnet Mask.
I paid several thousands of dollars on these and the biggest feature they advertise doesn't work. I can't believe they can get away with this without someone filing a law suit for false advertising. We have lost quite a bit of money "waiting on engineers".
There is another flaw in this unit's design which was stumbled upon by this issue. The firmware is remotely managed. Why do we not have the ability to upload the firmware ourselves?
So we basically have 100's of units that do not work and have no forseable way to make them work for our application. If Netgear ever actually pushes out a firmware to the device we will end up paying $1000's of dollars in data alone because we have not way to upload the firmware via our wired connections.
Bucanero: Were you able to find a suitable replacement? It's obvious Netgear has failed again (as usual).
I know it sounds like I'm bashing on Netgear, however, they created the hostility by falsly advertising their products, failing to support their products, ignoring customer requests and complaints, failure to provide any kind of reasonable honesty. If they stood behind their products and their products worked this post wouldn't have been made and I'd be second guessing if we should give them another shot.
I've just stumbled on this thread after trying to get a LB working with my ubnt Edgerouter. As you might imagine, it doesnt really work.
Any ideas how I can test the Beta firmware before I send the device back to where it came from?In the meantime, I've also ordered an old Sierra ES440, see if that works properly.
By the time I got on the beta release of the firmware I was long past the return period. And of course, the firmware did nothing to fix the issue. I guess NetGear sees their way of handling subnet masks as a feature and not a bug. BTW: I had been working with support for over two months.
If you can use it outside of bridge mode it works okay.
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 as outlined here : https://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5#LEASE_REQUIREMENTS_AND_REQUESTS
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).
Hi,
Can you tell me exactly where you make this setting in pfsense? I sent my LB1120 back to Amazon long ago but kept up with this thread. I am a pfsense fan but must admit I was not aware of this feature. I can't even find where it is set.
thanks
Retired_Member wrote: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 as outlined here : https://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5#LEASE_REQUIREMENTS_AND_REQUESTS
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).
Hi,
Can you tell me exactly where you make this setting in pfsense? I sent my LB1120 back to Amazon long ago but kept up with this thread. I am a pfsense fan but must admit I was not aware of this feature. I can't even find where it is set.
thanks
Retired_Member wrote: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 as outlined here : https://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5#LEASE_REQUIREMENTS_AND_REQUESTS
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).
