Tommy,You might be interested to know that one of my systems, the one I'm using now, was attacked by a rather nasty virus Christmas eve. I know where the virus came from, and I know what the virus is. I also know that even the 3 virus and malware programs I run wouldn't touch it, and that from past experience in the corporate world this particular threat is above serious. My decision was to roll back my system using the software and hardware I described above. I booted from the recovery CD and performed a sector by sector reimage of my system. 2 1/2 hours later the system is like new and the virus gone.
So what was the infection vector, Victor? And what was the nasty bug?
Anyway after using it a while it became clear that the Internet connection with it was very flaky, pages won't load half the time and stuff like that.
Try setting the MTU on the WAN interface of your router to 1492. The default is usually 1500, but the extra overhead of the DSL PPP connection often requires turning it down a bit.Does your router get a public IP address on its WAN interface, or is it pulling a private IP address (192.168.x.x) from the modem? If the subnets (first three octets) you'll have all kinds of problems. If they aren't the same but you're getting a private IP address, you might be dealing with a double-NAT issue which can result in flakiness.
The router is getting a private ip(192.168.168.x) from the modem (which is some variety of wireless LTE modem from the local telephone cooperation and is located on the side of the house with a cat5 that comes inside, goes to a PoE, and a cat5 goes from the PoE to the router) and the router is handing out addresses like 192.168.1.x. You may be onto something with double NAT being the problem. I'll see if I can disable NAT on the new router along with changing the MTU(assuming that can be an issue with a non-DSL modem) tomorrow and see if that helps. FWIW best I could tell the network connection itself wasn't dropping, just the Internet.
If you disable NAT, you would also have to set a static route in the modem pointing back to you your 192.168.1.x network... otherwise, the modem won't know where to route that traffic. Basically, the route entry in the modem would say "for the 192.168.1.x network, send it via the public IP address of the other router." This also means your router's WAN IP address would have to be set to a static IP address to prevent it from changing.I don't know what options you have, but for CenturyLink DSL service where I live, I can set the modem to 'bridging' mode, then have my router make the PPP connection. My router then gets a real, public IP address on its WAN interface.
Page created in 0.116 seconds with 23 queries.