whitefang: it's never too early ;)
whitefang: oohrahlights.com
I can't believe this packetloss is still here :(
something still seems to be jamming up the machines from time to time. :(
its not the machines
its one of the routers between me and my VPS
--- ionise.org ping statistics ---
3724 packets transmitted, 3413 packets received, 8.4% packet loss
round-trip min/avg/max/stddev = 108.183/111.739/148.069/1.510 ms
its been like this for almost 2 weeks now
whitefang: that sucks. I had a similar problem with freedesktop.org, which normally I wouldn't care about, except I was running freebsd.
... so every time it tried to grab a source tarball from there... :(
(not from arp though)
--- ionise.org ping statistics ---
4461 packets transmitted, 4324 packets received, 3.1% packet loss
round-trip min/avg/max/stddev = 101.007/134.934/360.248/46.853 ms
hm
Hi from android land
lucky: 63.216.14.157 is the weak link fwiw
14705 packets transmitted, 13598 packets received, 7.5% packet loss
round-trip min/avg/max/stddev = 81.902/107.490/682.102/35.244 ms
ah that's why mtr isn't showing any problem... it's going ipv6
--- 63.216.14.157 ping statistics ---
duh.
maybe a solution would be to setup an ipv6 tunnel?
is the packet loss actually causing you much trouble?
its pretty crappy
arpn has native ipv6
I get a lot of delay and dropped characters sometimes via ssh
no need for a tunnel.
yeah but my ISP doesn't
ah.
I use it as a ventrilo server too so that sucks even more
and I got it to run a personal minecraft server but I can forget that :/
is PCCW Global (63.216.14.157) that is the massive problem
it used to be almost as responsive as an SSH session on my LAN at 40ms or less
but now its a solid 125ms with spikes to 300ms+
I'd make a support ticket but its not really ARPs problem
or even my ISPs problem
its a peer
You can still email the PCCW NOC and show them the bad traceroutes
or send in ninjas to unplug it.