***: carvite_ has joined #arpnetworks
JC_Denton_ has joined #arpnetworks
anis has joined #arpnetworks
JC_Denton has quit IRC (*.net *.split)
pjs has quit IRC (*.net *.split)
carvite has quit IRC (*.net *.split)
anisfarhana has quit IRC (*.net *.split)
BryceBot has quit IRC (*.net *.split)
ziyourenxiang_ has joined #arpnetworks
BryceBot has joined #arpnetworks
BryceBot is now known as Guest5935
carvite_ has quit IRC (Changing host)
carvite_ has joined #arpnetworks
carvite_ is now known as carvite
Guest5935 is now known as BryceBot
BryceBot is now known as Guest34050
Guest34050 is now known as BryceBot
BryceBot is now known as Guest36816
Guest36816 is now known as BryceBot
BryceBot has quit IRC (Changing host)
BryceBot has joined #arpnetworks
pjs_ is now known as jps
jps is now known as pjs
erratic has quit IRC (Ping timeout: 256 seconds)
erratic has joined #arpnetworks
zedomega_ has joined #arpnetworks
zedomega has quit IRC (*.net *.split)
anis has quit IRC (Ping timeout: 260 seconds)
anis has joined #arpnetworks
mercutio has joined #arpnetworks
ChanServ sets mode: +o mercutio mercutio: We're implementing a new ipv6 router, would anybody be interested in beta testing it? brycec: mercutio: I'm intrigued. What's involved? ***: JC_Denton_ is now known as JC_Denton brycec: (just my /48 gets moved/announced from the new router, and I update my end?) mercutio: brycec: We'd just port your vlan over. ***: JC_Denton is now known as Guest47441 mercutio: You wouldn't change your end. ***: Guest47441 is now known as JC_Denton brycec: Cool. Should I expect much interruption/stability? (I mean, yeah it's a beta test, but *how* beta is it? :p)
Either way, I have a /64 (viable for beta-beta) and /48 (ideally late-beta) I'm happy to test with. mercutio: brycec: a little potentially
that's why looking for beta testers first. :)
it shouldn't be greatly unstable. it's like running a beta OS :) up_the_irons: I'm pretty confident it's solid brycec: Sounds good. My /64 does very, very little traffic while my /48 disruptions would be noticed but wouldn't be show-stopping. mercutio: it's not like running on beta hardware, it's more that there is a chance for issues because less proven stable rather than predictably unstable. brycec: That's all the endorsement I need :)
What's next, need me to email? PM? up_the_irons: We'll be terminating Cogent there as soon as they get their heads out of their asses and actually set up our new session brycec: ("terminating" is really terrible language choice when crossing from telecom back to the real world "Oh you're killing the contract?") mercutio: there's also killing a session etc, yeah, it can be odd ;) up_the_irons: brycec: nothing, mercutio will move your VLAN mercutio: then there's "server daemons" BryceBot: That's what she said!! up_the_irons: Haha yeah ***: ziyourenxiang_ has quit IRC (Ping timeout: 256 seconds) mercutio: your /64 and /48 are on the same vlan? brycec: BryceBot: no BryceBot: Oh, okay... I'm sorry. 'then there's "server daemons"' brycec: mercutio: no, completely different accounts in fact.
2607:f2f8:abf0::/64 and 2607:f2f8:a650::/48 mercutio: brycec: ah, so you want to move just your /64 now, or the /48 as well? brycec: mercutio: Yeah both accounts, more traffic is better right? mercutio: sure :) brycec: (both now, I wasn't clear) mercutio: ping me if any issues brycec: (Assuming I can connect to Freenode :P *rimshot*) mercutio: heh
you can always connect over ipv4 if ipv6 issues :)
ok moving your /64 shortly
brycec: do you have a test IP that you'd like me to check works? brycec: vps3.cobryce.com
(That's on the /48) mercutio: ah on the /64 brycec: (Had to look that one up) 2607:f2f8:abf0::253 should work mercutio: cool, i'll move your vlan now brycec
and check that that works :) -: brycec starts an mtr running :)
brycec is observing packet loss to 2607:f2f8:abf0::253 mercutio: it's moved but i can't reach from international
hangon :)
100% packet loss? brycec: Yeah, unreachable it seems. Coming from HE. mercutio: yeh it's from he.net i'm seeing it not work too
can you ping the gateway from there?
because the gateway can ping you -: brycec has to look up that host's v4 addy... brycec: mercutio: Yes, that :253 host is able to ping 2607:f2f8:abf0::1. My home connection is NOT able to ping 2607:f2f8:abf0::1 mercutio: it's odd, i can see the traffic going to you just no return
like it's lost it's default router
but still can see the gateway
can you see the default gw still looks sane?
weird i just saw some dns request come through brycec: Its default route is definitely set and working, and it was able to ping an IPv6 address of Google. mercutio: oh brycec: But when I try to reach that host from my home HE tunnel, nada. mercutio: yeh hangon fIorz: from ARP FRA doesn't work either, in case that helps you mercutio: ok better now brycec ? brycec: mercutio: Seems to work mercutio: sorry about that brycec: Beta(TM) mercutio: ironically it was the old router being the issue
it didn't load the route into fib from rib
that is the kernel routing table didn't match the userlevel routing table fIorz: still doesn't work from FRA mercutio: oh fIorz ? fIorz: [...]
11 r2.lax.arpnetworks.com (2607:f2f8:0:7::165) 179.839 ms 185.234 ms 175.512 ms
12 * * * mercutio: brycec: are you allowing icmp? fIorz: or maybe I am pinging the wrong address?
2607:f2f8:abf0::253 is the one that I don't get any responses from, ::1 and :a650::3 do respond mercutio: only abf0 has moved, and ::1 is gateway, that is why i was asking bryce :)
i can see traffic going through to it, but not coming back brycec: I'm sorry, I stepped away earlier once everything was working. Yes actually, the device blocks all traffic by default including ICMP packets. mercutio: cool
brycec: how is your latency? :) brycec: I haven't noticed any changes. mercutio: heh brycec: mercutio: Did you port the /48 I gave you too? I didn't notice any disruptions (I expected Freenode would've disconnected) mercutio: brycec: not yet :)
it'll be moved tonight most likely brycec: Cool
That one I use much, much more so I'll notice any changes in latency there. mercutio: cool. brycec: (The /64 you moved earlier is used basically-never, rarely anything "interactive" it's just there to be dualstack to a few sites that are 99.99% IPv4-only) mercutio: Does your normal route go via any2ix? brycec: I have no idea, and `mtr` can't seem to resolve any of the hops to DNS names so I still don't know. (looking at the un-moved network/host)
(Even traceroute6 fails to resolve them, blah) mercutio: that is so common with ipv6 brycec: I'm blaming Debian this time. The versions of mtr and traceroute on my home desktop have no issues with PTR for most of the hops mercutio: 2001:504:13::211:15
2001:504:13::211: would be the any2ix
15 is facebook :) brycec: Ah yes I see that /36 (32?) in my mtr
2. AS??? 2001:504:13::1a mercutio: cool
oh oops i maent 13 brycec: (mtr couldn't even determine its AS number) mercutio: i stripped off the last ip heh
2001:504:13::/48
so yeah any2ix should be migrated onto it soon too brycec: Just checked and both the moved and unmoved networks, going to google.com, are going over ANY2IX. mercutio: yeh google will, ISP traffic and other further away traffic is less likely
people like google, facebook etc peer a lot :)
well ISP traffic in US I should say is less likely to brycec: In that case, testing from my home HE.net tunnel to both the "moved" and "not yet moved" networks goes via HE.net -> ge-100-0-0-13.r00.lsanca07.us.ce.gin.ntt.net
(And off the top of my head, I only have HE.net tunnels to test from) mercutio: he.net goes via any2ix
it'll be reverse path going over ntt
ntt is terminated on a different router than any2ix brycec: And whadya know, running mtr the opposite way (towards my home connection) does show ANY2IX on both old and new v6 routers up_the_irons: How's it looking now?