NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bseright
Apr 05, 2017Aspirant
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...
- Oct 24, 2017
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
bordr415
Oct 23, 2017Aspirant
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.
- racingclub21Oct 23, 2017Tutor
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.
- Retired_MemberOct 23, 2017
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).- bordr415Oct 23, 2017Aspirant
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.)
- Retired_MemberOct 23, 2017
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.
- racingclub21Oct 23, 2017Tutor
thanks for the reply.
I'll cut my losses and look for alternatives then.
I've got the Sierra on order & also wondering if a Teltonika could do the job too.