***: hycer has joined #arpnetworks
[FBI] starts logging #arpnetworks at Tue Jul 19 12:27:06 2016
[FBI] has joined #arpnetworks vom513: howdy all - any known issues with ipv6 at the moment ?
my mail client started complaining (server is an arp vps)
mtr looks like something busted close to arp
i can pastebin an mtr/trace if that would help ***: bmacs has joined #arpnetworks brycec: I'm personally connected over ipv6 (ssh to the tmux that runs this weechat instance) and not noticing issues, but that doesn't mean everything is perfect bmacs: I'm having a lot of dropped packets on ipv4... epecially coming over pccw brycec: Now IPv4 issues, that one I'd buy vom513: heres the mtr - http://pastebin.com/bjXir7iP
pccw does appear in the path, trit after that brycec: My v4+v6 traffic is over different routes, no issues. Probably route-specific. bmacs: http://pastebin.com/zmJEcvaP brycec: Hm, I don't know who PCCW Global is but your issues do appear to start with them, perhaps an oversaturated link between PCCW and Level3 bmacs: I'm seeing 80% pacet loss here. any ideas, up_the_irons? mnathani: hmm, I dont see Level3 in that mtr
whats the sourc ip? bmacs: it's on charter... let me check... brycec: mnathani: vom513's mtr had Level3
specifically a Level3-PCCW handoff
I wonder if this is related to AWS' network issues too mnathani: I was looking at bmacs mtr bmacs: my source IP is 66.215.80.116
let me test over level3...
0% loss mnathani: route from ARP to 66.215.80.116 goes level3 to xo then to charteer
and loss occurs at charter brycec: mnathani: (I know. But bmacs never mentioned Level3 :P I was referencing vom513's mtr when I said Level3) mnathani: both mentioned pccw
thought your level3-pccw mention was related -: mnathani wanders off bmacs: Oh yeah... I did a mtr from ARP to charter and I see loss at charter...
Just tried from AWS oregon... 80% loss starting at PCCW
pccw -> trit -> arp
http://pastebin.com/M1eZRTrU
oh, I bet it's showing losses when it gets to charter because the return packets are going over PCCW
can we just pull those routes out of arp's AS?
I jsut did a reverse to AWS and it's showing losses once it exits level3 http://pastebin.com/SYxyF5cM
90% packet loss
up_the_irons an ideas? up_the_irons: We're looking into this currently ***: Squuu has joined #arpnetworks Squuu: ddos?
getting packet loss to my vps brycec: Squuu: https://twitter.com/arpnetworks/status/755499297202839553 BryceBot: TWITTER: We're currently looking into packet loss coming over PCCW paths (Tue Jul 19 20:27:23 +0000 2016) brycec: So check your traceroute/mtr, see if you're connecting over PCCW Squuu: yep up_the_irons: yeah it looks to be a DDoS
unless IP is spoof'd (same IP for everything), attack is coming from AWS -: brycec called it: 12:52 <brycec> I wonder if this is related to AWS' network issues too bmacs: The source IP of all the packets are the same? that's weird. Maybe somebody is just transfering a big file. ha.
Can that IP be null-routed? up_the_irons: We're already null routing the destination IP (target of attack) Squuu: muuuch better bmacs: yeah, things are def feeling better now BryceBot: That's what she said!! up_the_irons: oh BryceBot
Wondering why our null route over Trit Networks (and thus PCCW) didn't work
Squuu: bmacs : you guys seeing any other issues? vom513: up_the_irons: my v6 path in via l3->pccw->trit->arp looks much better up_the_irons: vom513: roger that thanks Squillis: nope. all's well here ***: Squuu has quit IRC (Quit: Page closed) up_the_irons: cool bmacs: Looking good, thanks! up_the_irons: No problem! ***: bmacs has left
vom513 has quit IRC (Quit: thanks guys)
hazardous has quit IRC (Ping timeout: 252 seconds)
hazardous has joined #arpnetworks