Single linode, lots of Priv In spikes?
since I've got only one linode I cannot understand these (relatively) huge Priv In spikes:
~~![](<URL url=)http://dl.dropbox.com/u/2875427/priv_in_graph.png
When I saw the first one I thought "maybe the backup" but I'd appreciate any help.
Thanks~~
11 Replies
My Linode shows exactly the same thing - it's probably something simple like pings hitting your Linode from the local router or similar and not likely to be something to worry about.
Indeed it's a few bites but they sort of coincide with a more sluggish website (which is the reason I check the graphs in the first place).
If you take any group of hosts running ipv6, you get a fair amount of background chatter, and a lot of it is multicast setup traffic. And it's usually at regular intervals, unless someone specifically changed it in their setup. Can't really turn it off without breaking "features" of ipv6. It's just part of the package really.
Some examples of what kinds of things use ipv6 where many people don't realize here:
and
-Chris
not worried about quota, more about the fact that it seemed to happen roughly at the same time of a more sluggish website
Thanks
Just an idea.
@fuzzman442:
Just a wild idea… are you using IPv6? I mean, is your goal to make that website IPv6 accessible? If not, make sure that your web server is not listening on your IPv6 addresses. Its possible that IPv6 is trying to auto-configure or something when that traffic hits your Linode. That can cause a perceived disruption to IPv4 traffic, because a lot of (most?) browsers these days are configured to prefer IPv6 by default. So if an IPv6 link is coming up when you are browsing, you might be seeing that.
Just an idea.
If there aren't any AAAA records, it doesn't matter if the web server is listening on IPv6. If there are AAAA records, working IPv6 won't cause delays. (Unless, like, you have a relatively poor IPv6 route, but that's not what I meant.)
I checked to see if I installed anything on April 2nd when they started, but that must have been when I enabled IP v6.
Thanks!