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