- Test - lists.nanog.org

Huawei optical transport
by jmcmasters＠atlanticbb.net 07 Aug '09

07 Aug '09

Everyone, I was curious if anyone has used Huawei Optical transport. We are looking at OptiX OSN 6800A to upgrade our backbone to 10G. Pro's and Con's would be great if anyone has used the platform. Thanks, Jeremy

1 0

Conclusion: Smart hands in NYC area and new: Tokyo
by Elmar K. Bins 06 Aug '09

06 Aug '09

Hello altogether, I got a couple of freelancers and a few tips which companies to use. I thought I'd at least share the company recommendations, of which I'll have the bosses pick. One other thing - I'll be needing the same thing in Tokyo by the end of the year. If anyone has recommendations, please don't hesitate. I'm not shy of travelling, but I'd rather save time and money there... Yours, Elmar. Recommended companies: Team Silverback (www.teamsilverback.com) OnForce (www.onforce.com) Endeavor Xeta Blackbox Ledcor (www.ltscompany.com)

2 1

Re: DOS in progress ?
by Jorge Amodio 06 Aug '09

06 Aug '09

> http://status.twitter.com/ > > "We are defending against a denial-of-service attack, and will update status > again shortly." Perhaps the "puddy tat" finally got the bird :-)

1 0

RE: DOS in progress ?
by David Hubbard 06 Aug '09

06 Aug '09

From: Marshall Eubanks [mailto:tme@americafree.tv] > > Twitter is very flaky & slow to load today, but that is > hardly unusual. > > Do you have any other evidence ? > http://www.cnn.com/2009/TECH/08/06/twitter.attack/index.html

1 0

Level3 Routing Problems in Atlanta?
by Peter Beckman 06 Aug '09

06 Aug '09

I'm having a few troubles with L3 on this fine, dreadfully humid evening. HOST: max Loss% Snt Last Avg Best Wrst StDev 1. mph 0.0% 10 0.7 0.6 0.5 0.8 0.1 2. 10.1.41.89 0.0% 10 1.7 1.9 1.7 2.3 0.2 3. G2-0-3-891.WASHDC-LCR-08.ver 0.0% 10 1.8 1.8 1.7 1.9 0.1 4. so-1-1-0-0.RES-BB-RTR2.veriz 0.0% 10 2.3 2.4 2.2 2.6 0.1 5. 0.so-1-2-0.XL4.IAD8.ALTER.NE 0.0% 10 2.8 2.8 2.6 3.0 0.1 6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE 0.0% 10 4.8 4.6 2.9 4.9 0.6 7. te-11-3-0.edge1.Washington4. 0.0% 10 5.1 3.4 2.8 5.1 0.9 8. vlan69.csw1.Washington1.Leve 0.0% 10 3.6 6.7 3.5 14.6 4.1 9. ae-61-61.ebr1.Washington1.Le 0.0% 10 12.8 9.2 5.7 16.0 3.6 10. ae-2.ebr3.Atlanta2.Level3.ne 10.0% 10 19.9 23.9 19.9 31.8 4.1 11. ge-5-0-0-52.gar2.Atlanta1.Le 0.0% 10 21.4 21.3 21.0 21.8 0.2 12. COX-COMMUNI.gar2.Atlanta1.Le 0.0% 10 209.8 201.7 197.4 209.8 4.0 <-- ew 13. mrfddsrj01-ge710.rd.dc.cox.n 10.0% 10 230.3 230.5 223.9 234.1 3.4 14. 70.164.18.1 10.0% 10 233.3 231.7 225.1 236.7 4.0 Return trip: HOST: 70.164.19.xx Loss% Snt Last Avg Best Wrst StDev 1. 70.164.19.3 0.0% 20 0.2 0.2 0.2 0.4 0.0 2. wsip-70-168-111-17.dc.dc.cox 5.0% 20 11.2 17.7 1.6 97.1 28.5 3. mrfddsrj01-ge706.rd.dc.cox.n 10.0% 20 36.9 42.0 1.4 282.6 79.5 4. 68.1.1.121 0.0% 20 31.4 39.1 24.0 157.9 28.6 5. ae-2-52.edge2.Atlanta2.Level 5.0% 20 211.9 212.2 208.0 215.7 2.1 <-- ew 6. 0.so-1-1-0.BR2.ATL4.ALTER.NE 0.0% 20 214.4 213.7 209.0 224.7 3.8 7. 0.so-2-1-0.XT1.ATL4.ALTER.NE 0.0% 20 51.7 55.6 50.6 62.5 3.3 8. 0.so-6-2-0.ATL01-BB-RTR1.VER 0.0% 20 56.7 60.0 51.0 123.1 15.1 9. so-7-1-0-0.LCC1-RES-BB-RTR1- 0.0% 20 229.6 231.6 228.6 239.7 2.8 10. P14-0.WASHDC-LCR-01.verizon- 0.0% 20 51.5 50.3 46.5 59.0 2.5 11. P13-0.WASHDC-LCR-03.verizon- 0.0% 20 226.9 245.0 226.9 363.4 33.0 12. P12-0.WASHDC-LCR-05.verizon- 0.0% 20 229.3 231.7 225.6 236.5 3.1 13. P15-0.WASHDC-LCR-07.verizon- 5.0% 20 320.0 243.6 226.6 324.9 29.3 14. ??? 100.0 20 0.0 0.0 0.0 0.0 0.0 15. mph (verizon vios in DC) 5.0% 20 231.3 232.1 227.2 235.2 2.3 Anyone else see this? Know what's going on? My route is kind of silly... I'm in Northern VA on Verizon FIOS, about 2 physical miles from the IP on Cox. Thank goodness for the speed of light. --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman(a)angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------

2 1

Do you aggregate?
by Zartash Uzmi 06 Aug '09

06 Aug '09

Hi all, I hope most people on the list look at the routing table analysis reports. Excerpt from last week show about 292961 prefixes which after maximum aggregation can be reduced to 138493. I wonder how many of you do actually aggregate? If so, do you aggregate manually or using some algorithm? In either case (manual or automatic aggregation), how frequently do you aggregate? more frequent than the BGP updates frequency? If you aggregate, do you announce the aggregated prefixes or the original un-aggregated prefixes? how big is your network? (Tier-1, 2, 3, campus, etc.) I am hoping to get a few answers :) Regards, Zartash

1 0

Networking is IPC
by Scott Weeks 05 Aug '09

05 Aug '09

Changed the subject line... --- jmamodio(a)gmail.com wrote: > Read "Patterns in Network Architecture" by John Day. "A Return to Fundamentals", great book. "the Internet today is more like DOS, but what we need should be more like Unix" Great thing he didn't say Windows :-) ----------------------------------------- I like these: "networking is interprocess communication". (quoted from Metcalfe - 1972) "Q: So, how long should an address be? A: Processing the address should halt" Chapters 5-8 are the meat of naming and addressing and he has a LOT to say on the subjects... :-) scott

2 1

Re: Dan Kaminsky
by Scott Weeks 05 Aug '09

05 Aug '09

--- jmamodio(a)gmail.com wrote: From: Jorge Amodio <jmamodio(a)gmail.com> Sooner or later, we or the new generation of ietfers and nanogers, will need to start thinking about a new naming paradigm and design the services and protocols associated with it. The key question is, when we start? ------------------------------------------------ Read "Patterns in Network Architecture" by John Day. scott

2 1

RE: DNS hardening, was Re: Dan Kaminsky
by Skywing 05 Aug '09

05 Aug '09

That is, of course, assuming that SCTP implementations someday clean up their act a bit. I'm not so sure I'd suggest that they're really ready for "prime time" at this point. - S -----Original Message----- From: Douglas Otis <dotis(a)mail-abuse.org> Sent: Wednesday, August 05, 2009 11:13 To: John Levine <johnl(a)iecc.com> Cc: nanog(a)nanog.org <nanog(a)nanog.org> Subject: Re: DNS hardening, was Re: Dan Kaminsky On 8/5/09 9:48 AM, John Levine wrote: > Other than DNSSEC, I'm aware of these relatively simple hacks to add > entropy to DNS queries. > > 1) Random query ID > > 2) Random source port > > 3) Random case in queries, e.g. GooGLe.CoM > > 4) Ask twice (with different values for the first three hacks) and > compare the answers DNSSEC introduces vulnerabilities, such as reflected attacks and fragmentation related exploits that might poison glue, where perhaps asking twice might still be needed. Modern implementations use random 16 bit transaction IDs. Interposed NATs may impair effectiveness of random source ports. Use of random query cases may not offer an entropy increase in some instances. Asking twice, although doubling resource consumption and latency, offers an increase in entropy that works best when queried serially. Establishing SCTP as a preferred DNS transport offers a safe harbor for major ISPs. SCTP protects against both spoofed and reflected attack. Use of persistent SCTP associations can provide lower latency than that found using TCP fallback, TCP only, or repeated queries. SCTP also better deals with attack related congestion. Once UDP is impaired by EDNS0 response sizes that exceed reassembly resources, or are preemptively dropped as a result, TCP must then dramatically scale up to offer the resilience achieved by UDP anycast. In this scenario, SCTP offers several benefits. SCTP retains initialization state within cryptographically secured cookies, which provides significant protection against spoofed source resource exhaustion. By first exchanging cookies, the network extends server state storage. SCTP also better ensures against cache poisoning whether DNSSEC is used or not. Having major providers support the SCTP option will mitigate disruptions caused by DNS DDoS attacks using less resources. SCTP will also encourage use of IPv6, and improve proper SOHO router support. When SCTP becomes used by HTTP, this further enhances DDoS resistance for even critical web related services as well. -Doug

2 1

RE: Sprint/Verizon BGP
by Edward Brookhouse 05 Aug '09

05 Aug '09

Thanks All - problem resolved. From: Bhavini Mehta [mailto:bhavinim@gmail.com] Sent: Wednesday, August 05, 2009 3:01 PM To: ebroo(a)setuidzero.org Subject: Re: Sprint/Verizon BGP Hello, Are you still seeing the problem?? I see the route changed in our routing table 30 mins back and now we are seeing the best route via Verizon. I just wanted to reach out and see if you still needed someone from Sprint to look at it. Thanks On Wed, Aug 5, 2009 at 11:35 AM, Edward Brookhouse <ebroo(a)setuidzero.org> wrote: Hi all, Any Sprint BGP admins on this list can offer any thoughts on why Sprint connected networks are preferring my Sprint connection when they should be preferring my Verizon? I (Healthy Directions) am AS16387, two blocks 63.73.158.0/24 and 63.78.31.0/24, being announced by sprint and Verizon, preferred to Verizon(DS3) over Sprint 3MB. Verizon BGP admins think everything is ok, have not heard back from BGP4 at sprint. Any thoughts appreciated, off-list contact welcome. Edward ebroo(a)healthydirections.com

1 0