RE: Sigh. 16 years ago today.
Rodney thanks for posting; I really enjoyed reading it. These treasures keep alive the historical significance of those who realized this technology that most today take for granted. -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Rodney Joffe Sent: Thursday, October 16, 2014 12:42 AM To: NANOG Subject: Sigh. 16 years ago today. https://www.ietf.org/rfc/rfc2468.txt
VZW IPv6 routing issues?
Shot in the dark here, but we're starting to see complaints from a few VZW customers that can no longer access mail services we're providing on the usual IMAP and POP ports (secure or otherwise). It only seems to be happening for users that are getting IPv6 addresses for cellular data. Web traffic isn't an issue, just mail. Has anyone else seen this?
BCP38 wiki reminder
Thanks to several folks who've recently asked me to create accounts for them on the BCP38.info wiki. (We had to leave it on manual because we couldn't come up with a reasonable way to despam it, and were stuck on an older release; I think that might have changed now...) We welcome all contributions to the site, in the name of reducing untraceable DOS attacks on the greater Internet. I've filled in the articles for which I have first hand knowledge, but we still need contributions from people with experience running larger more complex edge networks, and also parts of the core. Got some free time this weekend? Here's your chance to be Smart and Helpful! Cheers, -- jr 'or whacky; whichever you prefer' a -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
Need a contact at Earthlink Business (AS 6983, formerly Deltacom) for routing issue
If someone from AS 6983 is on the list, please reach out to me off-list. AS 6983 is currently advertising a /24 from our space. Thanks, John
Re: Sigh. 16 years ago today.
On Oct 15, 2014, at 23:20 , Larry Sheldon wrote: > On 10/15/2014 23:42, Rodney Joffe wrote: >> https://www.ietf.org/rfc/rfc2468.txt >> > > I posted this to Facebook a while ago: > > From NANOG > > Subject: Sigh. 16 years ago today. > > https://www.ietf.org/rfc/rfc2468.txt > > [Ed. note: The man being remembered was important, and in ways, still is. But > I mention it also because it points out that whereas we bang our heads > against soul-less monoliths, it seems, in the early days it was a really > small, close-knit group that brought this Internet thing out of the labs and > stood it up and made it play in remarkably productive ways.] In many ways, today, it is a larger and more diverse group, but the bottom line is that behind all those peering relationships, NANOG conferences, ARIN meetings, etc. are a dedicated group of engineers just trying to keep it all functional. Owen > > -- > The unique Characteristics of System Administrators: > > The fact that they are infallible; and, > > The fact that they learn from their mistakes. > > > Quis custodiet ipsos custodes
Anyone from AS6983 here?
AS6983 is announcing a /24 out of space allocated to AS7922. Having trouble getting sorted out with 6983’s NOC. Thanks. route-server.phx1>show ip bgp 198.0.0.0/16 long BGP table version is 1479726026, local router ID is 67.17.81.28 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external Origin codes: i - IGP, e - EGP, ? - incomplete Network Next HopMetric LocPrf Weight Path *>i198.0.0.067.16.148.3736300 0 6983 ? * i 67.16.148.3736300 0 6983 ? * i198.0.0.0/16 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i *>i 67.16.148.3750199 0 7922 i * i 67.16.148.3750199 0 7922 i route-server.phx1> http://whois.arin.net/rest/net/NET-198-0-0-0-1 P.S. We have asked Level3 to block the announcement.
Re: Anyone from AS6983 here?
A few folks replied off=list. This has been resolved. Thanks. On 10/16/14, 4:39 PM, "Smith, Courtney" wrote: >AS6983 is announcing a /24 out of space allocated to AS7922. Having >trouble getting sorted out with 6983¹s NOC. Thanks. > >route-server.phx1>show ip bgp 198.0.0.0/16 long >BGP table version is 1479726026, local router ID is 67.17.81.28 >Status codes: s suppressed, d damped, h history, * valid, > best, i - >internal, > r RIB-failure, S Stale, m multipath, b backup-path, x >best-external >Origin codes: i - IGP, e - EGP, ? - incomplete > > Network Next HopMetric LocPrf Weight Path >*>i198.0.0.067.16.148.3736300 0 6983 ? >* i 67.16.148.3736300 0 6983 ? >* i198.0.0.0/16 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >*>i 67.16.148.3750199 0 7922 i >* i 67.16.148.3750199 0 7922 i >route-server.phx1> > >http://whois.arin.net/rest/net/NET-198-0-0-0-1 > > > >P.S. We have asked Level3 to block the announcement. >
Ashburn VA Colo
Good morning! I am interested in obtaining a small initial footprint for colo within the Ashburn VA area. Can anyone make a recommendation to include a cabinet or two? Alternatively, I am familiar with Equinix and would consider space from any existing customers in the Equinix facility with space to sell! If you want to contact me off-list for details, I can provide the details. Thanks!
Major Level3 Issues
Just had major outages on our Level3 connections across the country. (LA, TX, ORD) Anyone have any news / updates which can be shared? Looks like AT&T and XO had loss of connectivity to Level3? Thank you! Dean
Re: Major Level3 Issues
Dean, Best I have is from their portal: The IP NOC reports that a module failed on a device in Chicago, IL causing additional impact to IP services across Multiple Markets. The IP NOC has confirmed that the module initially failed and recovered prior to manual intervention. A short time later, the module failed again, restored of its own accord and continued to bounce thereafter. Services have since been restored and stable as of approximately 23:54 GMT. The equipment vendor is being engaged to assist in isolation efforts to determine a root cause and the IP NOC is continuing to monitor at this time. We rerouted away majority traffic from Level 3 and will leave it till late tonight or early morning. We experienced two major blips tonight. Jason On Oct 16, 2014, at 21:25, Dean Perrine wrote: > Just had major outages on our Level3 connections across the country. (LA, > TX, ORD) > > Anyone have any news / updates which can be shared? > > Looks like AT&T and XO had loss of connectivity to Level3? > > Thank you! > Dean
Anyone seeing issues with TWC inWI at the moment?
Might just be me but seeiing extrememly long delays to their web servers [root@storage ~]# curl http://www.timewarnercable.com/>here % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 331 100 3310 0 5 0 0:01:06 0:00:59 0:00:07 67 [root@storage ~]# traceroute to www.timewarnercable.com (71.74.42.231), 30 hops max, 60 byte packets 5 tge1-1-0-8.milzwift01r.midwest.rr.com (65.29.44.158) 33.204 ms 33.426 ms 33.509 ms 6 bu-ether18.cr0.chi30.tbone.rr.com (66.109.6.206) 36.901 ms 17.829 ms 23.836 ms 7 ae-0-0.cr0.chi10.tbone.rr.com (66.109.6.20) 37.020 ms 37.239 ms 40.098 ms 8 ge-5-0-0.ar1.cdp01.tbone.rr.com (66.109.10.221) 64.300 ms 64.687 ms 64.588 ms 9 66.109.10.73 (66.109.10.73) 44.083 ms 45.343 ms 45.534 ms 10 75.180.131.165 (75.180.131.165) 48.200 ms 48.925 ms 50.939 ms 11 75.180.131.229 (75.180.131.229) 64.520 ms 65.393 ms 65.155 ms 12 www.timewarnercable.com (71.74.42.231) 41.589 ms 35.222 ms 34.410 ms [root@storage ~]# wget http://www.timewarnercable.com/>here --2014-10-16 23:34:28-- http://www.timewarnercable.com/ Resolving www.timewarnercable.com... 71.74.42.231, 2001:1998:840:b001::7 Connecting to www.timewarnercable.com|71.74.42.231|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://www.timewarnercable.com/en/residential.html [following] --2014-10-16 23:35:07-- http://www.timewarnercable.com/en/residential.html Reusing existing connection to www.timewarnercable.com:80. HTTP request sent, awaiting response... 200 OK Length: 142374 (139K) [text/html] Saving to: “residential.html.2” 100%[==>] 142,374 710K/s in 0.2s 2014-10-16 23:35:07 (710 KB/s) - “residential.html.2” saved [142374/142374] Probably just me or poor residential folks , but just wondering. Sorry to bother! Thanks -Joe
