#arpnetworks/ 2014-10-19,Sun

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
mnathanibrycec: looks like its O.K now : ping wolfman.devio.us
PING wolfman.devio.us (66.7.199.108) 56(84) bytes of data.
64 bytes from devio.us (66.7.199.108): icmp_seq=1 ttl=244 time=35.3 ms
[00:18]
***Arenlor has quit IRC (Ping timeout: 264 seconds) [00:29]
........ (idle for 36mn)
zhangxiaobao has joined #arpnetworks
zhangxiaobao has quit IRC (Read error: Connection reset by peer)
[01:05]
zhangxiaobao has joined #arpnetworks [01:21]
mnathaniI wonder what can explain this: https://smokeping.cobryce.com/?displaymode=n;start=2014-10-18%2013:26;end=now;target=Internet.VoipMS.toronto3voipms
latency drop from 160ms to about 70ms
[01:27]
zhangxiaobaoare you experiencing periodic abnormal latencies on ipv6?
every 8 or so pings has very high latency
64 bytes from 2607:f2f8:acd0::1: icmp_seq=1 ttl=64 time=20.8 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=2 ttl=64 time=29.8 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=3 ttl=64 time=0.527 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=4 ttl=64 time=0.847 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=5 ttl=64 time=0.496 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=6 ttl=64 time=0.512 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=7 ttl=64 time=9.80 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=8 ttl=64 time=25.5 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=9 ttl=64 time=11.1 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=10 ttl=64 time=0.795 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=11 ttl=64 time=0.736 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=12 ttl=64 time=0.709 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=13 ttl=64 time=0.548 ms
64 bytes from 2607:f2f8:acd0::1: icmp_seq=14 ttl=64 time=1.32 ms
[01:28]
mnathanizhangxiaobao: use pastebin for multi line messages [01:30]
zhangxiaobaook, sorry [01:31]
mnathaniI have not noticed anything, you are probably experiencing ICMP de-prioritization [01:31]
zhangxiaobaoand looking glass seem to have lost ipv6 connectivity, can't ping anywhere? [01:33]
***zhangxiaobao has quit IRC (Remote host closed the connection) [01:39]
mnathaniI don
I don't think they set up Ipv6 on the looking glass as yet
[01:47]
***zhangxiaobao has joined #arpnetworks [01:50]
.... (idle for 15mn)
zhangxiaobao has quit IRC (Remote host closed the connection) [02:05]
.............................. (idle for 2h25mn)
pjs has quit IRC (Read error: Network is unreachable)
pjs has joined #arpnetworks
up_the_irons has quit IRC (Ping timeout: 260 seconds)
pjs is now known as Guest20602
up_the_irons has joined #arpnetworks
ChanServ sets mode: +o up_the_irons
[04:30]
up_the_ironsmercutio: i fixed ipv6 on the lg [04:38]
.... (idle for 17mn)
mercutiooh cool
heh traceroute6 to www.arpnetworks.com shows as www
maybe take the search path out in resolv.conf?
[04:55]
..... (idle for 21mn)
up_the_ironslol
yeah go for it
[05:17]
......... (idle for 40mn)
***Guest20602 is now known as pjsg
pjsg is now known as pjs
[05:57]
.................................... (idle for 2h57mn)
brycecmnathani: That is interesting about the voip.ms hosts. If you look at the "Last 7 days" you'll see it's consistent, same times every day for the last week, coinciding with packet loss too. Apparently there's congestion along the route. Here's an mtr, you can clearly see it's the Level3/NTT handoff http://sprunge.us/dDNW [08:54]
..................... (idle for 1h43mn)
***pjs has quit IRC (*.net *.split)
toddf has quit IRC (*.net *.split)
SpaceDump has quit IRC (*.net *.split)
m0unds has quit IRC (*.net *.split)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
SpaceDump has joined #arpnetworks
m0unds has joined #arpnetworks
pjs has joined #arpnetworks
pjs is now known as Guest72906
[10:37]
......... (idle for 41mn)
Seji has quit IRC ()
Seji has joined #arpnetworks
[11:20]
.................................... (idle for 2h58mn)
mercutiohmm that didn't seem to work [14:22]
............... (idle for 1h13mn)
mnathanibrycec: I would think its more like a shift in routing, in a schedule like that rather than congestion. I plan to compare mtr reports from times of lower latency to higher latency to see if I can figure it out [15:35]
brycecmnathani: well you have my mtr from the high latency time period :) [15:36]
mnathaniI do indeed [15:36]
mercutioif there is actual congestion usuallyt iperf in udp mode at low bandwidth over a long period of the time is best way to monitor
you can usually get it to report every 0.5 seconds, but you can hack the source to report every 100 msec.
[15:38]
mnathanimercutio: you probably need access to a box at each end to test that out? [15:38]
mercutiomnathani: yeah.
that's the annoying part.
[15:38]
mnathaniremote end being monitored is a Toronto Voip.ms POP
is there a way to get a reverse trace route without access to a looking glass or the remote end?
[15:39]
mercutiooh.
nope
you could email them
is it level 3 outbound?
hopefully level3 inbound is turned on soon and fixes it.
[15:41]
staticsafestaticsafe is slightly concerned
i use Toronto's voip.ms POP
[15:44]
mercutioi tried google hangouts outbound voice thingy before. the free thing. it seemed laggy.
skype worked better.
i dunno how skype manages so well tbh. for international calls it seems to have some great jitter correction or something - it doesn't feel like it breaks up and jitters heaps.
and the echo cancellation seems superb.
[15:56]
.... (idle for 19mn)
mnathani+1 for Skype
connection has to be really poor for quality to degrade
[16:17]
mercutioi kind of hate skype, but it works well for actual calls.
it seems to be quite buggy though, especially on android.
and uses way too much cpu on android, linux, macos etc.
it never seems jabber really got as well functioning for every day users as i would have liked :(
[16:19]
mnathaniI use Skpe all the time on Windows, no complaints [16:22]
brycecFrom an ARP VPS? That would be really silly. 15:44:40 staticsafe | i use Toronto's voip.ms POP [16:33]
staticsafeoh nope
from home
[16:36]
brycecheh
Bear in mind that latency is being measured from an ARP vps... you're probably fine :p
er, bare
[16:36]
staticsafeim 10ms away from it, peering at the local IX [16:38]
mnathanistaticsafe: looking at the smokeping graphs, it seems toronto, toronto2 and toronto3 are the ones where latency changes drastically every day. ie: toronto4 seems unaffected
as brycec mentioned, this is latency to an ARP VPS
[16:39]
brycec(I don't think I knew there was a toronto4...)
toronto4 goes over Cogent
brycec never imagined he'd see Cogent actually be the better route
[16:40]
mnathanialthough the return traffic might be different as level3 is not announcing ARP IP space at the moment [16:42]
mercutioeww cogent
mnathani: on windows it works better than other platforms.
http://lg.arpnetworks.com/cgi-bin/bgplg?cmd=show+ip+bgp&req=184.75.213.210
http://lg.arpnetworks.com/cgi-bin/bgplg?cmd=show+ip+bgp&req=184.75.215.146
first is toronto4, second toronto3
oh, that's nlayer
i'm surprised it's going to nlayer via level3
so cogent is a better route if dual advertised, .. so they're avoiding cogent by not even advertising to cogent, or prepending
i like to add a prepend to cogent routes myself.
cogent often have short as-paths. but intermittent performance.
although on-net is a lot better than it was.
it's mostly their peering/transit that sucks.
[16:51]
......... (idle for 40mn)
mnathanimercutio: what do you mean by 'on-net' ? [17:37]
..... (idle for 24mn)
mercutiomnathani: cogent at both ends
like cogent -> at&t is crap etc.
[18:01]
.......... (idle for 45mn)
***sga0 has joined #arpnetworks
sga0_ has quit IRC (Ping timeout: 255 seconds)
[18:46]
......... (idle for 40mn)
zhangxiaobao has joined #arpnetworks
zhangxiaobao has quit IRC (Remote host closed the connection)
[19:26]
............... (idle for 1h14mn)
Guest72906 is now known as pjs [20:42]
................ (idle for 1h16mn)
vissborg has quit IRC (Remote host closed the connection)
vissborg has joined #arpnetworks
[21:58]
........................ (idle for 1h58mn)
novae has joined #arpnetworks
novae has quit IRC (Changing host)
novae has joined #arpnetworks
[23:57]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)