NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LB2120 DDNS client
I am implementing the LB2120 in the ROUTER mode and am connecting the Verizon modem directly to the input and run everything on the network created by the LB2120. I have a wireless repeater for all the wireless devices and a switch to feed all the wired devices on the LAN side of the LB2120. Many of the devices pass their current WAN IP address (so they are accessible from anywhere) to a DDNS service so I can contact them from outside the network no matter what WAN address they are currently on via the router(s). The problem is, the devices do not refresh that WAN address except on power-cycle boot-up. They are not intelligent enough to recognize a change of WAN addresses as a requirement to update the DDNS server. Once fall over takes place, and the 2120 is "assigned" a new WAN address via the cellular service, I can no longer access the devices on the LAN because I have no way of knowing the new WAN address. I have tried to program a network power switch to power cycle the LAN devices, forcing them to refresh their WAN addresses to that of the 2120 but once I lose contact with some of the devices, I lose conatact with all of them. The switch is intelligent enough to reset power if it loses a WAN signal but cannot distiguish that from a "changing" address, so it doesn't power cycle on a change of addresses.
A solution would be to simply add a DNS client to the 2120 thereby triggering a change of WAN address update to the DDNS monitor and allowing immediate access to the devices behind, essentially, a different modem.
I've considered the BRIDGE mode but for my implementation, it seems too limiting as I would need to run another modem behind it to operate my LAN properly.
Do I misunderstand the whole thing or are there other solutions I'm unaware of?
5 Replies
Are you still having issues with the LB2120 and DDNS? Have you found a work around?
Others in the community have indicated problems with the LB2120 not being friendly to DDNS.
Sorry for the dely . . . Life got in the way.
Still haven't figured it out.
I'm on Verizon with a Actiontec MI424WR Rev. 1 Modem
There is one WAN port
But my limited knowledge is keeping from figuring this all out.
Many of my devices are crashing through the LB2120 and into the Verizon Modem.
Others devices are not.
I don't really understand why some work and others don't and what to do about it.
It has both a WAN CoAx and WAN Ethernet connection.
Is that "two WAN ports"?
Do I connect the LB2120 to the Ethernet WAN port and my Intranet devices to the LAN Ethernet ports?
Or to the LB2120 ports?
If so, how do I reach devices on my Intranet and how do things inside the Intrnet connect to devices on the WAN Internet?
I'm sure someone is shaking their head at my stupidity. Just trying to understand.
S.
One of the things I have discovered using ping traceroute regarding the LB2120 is that the AT&T network does not use conventional back-bone system that you may observe with a tranditional HSI provider (i.e. Comcast, Charter, etc). The LB2120 will be assigned an IPv4 address, however, it appears to route through AT&T's own private network before getting to the internet backbone. So even if DDNS is implemented on the LB2120, the assigned IPv4 address will not be vissible on the internet backbone.
Even if we went with IPv6 addressing, it is not clear if the AT&T routers/gateways would block external access to the LB2120.
In short: I think implementing DDNS on the LB2120 may be more involved that just implementing some software on the LB2120. It may require coordination with the cell-phone providers.
NOTE: This is MY observation working in the South Bay Area of California.
Suggestion: Get a router with dual WAN ports. This will eliminate the need for "passthrough" modes and put the issue on the router/gateway instead of the modem. Most routers have much better support of DDNS than modems.