***: Stan___ has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)
Stan___ has joined #arpnetworks
Stan___ has quit IRC (Ping timeout: 246 seconds)
mercutio has quit IRC (Ping timeout: 260 seconds)
dj_goku has quit IRC (Ping timeout: 240 seconds)
mercutio has joined #arpnetworks
ChanServ sets mode: +o mercutio
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds) brycec: Anyone else seeing appalling performance with HE's tunnels the past 12 hours?
(Figured others here use HE too, might have seen same.)
(Or at least heard about it from a list they follow) JC_Denton: yes brycec: Specifically I'm seeing over 50% packet loss to my gif's endpoint (tserv1.sea1) itself, and that really doesn't help the tunneled traffic. JC_Denton: painfully high latency and loss brycec: Well always nice when I'm not alone :) JC_Denton: must be all the netflix ipv6 angst ;) brycec: lol
(Not in my household - Netflix pulled that bullshit and I null-routed their IPv6 prefix) mnathani: brycec: I am curious how you figured out all the prefixes they use brycec: Google :P mnathani: dont they use akamai and/or amazon to host their content brycec: They self-host most of their stuff actually mnathani: in addition to ISP/Partner Netflix connect
you used pfsense at your network edge I presume to null-route? brycec: http://www.dslreports.com/forum/r30792233-ipv6-Netflix-now-also-blocking-HE-net-IPv6-Tunnels ***: fIorz_ has joined #arpnetworks
fIorz has quit IRC (Ping timeout: 244 seconds) JC_Denton: a huge chunk of their v6 stuff is in AWS, though
which sucks
so i did the dns proxy
which is annoying, because it breaks DNSSEC
i wish bind rpz could filter that crap brycec: (Currently down to 8% loss and falling, yippee)
0 loss in the last 200 seconds, and normal ping times, this feels much better
Oh bother, packet loss once again. ***: dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 250 seconds) mercutio: brycec: i haven't been having packet loss issues with he.net tunnel to arp
well smokeping doesn't show such
it may be bad to other places brycec: ...why would anyone with native v6 tunnel to ARP? mercutio: it's tracing to arp
from he.net
so lax to lax
i'm also monitoring the germany arp location too though
which is also fine from lax brycec: Ohhh I misunderstood, got it now. mercutio: cool brycec: Well it's not HE's network that seems to be the issue but rather an overloaded (DDoS'd, etc) POP, tserv1.sea1.he.net mercutio: ahh ok
i only recently changed from san jose to lax termination brycec: Was getting loss+latency with plain old v4 traffic to that host. mercutio: but they actually have a few locations, maybe sjc would work better for you?
actually i'm not sure what location it was
now that i think about it
because their main dc is fremont
yeah it was fremont
much of a muchness i suppose brycec: mercutio: I'm pretty sure Seattle is my closer (network, and geographic) POP https://dl.dropboxusercontent.com/u/3167967/screenshot_2016-07-07_11-38-50.png mercutio: doesn't help if network is lousy to there ;) brycec: traceroute *to* the POP was fine too mercutio: oh i thought you said it was bad with ipv4 too brycec: mercutio: Right, at hop 9 mercutio: tserv3.fmt2.ipv6.he.net is where i was brycec: "ping -4 tserv1.sea1.he.net" so to speak mercutio: heh wy route to tserv1.sea.he.net is via he.net in lax brycec: Really? Goes via Level3 for me ARP -> tserv1.sea1.he.net mercutio: from new zealand i mean brycec: ah mercutio: so i can't really test sea well ***: dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 246 seconds)
dj_goku has joined #arpnetworks