NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LM1200 repeatedly dropping link
I recently purchased an LM1200-100NAS to serve as an LTE failover connection for my homelab and noticed a strange issue while setting up my pfSense-based router to use the LM1200 as a secondary WAN c...
Well the Verizon conspiracy and default settings kinda sidetracked me. But, I got the LM1200 working well:
Login to LM1200
Settings > LAN > Operation Modes > Router
Settings > LAN > DHCP Server > Disabled
IP Address > 192.168.5.1/24 > Submit
(Default but use whatever non-routable IP address you wish.)
Settings > Software and Reset > Restart > OK
Login to your router
WAN IP Address set to Static
WAN IP Address set to same subnet as LM1200
Reboot
Fast, smooth, reliable failover and fallback. Nairy a bobble.
Good deal and Good Night.
ilektranik
Awesome ilektranik , love seeing the debugging spirit!
Main issue is that "Router" Operation Mode has always worked for Verizon. But "Bridge" does not.
So for situations where someone is hosting a server on their network, "Router" doesn't fit the bill as you can't reach internal resources.
As I convert more of my internal services to utilize reverse proxy, this is not as big a deal anymore, so may switch back to Verizon/Router mode at some point.
A single LAN port router with a static IP address is functionally a bridge, is it not. 'What's in a name?' To quote techtarget, "A simple bridge will have two ports -- in and out -- and will only connect two networks." Netgear simply screwed the pooch on implementation of bridging with the LM1200. A fix years in the making is no fix at all.
Have you looked at your upload speeds with the LM1200? The low data caps before downgrade? I fear hosting a Public Internet server of any utility behind this device is quite impossible.
And if you're stuck with Comcast, as I am, pretty much forget a home server anyway. At least a Port 80 or 443 one. Even at my 100Mb down and 10Mb up that's pretty slow for a server to service the Public Internet. A local reverse proxy hardly helps this.
If you rent a remote reverse proxy (I don't wanna say it ... cloud), there are still the speed and data cap speed reduction issues. So the actual server itself needs to be on somebody else's hardware. You may well still want a reverse proxy but that ain't a home server (home is kinda blurred as everyone works from home now).
Then there's the VPN, which seems de rigueur to me. Now, we're talking STUN/TURN which is a practical, albeit complex, solution anyway. This allows remoting into the house for console access to at home hosts which seems to be the best one is going to do with home servers.
Finally, if this always worked, why do so many in this forum thread state they've given up? Why all the Verizon won't work stuff? Why did no one SHOUT just use these simple setting steps? Why did I 'waste' hours of my life?
ilektranik
I'm seeing the same issue on my LM1200 with VZW. When I set to router mode with DHCP disabled as described above, it works. I'd like to retain bridge mode if possible. Any update on a permanent fix?