reply to novasource
Re: [TWC] TWC DNS servers dont respond after awake from sleep It was a big topic sometime in the past, kinda forgot about it to be honest.
I while back I used to have the Ubee device and it was a piece of crap. It had all sorts of problems with having packet loss with the ubee router.
I was having intermittent problems with looking my VPN connect for work and all my problems went away when I started using the ubee device in bridge mode and using my own router.
I had a friend who got the same ubee device several months later and started having the same exactly problems. When he changed the ubee device into bridge mode and started using his own router all his problems disappeared too.
SeleniaI love DebianPremium
reply to Jabbu
said by Jabbu:It must be crappy. With all the port scans I get on TWC(not sure why I didn't get them on Verizon, though TWC is otherwise better), enabling it on my Cisco equipment provides quite a performance boost. My guess is it's not allowing these to flood currently open connections. Of course, if it gets overloaded, I could see it degrading the performance or causing a reboot. I guess that is the difference between crappy and good equipment, among several other factors.
That flood protection is terrible.
100.1 usually means the modem is in bridge.
1.1/0.1 is acting as a gateway.
I bet $20 your problem is fixed.
A fool thinks they know everything.
A wise person knows enough to know they couldn't possibly know everything.
There are zealots for every OS, like every religion. They do not represent the majority of users for either.