July 2007 - Test - lists.nanog.org

[urgent assistance] 198.32.0.0/16 - Disappeared...
by Fergie 31 Aug '07

31 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paging Bill Manning... Unfortunately, we've tried to reach Bill, as well as other folks at EP.NET to no avail, and this is impacting us quite negatively. [snip] Not available in any routing tables I have access to or any of the looking glasses from http://www.nanog.org/lookingglass.html. this is significant because any in-addr blocks that are authoritative @ flag.ep.net and dot.ep.net will now suffer from reverse name resolution issues. - From ATT route server: route-server>sh ip bgp 198.32.4.13 % Network not in table - From CerfNET route server: route-server>sh ip bgp 198.32.4.13 % Network not in table Allstream Toronto: route-server.east>sh ip bgp 198.32.4.13 % Network not in table This has been a problem since yesterday evening. [snip] FYI, some of our address space has been sub-allocated via EP.net and relies on it's reachability: [DOMAIN whois information for EP.NET ] Domain Name: EP.NET Namespace: ICANN Unsponsored Generic TLD - http://www.icann.org TLD Info: See IANA Whois - http://www.iana.org/root-whois/net.htm Registry: VeriSign, Inc. - http://www.verisign-grs.com Registrar: NETWORK SOLUTIONS, LLC. - http://www.networksolutions.com Whois Server: whois.networksolutions.com Name Server[whois+dns with ip] DOT.EP.NET 198.32.2.10 Name Server[from whois+dns, whois ip]: DOT.EP.NET 2001:478:6:0:230:48FF:FE22:6A29 Name Server[whois+dns with ip] FLAG.EP.NET 198.32.4.13 Updated Date: 11-Jan-2007 Creation Date: 09-Dec-1994 Expiration Date: 08-Dec-2012 Status: clientTransferProhibited [whois.networksolutions.com] Welcome to the Network Solutions Registrar WHOIS Server. The IP address from which you have visited the Network Solutions Registrar WHOIS database is contained within a list of IP addresses that may have failed to abide by Network Solutions' WHOIS policy. Failure to abide by this policy can adversely impact our systems and servers, preventing the processing of other WHOIS requests. To see the Network Solutions WHOIS Policy, click on or copy and paste the following URL into your browser: http://www.networksolutions.com/whois/index.jhtml If you feel that you have received this message in error, please contact us at: whoisquery(a)networksolutions.com and include the following information: Whois Query: domain ep.net YOUR IP address is 216.151.198.186 Date and Time of Query: Fri May 11 21:39:55 EDT 2007 Reason Code: CE [whois.networksolutions.com] Please contact me off-list is you have any inisght into this. Thanks, - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.1 (Build 1012) wj8DBQFGRRydq1pz9mNUZTMRAt1RAJ0daUTj2zsy4yw9Yq83mTgQdYBXcQCg+lgC Hs2XTn1hp42IjMLXmTfU4Vs= =D8x5 -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

5 6

Telenor AS8210 and AS8434 technical contact?
by Anonymous List User 01 Aug '07

01 Aug '07

I must apologize for posting this anonymously. Can anybody provide me with a technical contact at Telenor (AS8210 and AS8434) to discuss European Teleport / VSAT network issues? Thanks...

2 1

Re: An Internet IPv6 Transition Plan
by Chad Oleary 31 Jul '07

31 Jul '07

I'm wondering if we should really be considering a "transition" plan at this point? From what I can see, there will be many IPv4 only networks around for many years to come. The technology doesn't have an expiration date. Rather than focusing on "transitioning" every network from v4 to v6, shouldn't this draft focus on how an "initial implementation of v6" is going to interop with v4 as we know it today? Personally, I see v6 as something that needed and desired by the certain groups. However, when looking at the enterprise, for example, better solutions are needed for things like multi-homing, last I checked. IPv4 will get more expensive as time goes on, but some will be willing to pay that price. Perhaps the biggest challenge, IMO, in this much more dynamic network, is DNS. How do I (or my new vendor) readdress every node at my site, and actually know what device has what address? rtadvd doesn't do DNS updates. DHCPv6 doesn't even hand out addresses. I've seen host-based approaches, is that the answer? How does all this happen securely? DNSSEC comes to mind, but that's a whole different story. Add, since a host can have many preferred addresses, which to use? How do deprecated addresses get withdrawn from DNS? I think a more successful approach would be to address how we plan to add v6 to the current network. Perhaps a transition plan is appropriate for some networks. But, I don't think this is a one-size fits all issue. This is the part that I have issue with: 2.3.4 Service Providers area MAY continue to offer IPv4-based Internet connectivity to their customers. Organizations MAY continue to use IPv4-based Internet connectivity. Organizations MAY remove IPv4-based Internet connectivity from Internet-facing servers. If I'm an IPv4 only site outside of this "perfect world", I just lost connectivity to parts those that moved to IPv6. Not everyone will follow this plan, and this will happen. For now, we need to learn how to co-exist. Thanks for your time, Chad

19 41

New IPv4 blocks allocated to RIPE NCC
by Alex Le Heux 31 Jul '07

31 Jul '07

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 94/8 and 95/8 from the IANA in July 2007. We will begin allocating from these ranges in the near future. The minimum allocation size from these two /8s has been set at /21. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Please also note that two "pilot" prefixes are being announced from each /8. These prefixes are: 95.192.0.0/16 95.255.248.0/21 They all originate in AS12654. The following pingable addresses are available in these blocks: 95.192.0.1 95.255.248.1 More information on this "pilot" activity is available in the document "De-Bogonising New Address Blocks", which can be found at: http://www.ripe.net/ripe/docs/ripe-351.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator

1 0

secure.net admin, regarding ddos
by payam Chychi 30 Jul '07

30 Jul '07

Hey, Sorry for the off topic here but I was hoping to find an admin/engineer from secure.net. Either they have a lot of compromised boxes on their network or they have kids working for them that love to ddos. cheers -Payam

1 0

94/8, 95/8 allocated to the RIPE NCC
by Leo Vegoda 29 Jul '07

29 Jul '07

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to the RIPE NCC in July 2007: 94/8 and 95/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, -- Leo Vegoda IANA Numbers Liaison

1 0

Netlantis - Routing Table Geoanalysis
by Philippe Bourcier 29 Jul '07

29 Jul '07

Hi, Sorry for the cross-post. The Netlantis team (Pascal Gloor and me) is pleased to announce a new BGP routing tables visualization project. This project is called Routing Table Geoanalysis and aims at representing various statistics based on the analysis of a BGP routing table. The result of this analysis is a poster-size computer-generated image (12+ Megapixels) which you can easily print. Project's URL : http://rtg.netlantis.org/ The statistics for each routing table we analyse are : - The distribution across continents (or more precisely geo-political areas) of the total number of IP addresses announced - The number of IP addresses announced for 100 inhabitants of these areas - The number of routes, IP addresses and the average number of IP addresses per route - The main upstream AS's share in the routing table (in number of IP) and the geographic distribution of IP addresses announced through or by them - The distribution of AS path length by continent - The prefix size distribution The geo-political areas (I'm abusively calling continents) used for the statistics are : Africa, Asia, Central America, Europe, Middle-East, North America, Oceania and South America. When it's relevant, I also use the area World which is simply a way to display the average statistics for the whole routing table. The posters (and statistics) will be automatically updated every month. English not being my native language, I'll be happy if some people can help me fix or improve my wording and explanations so they can be better understood, especially on this page: http://rtg.netlantis.org/?info=rtg I'm thinking about adding a page on which you could automatically upload (via curl) your clogin -c "term len 0\rsh ip bgp" every month so that any AS could also be listed without the need to peer anywhere... tell me if you are interested by this feature. Thanks to routeviews for providing the routing tables and to our sponsors : IP-MAN, OVH and MaxMind. ps: If you want to sponsor Netlantis, we found a piece of hardware which might help us return in a short time to production, the thing is a DDRAM-based hard-disk (more details on my blog), contact me in private if you can help us get one. Sincerely, Philippe Bourcier web : http://sysctl.org/ blog : http://netlantis.blogspot.com

1 0

Cogent outage details?
by Scott Francis 27 Jul '07

27 Jul '07

am receiving word that Cogent has been the victim of "hardware problems on our backbone causing latency and packet loss to customers on the east coast". I did manage to get a master ticket number (608503), but I'm curious if anybody out there (perhaps an actual Cogent customer) has more details - backhoe? operator error? evaporating subatomic black hole? -- darkuncle(a){gmail.com,darkuncle.net} || 0x5537F527 encrypted email to the latter address please http://darkuncle.net/pubkey.asc for public key

6 5

Re: Why do we use facilities with EPO's?
by George William Herbert 27 Jul '07

27 Jul '07

>Seems like the EPO should be a logical AND with the fire alarm system - >it only works AFTER you have an existing fire alarm in the building. No, no. If the fire alarm system fails, the fire responders need to be able to hit the EPO and be sure that it works anyways. It has to be an absolute - firefighters have to know that the thing they hit was the only, and right, thing, and that they aren't going to die because they sprayed water on an energized but on fire electrical system backed by a 120 KVA UPS or some such. Also, one should not wait for fire alarms to go off to de-energize a room in the clear presence of an electrical fire or major short. Preventing the fire is better than putting it out. Telco central offices are somewhat of an exception in many ways, but just about anyone else should have a real live EPO. -george william herbert gherbert(a)retro.com

5 7

RE: Where did freeipdb IP utility site go?
by Brandon Butterworth 27 Jul '07

27 Jul '07

> Are there any "good" tools for IPv6 address management? "There's so many bits they don't need managing" brandon

4 3