- NANOG - lists.nanog.org

Salt Lake NANOG peering
by Pete Kruckenberg 09 Apr '03

09 Apr '03

We're excited to host the June NANOG in Salt Lake, and give the NANOG crowd to enjoy a few beautiful days in Utah. I know how important it'll be to have good connectivity to your network while you're here in Utah. As a special offer to NANOG attendees, we have made an exception to our normally stringent peering policy to ensure your SSH and IRC sessions are optimized for NANOG (Ethereal, ettercap and Cain&Able performance will not affected). For a limited time, we are now accepting requests for peering at PAIX Palo Alto and Equinix Chicago. As an additional incentive, anyone who peers with us before May 1 will be able to keep that peering indefinitely, so respond quickly. Pete.

4 3

TWTelecom
by Peder Angvall 09 Apr '03

09 Apr '03

Anybody from TWTelecom on the list who might know of a problem in Dallas? > 60% of pings appear to be lost through their Dallas network. I've been on hold at the NOC for 20 minutes. Packets: Sent = 908, Received = 275, Lost = 633 (69% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 361ms, Average = 14ms 7 0.so-1-3-0.XL2.DFW9.ALTER.NET (152.63.99.214) [AS 701] 40 msec 40 msec 36 msec 8 POS7-0.GW10.DFW9.ALTER.NET (152.63.101.133) [AS 701] 40 msec 40 msec 36 msec 9 twtelecom-gw.customer.alter.net (65.208.11.194) [AS 701] 40 msec 40 msec 36 msec 10 core-01-ge-0-2-0-0.dlfw.twtelecom.net (168.215.54.85) [AS 4323] 40 msec * 40 msec 11 * * * 12 * * * 13 * * * 14 * 64-132-228-250.gen.twtelecom.net (64.132.228.250) [AS 4323] 44 msec 44 msec 15 64-132-228-6.gen.twtelecom.net (64.132.228.6) [AS 4323] 52 msec 48 msec 48 msec

2 1

Anyone in boston..
by haesu 08 Apr '03

08 Apr '03

Hi, Anyone from Boston here: Do any of you have the ability to provision/turn-up a T1 or fractional T3 dedicated internet service QUICKLY, before April 30th in Boston area? We've been under process of getting dedicated internet from Qwest here but the process with them has been delayed so much that this is starting to get frustrating, which makes us to now contemplate our other options... Please reply off-list. Thank you, -hc

1 0

RE: Leo Bicknell knows why I had to post this...
by Ben Buxton 08 Apr '03

08 Apr '03

> From: Valdis.Kletnieks(a)vt.edu [mailto:Valdis.Kletnieks@vt.edu] > > The rest of you can just consider it yet another thing adding to > address space consumption... > > http://news.bbc.co.uk/1/hi/technology/2917739.stm I'll be putting my lavatory rolls safely behind a NAT firewall thank you very much, lest they have 'holes' in them and arent easy to patch. :) Maybe they will support proxying via socks... BB

3 2

60/8 allocated to APNIC by IANA
by John L Crain 08 Apr '03

08 Apr '03

Hi Folks, This is a heads up to let you know that the IANA has allocated the following range of IPv4 addresses to APNIC. 60.0.0.0/8 A notation of the allocation has been made at <http://www.iana.org/assignments/ipv4-address-space>. The range 223/8 was at the same time returned to the IANA and it's status marked as IANA Reserved. You may wish to adjust your filters accordingly. -- Best regards, John Crain mailto:crain@iana.org

1 0

Bogon update 60/8 and 223/8
by Stephen Gill 08 Apr '03

08 Apr '03

[ Apologies to those who have received this post in other fora. ] IANA has received 223/8 *from* APNIC, and allocated 60/8 *to* APNIC. Thus 223/8 reverts to RESERVED (bogon) status and 60/8 moves to ALLOCATED status. The numerous Team Cymru bogon projects have been updated to reflect the following IANA allocation on April 08, 2003: 60/8 Apr 03 APNIC 223/8 Apr 03 IANA - Reserved NOTE WELL: This post includes an allocation and a DE-ALLOCATION. Please be sure to adjust your filters accordingly. IANA allocations change over time, so please check regularly to ensure you have the latest filters. The use of the bogon route-server will automate these updates for you and your network (see below). We do announce updates to the bogon projects to the FIRST community, as well as on lists such as NANOG, isp-routing, isp-security, isp-bgp, cisco-nsp, and bogon-announce. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not blindly apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/index.html> A quick summary of the documents and projects that have been updated include the following: HTTP <http://www.cymru.com/Bogons/> The Bogon List The Text Bogon List, Unaggregated The Text Bogon List, Aggregated Secure BIND Template Secure IOS Template (Cisco) Secure BGP Template (Cisco) Secure JUNOS Template (Juniper) Secure JUNOS BGP Template (Juniper) Ingress Prefix Filter Templates, Loose and Strict (Cisco) Ingress Prefix Filter Template, Loose and Strict (Juniper) BGP <http://www.cymru.com/BGP/bogon-rs.html> Bogon route-server[*] RADb <http://www.radb.net/cgi-bin/radb/whois.cgi?obj=fltr-bogons> <http://www.radb.net/cgi-bin/radb/whois.cgi?obj=fltr-unallocated> <http://www.radb.net/cgi-bin/radb/whois.cgi?obj=fltr-martian> fltr-unallocated fltr-martian fltr-bogons DNS <http://www.cymru.com/Bogons/index.html#dns> Bogon (bogons.cymru.com) zone Monitoring <http://www.cymru.com/BGP/> Bogon prefix monitoring [*] All of the bogon peers have received the appropriate BGP prefix updates. Please feel free to contact Team Cymru with any comments, questions, or concerns. Thanks! Steve, for Team Cymru. -- Team Cymru http://www.cymru.com/About/teamcymru.html ASSERT(coffee != empty);

1 0

Anyone in Calgary?
by Alex Rubenstein 08 Apr '03

08 Apr '03

I need some hands in Calgary, urgently.. anyone help out? -- Alex Rubenstein, AR97, K2AHR, alex(a)nac.net, latency, Al Reuben -- -- Net Access Corporation, 800-NET-ME-36, http://www.nac.net --

1 0

timewarner telecom experiences ?
by matthew zeier 08 Apr '03

08 Apr '03

Looking at getting an GigE from Time Warner Telecom - having never used them, I'm hoping someone can give me insight into their connectivity. Thanks. -- matthew zeier - "Curiosity is a willing, a proud, an eager confession of ignorance." - Leonard Rubenstein

1 0

AS 5547 leaks 80.0.0.0/8 and 2.0.0.0/8
by Kai Schlichting 08 Apr '03

08 Apr '03

AS 5547 currently leaks 80.0.0.0/8 and 2.0.0.0/8 (IANA unassigned). As it appears, only Oregon-IX (of the 6-7 route-servers I looked at) seems to accept a larger number of routes from that AS right now, many seem to be filtering this AS at this point. Network Next Hop Metric LocPrf Weight Path *> 2.0.0.0 167.142.3.6 0 5056 701 3491 20485 5547 ? *> 80.0.0.0 167.142.3.6 0 5056 701 3491 20485 5547 ? I think someone should work on AS 3491 (cais.net) with a mallet for running no inbound prefix filtering with AS 20485 (transtelecom.net, a russian ISP, one that can apparently be trusted even less than CAIS) - a situation that calls for instant de-peering, if you ask me. Also: 2.0.0.0/8 from AS: 5547 (upstreams: 20485) 80.0.0.0/8 from AS: 5547 (upstreams: 20485) 195.161.13.0/24 from AS: 5547 (upstreams: 20485) 195.161.19.0/24 from AS: 5547 (upstreams: 20485) 195.161.68.0/24 from AS: 5547 (upstreams: 20485) 195.161.236.0/24 from AS: 5547 (upstreams: 20485) 195.161.236.0/22 from AS: 5547 (upstreams: 20485) 195.161.237.0/24 from AS: 5547 (upstreams: 20485) 195.161.238.0/24 from AS: 5547 (upstreams: 20485) 195.208.8.0/24 from AS: 5547 (upstreams: 20485) 195.208.8.0/21 from AS: 5547 (upstreams: 20485) 195.208.10.0/24 from AS: 5547 (upstreams: 20485) 195.208.11.0/24 from AS: 5547 (upstreams: 20485) 195.208.12.0/24 from AS: 5547 (upstreams: 20485) 195.208.13.0/24 from AS: 5547 (upstreams: 20485) 195.208.14.0/24 from AS: 5547 (upstreams: 20485) 213.59.129.0/24 from AS: 5547 (upstreams: 20485) 213.59.130.0/24 from AS: 5547 (upstreams: 20485) 213.59.131.0/24 from AS: 5547 (upstreams: 20485) 213.59.132.0/24 from AS: 5547 (upstreams: 20485) 213.59.133.0/24 from AS: 5547 (upstreams: 20485) 213.59.134.0/24 from AS: 5547 (upstreams: 20485) 213.59.135.0/24 from AS: 5547 (upstreams: 20485) 213.59.234.0/24 from AS: 5547 (upstreams: 20485) 217.107.38.0/24 from AS: 5547 (upstreams: 20485) 217.107.39.0/24 from AS: 5547 (upstreams: 20485)

1 0

msnbc
by hostmaster 08 Apr '03

08 Apr '03

Can someone explain to me why: msnbc.com = 207.46.150.20 = Microsoft Corp. while www.msnbc.com = 199.232.61.145 = Cambridge Entrepreneurial It's really getting confusing .... -Bert PS: no hard feelings if replies are off list.

1 0