Forum Discussion
Just got Gen5, new router is losing internet over and over again.
- 8 years ago
Hrm, you may want to look into using the Parental controls in the modem to limit things, along with Norton DNS... It's not that the DNS settings are being bypassed, it's that OpenDNS depends on knowing what IP you are behind... Sadly, we aren't given a publicly routable IPv4 address and things such as OpenDNS don't usually work well.
If you know a little bit about FreeBSD and the such... I would urge you to look into setting PFSense + Squid + SquidGuard up on your network as a local firewall/proxy. Some pretty powerful stuff once you get the hang of it.
Before you do that, try powering the modem off for a few minutes... When I changed from the default to the one I prefered, the Modem had serious issues, especially when I went to add in a static MAC entry... Pulling power at the wall for a little bit, and rebooting the rest of my network and it started to smooth out.
What do you have the lease time set to? I am going on a 1 hour lease, forgot what the default is.
Next time the network is up, check your IP on your computer and see what it says... When it goes back down, immediately check again and see if the address has suddnely changed..?
Well, its still stable, this is frusturating behavior to say the least. I have re-enabled wireless, 5GHz only for my office and plugged in a Netgear for the rest of the household.
I did notice while troubleshooting that for a little bit my computer would get the external IP of the device, then switch to the private lan address. That seems to be settled out now.
FYI, I set my lease to 1 day.
- JohnL8 years agoNew Poster
I was able to replicate the problem when I disabled IPV6 Automatic, also noted this in the logs, look at the dates:
I just noticed this... Look at the dates:
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [2]: Record Type=2
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [1]: Multicast Address=224.0.0.253
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [1]: Num src=0
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [1]: Aux Data Len=0
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [1]: Record Type=2
Dec 31 19:01:08 (none) user.warn [igmpproxy main] igmpproxy[1191]: [acceptV3GroupReport] Group Record [0]: Multicast Address=224.0.0.253- C0RR0SIVE8 years agoAssociate Professor
Don't mess with the IPv6 setting...
As far as those error logs, they can pretty much be ignored. The unit doesn't know the time/date untill after it has contacted the NOC, if it's somewhat freshly rebooted it could be showing old information. The other errors I can't explain, I get them as well but performance seems fine? It's probably something similar to other wireless routers where it logs any little hiccup that doesn't always matter.
But yeah, don't mess with the IPv6 settings... Leave them enabled on the modem, otherwise this will happen... "I did notice while troubleshooting that for a little bit my computer would get the external IP of the device, then switch to the private lan address."
That aside... does the system still seem stable and working right? If not, Liz will have to run diagnostics on your terminal when she pops into the office tomorrow.- JohnL8 years agoNew Poster
At the moment it seems ok, but the behavior is still concerning to me. It seems that with IPV6 enabled OpenDNS does not work, it must bypass the defined DNS settings. I am working with an additional router internally attemping to lock down the connection a bit to keep my kids focused during school hours.
Related Content
- 5 months ago
- 10 months ago
- 9 months ago
- 5 years ago