#arpnetworks 2016-07-19,Tue

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)
WhoWhatWhen
***hycer has quit IRC (Ping timeout: 250 seconds) [10:59]
hycer has joined #arpnetworks [11:06]
................. (idle for 1h21mn)
[FBI] starts logging #arpnetworks at Tue Jul 19 12:27:06 2016
[FBI] has joined #arpnetworks 		[12:27]
vom513howdy 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 		[12:28]
***bmacs has joined #arpnetworks [12:38]
brycecI'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:38]
bmacsI'm having a lot of dropped packets on ipv4... epecially coming over pccw [12:39]
brycecNow IPv4 issues, that one I'd buy [12:40]
vom513heres the mtr - http://pastebin.com/bjXir7iP
pccw does appear in the path, trit after that 		[12:41]
brycecMy v4+v6 traffic is over different routes, no issues. Probably route-specific. [12:43]
bmacshttp://pastebin.com/zmJEcvaP [12:43]
brycecHm, 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:45]
bmacsI'm seeing 80% pacet loss here. any ideas, up_the_irons? [12:51]
mnathanihmm, I dont see Level3 in that mtr
whats the sourc ip? 		[12:51]
bmacsit's on charter... let me check... [12:52]
brycecmnathani: vom513's mtr had Level3
specifically a Level3-PCCW handoff
I wonder if this is related to AWS' network issues too 		[12:52]
mnathaniI was looking at bmacs mtr [12:53]
bmacsmy source IP is 66.215.80.116
let me test over level3...
0% loss 		[12:53]
mnathaniroute from ARP to 66.215.80.116 goes level3 to xo then to charteer
and loss occurs at charter 		[12:53]
brycecmnathani: (I know. But bmacs never mentioned Level3 :P I was referencing vom513's mtr when I said Level3) [12:54]
mnathaniboth mentioned pccw
thought your level3-pccw mention was related
mnathani wanders off 		[12:55]
bmacsOh yeah... I did a mtr from ARP to charter and I see loss at charter... [12:56]
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 		[13:05]
up_the_irons an ideas? [13:19]
up_the_ironsWe're looking into this currently [13:25]
***Squuu has joined #arpnetworks [13:26]
Squuuddos?
getting packet loss to my vps 		[13:26]
brycecSquuu: https://twitter.com/arpnetworks/status/755499297202839553 [13:28]
BryceBotTWITTER: We're currently looking into packet loss coming over PCCW paths (Tue Jul 19 20:27:23 +0000 2016) [13:28]
brycecSo check your traceroute/mtr, see if you're connecting over PCCW [13:28]
Squuuyep [13:29]
up_the_ironsyeah it looks to be a DDoS [13:30]
unless IP is spoof'd (same IP for everything), attack is coming from AWS [13:35]
brycecbrycec called it: 12:52 <brycec> I wonder if this is related to AWS' network issues too [13:40]
bmacsThe 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? 		[13:41]
up_the_ironsWe're already null routing the destination IP (target of attack) [13:52]
Squuumuuuch better [13:55]
bmacsyeah, things are def feeling better now [13:55]
BryceBotThat's what she said!! [13:55]
up_the_ironsoh BryceBot [13:58]
Wondering why our null route over Trit Networks (and thus PCCW) didn't work [14:08]
.... (idle for 15mn)
Squuu: bmacs : you guys seeing any other issues? [14:23]
vom513up_the_irons: my v6 path in via l3->pccw->trit->arp looks much better [14:24]
up_the_ironsvom513: roger that thanks [14:26]
Squillisnope. all's well here [14:39]
***Squuu has quit IRC (Quit: Page closed) [14:39]
..... (idle for 20mn)
up_the_ironscool [14:59]
.... (idle for 15mn)
bmacsLooking good, thanks! [15:14]
up_the_ironsNo problem! [15:16]
............... (idle for 1h11mn)
***bmacs has left [16:27]
.................. (idle for 1h28mn)
vom513 has quit IRC (Quit: thanks guys) [17:55]
.................... (idle for 1h35mn)
hazardous has quit IRC (Ping timeout: 252 seconds) [19:30]
hazardous has joined #arpnetworks [19:38]
↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)