RE: where to go to understand DDoS attack vector
In this case, 17 is both the protocol and port number. Confusing coincidence :) -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Roland Dobbins Sent: Tuesday, August 26, 2014 8:32 AM To: nanog@nanog.org Subject: Re: where to go to understand DDoS attack vector On Aug 26, 2014, at 8:26 PM, Stephen Satchell l...@satchell.net wrote: qotd17/udp quote No, that's the protocol number - 17 is UDP - not the port number. -- Roland Dobbins rdobb...@arbor.net // http://www.arbornetworks.com Equo ne credite, Teucri. -- Laocoön
IPv6 route annoucement
Hoping to not start a war... We (a multi-homed end-user site) are finally getting IPv6-enabled Internet connectivity from one of our ISPs. In conversations regarding our BGP config, the ISP has balked at allowing us to advertise our ARIN-assigned /44, saying things like, do you know how many addresses that is!!?? Am I way off base in thinking this network size is not out of the norm? I know it's a lot of addresses (19 octillion-something?), but that assignment was based on the same criteria that got us a /22 in v4 space. Should accepting a /44 in v6 not be equivalent, policy-wise, to accepting a /22 in v4? Thanks, John -- John York Information Technology | Network Administrator Phone: 615-399-7000 x:333 Griffin Technology 2030 Lindell Avenue Nashville, TN 37203 USA
RE: BGPMON Alert Questions
We have a registered prefix that was affected. The RPKI may have helped though; only one BGPMON peer saw the mis-originated route. Much better than being on the 10+ list. -Original Message- From: Randy Bush [mailto:ra...@psg.com] Sent: Wednesday, April 02, 2014 7:23 PM To: North American Network Operators' Group Subject: Re: BGPMON Alert Questions note joels careful use of 'injected'. imiho, 'hijacked' is perjorative implying evil intent. i very much doubt that is the case here. it looks much more like an accident. could we try to be less accusatory with our language. 'injected', 'mis-originated', ... would seem to descrive the situation. and, btw, how many of those whose prefixes were mis-originated had registered those prefixes in the rpki? randy This message and any attachments should be treated as confidential information of Griffin Technology, Inc.
Re: google troubles?
We saw the same thing, but seems to be cleared up now. All our providers that routed to Google addresses in ATL had the issue. We have one provider that lands on Google addresses in DFW, and it was working. ...And now I see that it isn't completely resolved. Some Google apps are still inaccessible via the Atlanta routes. On Wed, Jul 10, 2013 at 9:28 AM, Blair Trosper blair.tros...@gmail.comwrote: Seeing lots of reports of people unable to get to many Google services. Seems to be affecting Comcast users disproportionately. It's fine for me, but a lot of my staff are basically out of luck...but according to the Google Apps Status page, everything is fine. It's anecdotal, but it would seem like there's an issue based on these reports. Oh, and this: http://www.cnn.com/2013/07/10/tech/web/google-down/index.html Anyone know what's up? Fiber cut? DC outages? -- blair -- John York Information Technology | Network Administrator Phone: 615-399-7000 x:333 Griffin Technology 2030 Lindell Avenue Nashville, TN 37203 USA This message and any attachments should be treated as confidential information of Griffin Technology, Inc.
