NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LB2120 - Bridge Mode Issues
First some details about my setup and what I've learned so far about bridge mode on the LB2120. The next posts will describe some issues I'm having and ask for help. I'm using an LB210 in bridge ...
Everything is working pretty well except that I can only access the raspberry pi's SMB shares by IP, not by name. Again, I understand that once the wireline broadband goes down and the LB2120 fails over, I won't be able to reach the raspberry pi at all from the local lan. Even though the LB210 is in bridge mode, when the failover occurs, it cuts off the WAN port completely and instead of passing through the IP from the ethernet WAN port it passes the newly received mobile IP to the raspberry pi. Still, it'd be great if I could get this to work.
It apepars that NetBios name registration broadcasts from the raspberry pi are getting blocked by the LB2120, even though it's in bridge mode.
Anyone have any ideas about how to work around this?
Thanks.
One other FYI about the LB2120's quirky bridge mode is that you can't manage the LB2120 from the WAN port, even in bridge mode. As a workaround, I set up the raspberry pi that's connected to the LB2120's LAN port as a web proxy.
The kludgy way I did this was to create an SSH putty session to the raspberry pi that has tunnelling enabled. Of course, for this to work the device connected on the LB2120's LAN port (eg my raspberry pi) must have SSH enabled.
In the putty configuration window, set the IP to the device connected to the LAN port (192.168.1.20 in my case). Next, still in putty, go to Connection->SSH->Tunnels and add a new forwarded port with Port set to 1234 and the "Dynamic" radio button pressed (leave destination blank). Click Add and then click the session category (on the left) and save the configuration.
Whenever you want to manage the LB2120, start an SSH session to the device connected to the LB2120's LAN port using the parameters you just saved and login to the device. Next, go to your web browser and set up a manual proxy with the SOCKS host set to 127.0.0.1, the port set to 1234, and SOCKS version set to SOCKS v5.
Now you can enter the IP address that you statically assigned to your LB2120 into your web browser to manage it (in my case, 192.168.1.200). This only works while the SSH session is active and also remember to turn off the proxy once you're done managing the LB2120.
Your brief is excellent. It was helpful to consult during my implementation. I decided to leverage the routed mode as a result. This allows for the dhcp function on the LB2120 to leveraged for my internal router during a failover scenario.
Additionally I configured my internal router as the dmz host on the LB2120, which allowed all PNAT & firewalls rules to work completely.
This allows the failover and failback functions to works without intervention.