June 2008 - Test - lists.nanog.org

Bandcon Transport Services..
by Christian 16 Jun '08

16 Jun '08

Anyone here use Bandcon's transport services? Positive/Negative experiences, any feedback would be helpful.. Thanks ck

2 1

RE: Best utilizing fat long pipes and large file transfer
by Skywing 16 Jun '08

16 Jun '08

It's 10 half-open (SYN_SENT) outbound TCP connections as I recall. - S -----Original Message----- From: goemon(a)anime.net <goemon(a)anime.net> Sent: Monday, June 16, 2008 12:26 To: Glen Turner <gdt(a)gdt.id.au> Cc: nanog(a)merit.edu <nanog(a)merit.edu> Subject: Re: Best utilizing fat long pipes and large file transfer On Mon, 16 Jun 2008, Glen Turner wrote: > Then there's the deliberate nobbling of the TCP implementation, > such as the restriction to ten of connections to Windows Xp SP3. > Apparently you're meant to buy Windows Server if you are running > P2P applications :-) are you quite sure it is *10 tcp connections*? have you tested this? -Dan

1 0

DNS problems to RoadRunner - tcp vs udp
by Mark Price 16 Jun '08

16 Jun '08

I have seen intermittent problems on some client windows servers sending to rr.com recently. For example, the MX hosts for triad.rr.com are: # dig -t mx triad.rr.com ;; QUESTION SECTION: ;triad.rr.com. IN MX ;; ANSWER SECTION: triad.rr.com. 1609 IN MX 10 hrndva-smtpin01.mail.rr.com. triad.rr.com. 1609 IN MX 20 hrndva-smtpin02.mail.rr.com. The authoritative nameservers for mail.rr.com: # dig -t ns mail.rr.com ;; QUESTION SECTION: ;mail.rr.com. IN NS ;; ANSWER SECTION: mail.rr.com. 14204 IN NS cdptpa-admin02.mail.rr.com. mail.rr.com. 14204 IN NS hrndva-admin01.mail.rr.com. mail.rr.com. 14204 IN NS hrndva-admin02.mail.rr.com. mail.rr.com. 14204 IN NS cdptpa-admin01.mail.rr.com. All 4 of those queries will answer a UDP DNS query for host record hrndva-smtpin01.mail.rr.com. However, the hrndva-admin01.mail.rr.com and hrndva-admin02.mail.rr.com servers do not respond to TCP queries at all. Example: # dig hrndva-smtpin01.mail.rr.com @hrndva-admin01.mail.rr.com +tcp ; <<>> DiG 9.3.3rc2 <<>> hrndva-smtpin01.mail.rr.com @hrndva-admin01.mail.rr.com +tcp ; (1 server found) ;; global options: printcmd ;; connection timed out; no servers could be reached >From what I have read, public DNS servers should support both UDP and TCP queries. TCP queries are often used when a UDP query fails, or if the answer is over a certain length. Any clues would be appreciated. Mark -- Mark Price Tranquil Hosting www.tqhosting.com

24 33

Single IP routing problems through Level3
by Matt Palmer 15 Jun '08

15 Jun '08

We're seeing some really weird issues with connections that go through / to Level3 IP space. Basically, certain "pairs" of IPs (particular L3 IPs coupled with particular IPs of ours) have dodgy/nonexistent connectivity, but if you change the IP at either end everything's hunky dory. I've sniffed (from both ends) pings going from a host in L3 space to our end and seen the pings arrive at our end and head back in the direction of L3, but they never get to their destination. Traceroutes from L3 stop at the next-to-last hop, while traceroutes back get to the hop before L3 space and stop. All of this behaviour is source/dest *pair* specific -- if I ping/traceroute from another address (in the same netblock as the problematic IP, so all the same equipment is involved) at either end, or to another address (again, same netblock) at either end, it all works again. I've got two questions: 1) Has anyone else seen similar behaviour from L3 (or other providers, even), so I know I'm not going mad? 2) What sort of configuration problem or software bug would cause this sort of problem to occur? If it was an IP blacklist (or even a block routing issue) anywhere along the line, surely it wouldn't be sensitive to changing the other end's address to another one in the same /24? Any insight/anecdotes/etc would be greatly appreciated, as it's starting to do my head in. Just knowing I'm not alone with this insanity would be nice at this point. <grin> If it makes any difference, the blocks I'm working from at my end are Internap, in 74.201.254.0/23 (we don't have all of it, just most of it), while the far end is 8.12.35.0/24. - Matt

4 4

Re: Single IP routing problems through Level3
by Jon Wolberg 15 Jun '08

15 Jun '08

I've seen the exact same symptoms before with another provider and it was a L3 Port-Channel that was not balanced properly due to a link being down which wasn't detected as such. It was also causing very sporadic latency spikes and dropped packets. Jon ----- Original Message ----- From: "Matt Palmer" <mpalmer(a)hezmatt.org> To: nanog(a)nanog.org Sent: Sunday, June 15, 2008 10:39:56 AM GMT -05:00 US/Canada Eastern Subject: Re: Single IP routing problems through Level3 On Sun, Jun 15, 2008 at 11:12:25AM -0300, Rubens Kuhl Jr. wrote: > 1) I've seen this behavior before; you are not alone in the universe. Thank $DEITY for that. <grin> > 2) Most likely there is a balanced channel on the path, either L3 or > L2, and one of the links in the bundle is dead but has not been > detected as such. A multiple-link bundle which is load balanced by source/destination pair with an undetected dud link? I hadn't thought of that, but it does make an *awful* lot of sense. (Although, not being a big-network transit kinda person, I don't know if such a thing actually exists <grin>) I'll mention it (or ask about it) as a possibility next time I talk to the relevant people, though. Thanks, - Matt > On Sun, Jun 15, 2008 at 11:01 AM, Matt Palmer <mpalmer(a)hezmatt.org> wrote: > > We're seeing some really weird issues with connections that go through / to > > Level3 IP space. Basically, certain "pairs" of IPs (particular L3 IPs > > coupled with particular IPs of ours) have dodgy/nonexistent connectivity, > > but if you change the IP at either end everything's hunky dory. > > > > I've sniffed (from both ends) pings going from a host in L3 space to our end > > and seen the pings arrive at our end and head back in the direction of L3, > > but they never get to their destination. Traceroutes from L3 stop at the > > next-to-last hop, while traceroutes back get to the hop before L3 space and > > stop. > > > > All of this behaviour is source/dest *pair* specific -- if I ping/traceroute > > from another address (in the same netblock as the problematic IP, so all the > > same equipment is involved) at either end, or to another address (again, > > same netblock) at either end, it all works again. > > > > I've got two questions: > > > > 1) Has anyone else seen similar behaviour from L3 (or other providers, > > even), so I know I'm not going mad? > > > > 2) What sort of configuration problem or software bug would cause this sort > > of problem to occur? If it was an IP blacklist (or even a block routing > > issue) anywhere along the line, surely it wouldn't be sensitive to > > changing the other end's address to another one in the same /24? > > > > Any insight/anecdotes/etc would be greatly appreciated, as it's starting to > > do my head in. Just knowing I'm not alone with this insanity would be nice > > at this point. <grin> > > > > If it makes any difference, the blocks I'm working from at my end are > > Internap, in 74.201.254.0/23 (we don't have all of it, just most of it), > > while the far end is 8.12.35.0/24.

1 0

Re: NANOG Digest, Vol 5, Issue 33
by Paul Dowles 15 Jun '08

15 Jun '08

-----Original Message----- From: nanog-request(a)nanog.org Date: Sat, 14 Jun 2008 21:54:35 To: <nanog(a)nanog.org> Subject: NANOG Digest, Vol 5, Issue 33 Send NANOG mailing list submissions to nanog(a)nanog.org To subscribe or unsubscribe via the World Wide Web, visit http://mailman.nanog.org/mailman/listinfo/nanog or, via email, send a message with subject or body 'help' to nanog-request(a)nanog.org You can reach the person managing the list at nanog-owner(a)nanog.org When replying, please edit your Subject line so it is more specific than "Re: Contents of NANOG digest..." Today's Topics: 1. RE: [NANOG] Introducing latency for testing? (Frank Bulk - iNAME) 2. Re: .255 addresses still not usable after all these years? (Greg VILLAIN) 3. Re: DNS problems to RoadRunner - tcp vs udp (Scott McGrath) 4. Re: DNS problems to RoadRunner - tcp vs udp (Jeroen Massar) 5. Re: [NANOG] Introducing latency for testing? (Chris Marlatt) 6. Re: [NANOG] Introducing latency for testing? (Joel Jaeggli) 7. Re: DNS problems to RoadRunner - tcp vs udp (Scott McGrath) 8. Re: DNS problems to RoadRunner - tcp vs udp (Simon Leinen) 9. Re: DNS problems to RoadRunner - tcp vs udp (Jeroen Massar) ---------------------------------------------------------------------- Message: 1 Date: Sat, 14 Jun 2008 13:34:53 -0500 From: "Frank Bulk - iNAME" <frnkblk(a)iname.com> Subject: RE: [NANOG] Introducing latency for testing? To: "'Mike Lyon'" <mike.lyon(a)gmail.com>, "NANOG" <nanog(a)merit.edu> Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAACMh0iCc5e/TLORNwsUDcWNAQAAAAA=(a)iname.com> Content-Type: text/plain; charset="us-ascii" It's not free, but at a recent trade show I did see what appeared to be an affordable unit from Apposite Technologies (apposite-tech.com) And there's always PacketStorm. Frank -----Original Message----- From: Mike Lyon [mailto:mike.lyon@gmail.com] Sent: Friday, May 02, 2008 3:13 PM To: NANOG Subject: [NANOG] Introducing latency for testing? So I want to mimic some latency in a test network for DB replication. I am wondering what other's have used for this? Obviously, the best way to would be to actually have one box across the US or across the globe to actually test against but what if you don't have that? Are there any GPL software router solutions that would allow you to tweak the latency in between the two test boxes? Thanks in advance. -Mike _______________________________________________ NANOG mailing list NANOG(a)nanog.org http://mailman.nanog.org/mailman/listinfo/nanog ------------------------------ Message: 2 Date: Sat, 14 Jun 2008 20:33:21 +0200 From: Greg VILLAIN <nanog(a)grrrrreg.net> Subject: Re: .255 addresses still not usable after all these years? To: nanog(a)nanog.org Message-ID: <A2776BAD-491D-4F3D-9645-02EC7492E1FB(a)grrrrreg.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Jun 14, 2008, at 12:26 AM, Mike Lewinski wrote: > David Hubbard wrote: >> I remember back in the day of old hardware and operating >> systems we'd intentionally avoid using .255 IP addresses >> for anything even when the netmask on our side would have >> made it fine, so I just thought I'd try it out for kicks >> today. From two of four ISP's it worked fine, from Verizon >> FIOS and Road Runner commercial, it didn't. So I guess >> that old problem still lingers? > > The TCP/IP stack in Windows XP is broken in this regard, possibly in > Vista as well, though I've yet to have the displeasure of finding > out. I have a router with a .255 loopback IP on it. My Windows XP > hosts cannot SSH to it. The specific error that Putty throws is > "Network error: Cannot assign requested address". > > At least if I ever need to completely protect a device from access > by Windows users, I have a good option :) > > Mike From what I recall, Microsoft's stack was based on the only free one they could afford back in the Trumpet/Winsock days, namely BSD's. It is either dependent on how the stack is integrated, or it simply implies that BSD's stack is(was) also broken (I'd tend to doubt that). Also, Vista's stack was supposed to have been re-developed from scratch, never checked it. Greg VILLAIN ------------------------------ Message: 3 Date: Sat, 14 Jun 2008 16:40:10 -0400 From: Scott McGrath <mcgrath(a)fas.harvard.edu> Subject: Re: DNS problems to RoadRunner - tcp vs udp To: Randy Bush <randy(a)psg.com> Cc: nanog(a)merit.edu Message-ID: <48542CAA.5010503(a)fas.harvard.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Not to toss flammables onto the pyre. BUT there is a large difference from what the RFC's allow and common practice. In our shop TCP is blocked to all but authoratative secondaries as TCP is sinply too easy to DoS a DNS server with. We simply don't need a few thousand drones clogging the TCP connection table all trying to do zone transfers ( yes it happened and logs show drones are still trying ) For a long time there has been a effective practice of UDP == resolution requests TCP == zone transfers It would have been better if a separate port had been defined for zone transfers as that would obviate the need for a application layer gateway to allow TCP transfers so that zone transfers can be blocked and resolution requests allowed for now all TCP is blocked. Now just because someone has a bright idea they drag out a 20 y/o RFC and say SEE, SEE you must allow this because the RFC says so all the while ignoring the 20 years of operational discipline that RFC was written when the internet was like the quad at college everyone knew one and other and we were all working towards a common goal of interoperability and open systems , These days the net is more like a seedy waterfront after midnight where criminal gangs are waiting to ambush the unwary and consequently networks need to be operated from that standpoint. At the University networking level it is extremely difficult as we need to maintain a open network as much as possible but protect our infrastructure services so that they have 5 nines of availability back in the day a few small hosts would serve DNS nicely and we did not have people trying to take them down and/or infecting local hosts and attempting DHCP starvation attacks. And no we are not at the 5 nines level but we are working on it. - Scott Randy Bush wrote: >> If my server responded to TCP queries from anyone other than a secondary >> server, I would be VERY concerned. >> > > you may want to read the specs > > randy > ------------------------------ Message: 4 Date: Sat, 14 Jun 2008 22:47:47 +0200 From: Jeroen Massar <jeroen(a)unfix.org> Subject: Re: DNS problems to RoadRunner - tcp vs udp To: Scott McGrath <mcgrath(a)fas.harvard.edu> Cc: nanog(a)merit.edu Message-ID: <48542E73.9070109(a)spaghetti.zurich.ibm.com> Content-Type: text/plain; charset="iso-8859-1" Scott McGrath wrote: [..] > For a long time there has been a effective practice of > > UDP == resolution requests > TCP == zone transfers WRONG. TCP is there as a fallback when the answer of the question is too large. Zone transfer you can limit in your software. If you can't configure your dns servers properly then don't run DNS. Also note that botnets have much more effective ways of taking you out. And sometimes domains actually require TCP because there are too many records for a label eg http://stupid.domain.name/node/651 If you are thus blocking TCP for DNS resolution you suddenly where blocking google and thus for some people "The Internet". Also see: http://homepages.tesco.net/J.deBoynePollard/FGA/dns-edns0-and-firewalls.html (Which was the second hit for google(EDNS0) after a link to RFC2671) Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: OpenPGP digital signature Url : http://mailman.nanog.org/pipermail/nanog/attachments/20080614/8dc85bfe/atta… ------------------------------ Message: 5 Date: Sat, 14 Jun 2008 16:47:32 -0400 From: Chris Marlatt <cmarlatt(a)rxsec.com> Subject: Re: [NANOG] Introducing latency for testing? To: frnkblk(a)iname.com Cc: NANOG <nanog(a)merit.edu> Message-ID: <48542E64.3000704(a)rxsec.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Frank Bulk - iNAME wrote: > It's not free, but at a recent trade show I did see what appeared to be an > affordable unit from Apposite Technologies (apposite-tech.com) And there's > always PacketStorm. > > Frank > > -----Original Message----- > From: Mike Lyon [mailto:mike.lyon@gmail.com] > Sent: Friday, May 02, 2008 3:13 PM > To: NANOG > Subject: [NANOG] Introducing latency for testing? > > So I want to mimic some latency in a test network for DB replication. > I am wondering what other's have used for this? Obviously, the best > way to would be to actually have one box across the US or across the > globe to actually test against but what if you don't have that? Are > there any GPL software router solutions that would allow you to tweak > the latency in between the two test boxes? > > Thanks in advance. > > -Mike > > _______________________________________________ > NANOG mailing list > NANOG(a)nanog.org > http://mailman.nanog.org/mailman/listinfo/nanog > > IIRC ipfw can do this using dummynet and the delay directive. Regards, Chris ------------------------------ Message: 6 Date: Sat, 14 Jun 2008 14:08:25 -0700 From: Joel Jaeggli <joelja(a)bogus.com> Subject: Re: [NANOG] Introducing latency for testing? To: Chris Marlatt <cmarlatt(a)rxsec.com> Cc: NANOG <nanog(a)merit.edu> Message-ID: <48543349.7060400(a)bogus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Chris Marlatt wrote: > Frank Bulk - iNAME wrote: >> It's not free, but at a recent trade show I did see what appeared to >> be an >> affordable unit from Apposite Technologies (apposite-tech.com) And >> there's >> always PacketStorm. >> >> Frank >> >> -----Original Message----- >> From: Mike Lyon [mailto:mike.lyon@gmail.com] Sent: Friday, May 02, >> 2008 3:13 PM >> To: NANOG >> Subject: [NANOG] Introducing latency for testing? >> >> So I want to mimic some latency in a test network for DB replication. >> I am wondering what other's have used for this? Obviously, the best >> way to would be to actually have one box across the US or across the >> globe to actually test against but what if you don't have that? > boxes across the globe have the property of being somewhat less deterministic than you'd like if you need repeatability. > IIRC ipfw can do this using dummynet and the delay directive. it will also do jitter and drop rate... to wit, it's exactly what is need here. there are analogous tools for iptables based platforms. ------------------------------ Message: 7 Date: Sat, 14 Jun 2008 17:18:38 -0400 From: Scott McGrath <mcgrath(a)fas.harvard.edu> Subject: Re: DNS problems to RoadRunner - tcp vs udp To: Jeroen Massar <jeroen(a)unfix.org> Cc: nanog(a)merit.edu Message-ID: <485435AE.8060609(a)fas.harvard.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed There is no call for insults on this list - Rather thought this list was about techincal discussions affecting all of us and keeping DNS alive for the majority of our customers certainly qualifies. We/I am more than aware of the DNS mechanisms and WHY there are there trouble is NO DNS server can handle directed TCP attacks even the root servers crumbled under directed botnet activity and we have taken the decision to accept some collateral damage in order to keep services available. We are a well connected university network with multi-gigabit ingress and egress with 10G on Abilene so we try to protect the internet from attacks originating within our borders AND we really feel the full wrath of botnets as we do not have a relatively slow WAN link to buffer the effects. Yes - we are blocking TCP too many problems with drone armies and we started about a year ago when our DNS servers became unresponsive for no apparent reason. Investigation showed TCP flows of hundreds of megabits/sec and connection table overflows from tens of thousands of bots all trying to simultaneously do zone transfers and failing tried active denial systems and shunning with limited effectiveness. We are well aware of the host based mechanisms to control zone information, Trouble is with TCP if you can open the connection you can DoS so we don't allow the connection to be opened and this is enforced at the network level where we can drop at wire speed. Open to better ideas but if you look at the domain in my email address you will see we are a target for hostile activity just so someone can 'make their bones'. Also recall we have a comittment to openess so we would like to make TCP services available but until we have effective DNS DoS mitigation which can work with 10Gb links It's not going to happen. - Scott Jeroen Massar wrote: > Scott McGrath wrote: > [..] >> For a long time there has been a effective practice of >> >> UDP == resolution requests >> TCP == zone transfers > > WRONG. TCP is there as a fallback when the answer of the question is > too large. Zone transfer you can limit in your software. If you can't > configure your dns servers properly then don't run DNS. > Also note that botnets have much more effective ways of taking you out. > > And sometimes domains actually require TCP because there are too many > records for a label eg http://stupid.domain.name/node/651 > If you are thus blocking TCP for DNS resolution you suddenly where > blocking google and thus for some people "The Internet". > > Also see: > http://homepages.tesco.net/J.deBoynePollard/FGA/dns-edns0-and-firewalls.html > > > (Which was the second hit for google(EDNS0) after a link to RFC2671) > > Greets, > Jeroen > ------------------------------ Message: 8 Date: Sat, 14 Jun 2008 23:23:44 +0200 From: Simon Leinen <simon.leinen(a)switch.ch> Subject: Re: DNS problems to RoadRunner - tcp vs udp To: Jon.Kibler(a)aset.com Cc: nanog(a)merit.edu Message-ID: <aaod63g17j.fsf(a)switch.ch> Content-Type: text/plain; charset=us-ascii Jon Kibler writes: > Also, other than "That's what the RFCs call for," why use TCP for > data exchange instead of larger UDP packets? TCP is more robust for large (>Path MTU) data transfers, and less prone to spoofing. A few months ago I sent a message to SwiNOG (like NANOG only less North American and more Swiss) about this topic, trying to explain some of the tradeoffs: http://www.mail-archive.com/swinog@lists.swinog.ch/msg02612.html Mostly I think that people "approaching this from a security perspective only" often forget that by fencing in the(ir idea of the) current status quo, they often prevent beneficial evolution of protocols as well, contributing to the Internet's "ossification". -- Simon. ------------------------------ Message: 9 Date: Sat, 14 Jun 2008 23:54:49 +0200 From: Jeroen Massar <jeroen(a)unfix.org> Subject: Re: DNS problems to RoadRunner - tcp vs udp To: Scott McGrath <mcgrath(a)fas.harvard.edu> Cc: nanog(a)merit.edu Message-ID: <48543E29.70809(a)spaghetti.zurich.ibm.com> Content-Type: text/plain; charset="iso-8859-1" Scott McGrath wrote: > > There is no call for insults on this list Insults? Where? If you feel insulted by any of the comments made on this list by people, then you probably are indeed on the wrong list. But that is just me. > - Rather thought this list was > about techincal discussions affecting all of us and keeping DNS alive > for the majority of our customers certainly qualifies. [..blabber about DNS attacks over TCP..] If I where a botnet herder and I had to take out your site and I was going to pick TCP for some magical reason then I would not care about your DNS servers, I would just hit your webservers, hard. I mean just the 'index.html' (http://www.harvard.edu/) is 24Kb, that is excluding pictures and there is bound to be larger data there which you are going to send and the bots only have to say "ACK" to once in a while. Multiply that by say a small botnet of 1M hosts, each just requests that 24Kb file. You will have a million flows and won't have any way to rate limit that or control it. Your link was already full trying to send it back to the clients and next to that your server was probably not able to process it in the first place. Simple, effective, nothing you can do about it, except get way and way more hardware. If somebody wants to take you out, they will take you out. Just get one other box with 10GE (not too hard to do) or just get a million of them with a little bit of connectivity (which is quite easy apparently)... > We/I am more than aware of the DNS mechanisms and WHY there are there > trouble is NO DNS server can handle directed TCP attacks even the root > servers crumbled under directed botnet activity and we have taken the > decision to accept some collateral damage in order to keep services > available. "The root servers crumbled" wow, I must have missed somebody taking out all the 13 separate and then individually anycasted root servers. Which btw only do UDP as currently '.' is still small enough. $ dig @a.root-servers.net. . NS +tcp [..] ;; Query time: 95 msec ;; SERVER: 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30) ;; WHEN: Sat Jun 14 23:45:52 2008 ;; MSG SIZE rcvd: 604 That is only 1 packet to 1 packet, still only 500 bytes. While your little webserver would generate 24kb for that same sequence. > We are a well connected university network with > multi-gigabit ingress and egress with 10G on Abilene so we try to > protect the internet from attacks originating within our borders AND we > really feel the full wrath of botnets as we do not have a relatively > slow WAN link to buffer the effects. The whole point generally of botnets is just the Denial of Service (DoS), if that is because your link is full or the upstreams link is full or because the service can't service clients anymore. But clearly, as you are blocking TCP-DNS you are DoSing yourself already, so the botherders win. Also note that Abilene internally might be 10G and in quite some places even 40G, but you still have to hand it off to the rest of the world and those will count as those 'slow WAN' links that you think everybody else on this planet is behind. (Hint: 10GE is kinda the minimum for most reasonably sized ISP's) > Yes - we are blocking TCP too many problems with drone armies and we > started about a year ago when our DNS servers became unresponsive for no > apparent reason. Investigation showed TCP flows of hundreds of > megabits/sec and connection table overflows from tens of thousands of > bots all trying to simultaneously do zone transfers and failing tried > active denial systems and shunning with limited effectiveness. How is a failed AXFR going to generate a lot of traffic, unless they are repeating themselves over and over and over again? Thus effectively just packeting you? Also, are you talking about Recursive or Authoritive DNS servers here? Where those bots on your network, or where they remote? > We are well aware of the host based mechanisms to control zone > information, Trouble is with TCP if you can open the connection you can > DoS so we don't allow the connection to be opened and this is enforced > at the network level where we can drop at wire speed. Do you mean that the hosts which do TCP are allowed to do transfers or not? As in the latter case they can't generate big answers, they just get 1 packet back and then end then FIN. Note also, that if they are simply trying to overload your hosts, UDP is much more effective in doing that already and you have that hole wide open apparently otherwise you wouldn't have DNS. > Open to better > ideas but if you look at the domain in my email address you will see we > are a target for hostile activity just so someone can 'make their bones'. It probably has nothing to do with the domain name, it more likely has something to do with certain services that are available or provided on your network. > Also recall we have a comittment to openess so we would like to make TCP > services available but until we have effective DNS DoS mitigation which > can work with 10Gb links It's not going to happen. You think that 10Gb is a 'fat link', amusing ;) There are various vendors, most likely also reading on this list, who can be more than helpful in providing you with all kinds of bad, but also a couple of good solutions to most networking issues that you are apparently having. But the biggest issue you seem to have is not knowing what the DoS kiddies want to take out and why they want to take it out. Greets, Jeroen PS: You do know that an "NS" record is not allowed to point to a CNAME I hope? (NS3.harvard.edu CNAME ns3.br.harvard.edu. RFC1912 2.4 ;) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: OpenPGP digital signature Url : http://mailman.nanog.org/pipermail/nanog/attachments/20080614/29473ad3/atta… ------------------------------ _______________________________________________ NANOG mailing list NANOG(a)nanog.org http://mailman.nanog.org/mailman/listinfo/nanog End of NANOG Digest, Vol 5, Issue 33 ************************************

1 0

Re: .255 addresses still not usable after all these years?
by Scott Weeks 15 Jun '08

15 Jun '08

I don't get it. As I mentioned about a year ago, when we last had this discussion, I have been handing out /23s to DHCP customers for years. No problems. .0 and .255 are not on WAN circuits or anything else, but zero problems for dynamically assigned customers. scott

1 0

[NANOG] Introducing latency for testing?
by Mike Lyon 14 Jun '08

14 Jun '08

So I want to mimic some latency in a test network for DB replication. I am wondering what other's have used for this? Obviously, the best way to would be to actually have one box across the US or across the globe to actually test against but what if you don't have that? Are there any GPL software router solutions that would allow you to tweak the latency in between the two test boxes? Thanks in advance. -Mike

10 11

.255 addresses still not usable after all these years?
by David Hubbard 14 Jun '08

14 Jun '08

I remember back in the day of old hardware and operating systems we'd intentionally avoid using .255 IP addresses for anything even when the netmask on our side would have made it fine, so I just thought I'd try it out for kicks today. From two of four ISP's it worked fine, from Verizon FIOS and Road Runner commercial, it didn't. So I guess that old problem still lingers? David

16 16

Weekly Routing Table Report
by Routing Analysis Role Account 13 Jun '08

13 Jun '08

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 14 Jun, 2008 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 259901 Prefixes after maximum aggregation: 128080 Deaggregation factor: 2.03 Unique aggregates announced to Internet: 126786 Total ASes present in the Internet Routing Table: 28442 Prefixes per ASN: 9.14 Origin-only ASes present in the Internet Routing Table: 24790 Origin ASes announcing only one prefix: 11978 Transit ASes present in the Internet Routing Table: 3652 Transit-only ASes present in the Internet Routing Table: 78 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 18 Max AS path prepend of ASN (43380) 13 Prefixes from unregistered ASNs in the Routing Table: 623 Unregistered ASNs in the Routing Table: 229 Number of 32-bit ASNs allocated by the RIRs: 48 Prefixes from 32-bit ASNs in the Routing Table: 8 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 780 Number of addresses announced to Internet: 1858706912 Equivalent to 110 /8s, 201 /16s and 157 /24s Percentage of available address space announced: 50.1 Percentage of allocated address space announced: 60.9 Percentage of available address space allocated: 82.3 Percentage of address space in use by end-sites: 72.2 Total number of prefixes smaller than registry allocations: 126226 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 59132 Total APNIC prefixes after maximum aggregation: 22129 APNIC Deaggregation factor: 2.67 Prefixes being announced from the APNIC address blocks: 56160 Unique aggregates announced from the APNIC address blocks: 25128 APNIC Region origin ASes present in the Internet Routing Table: 3275 APNIC Prefixes per ASN: 17.15 APNIC Region origin ASes announcing only one prefix: 869 APNIC Region transit ASes present in the Internet Routing Table: 508 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 17 Number of APNIC addresses announced to Internet: 352137632 Equivalent to 20 /8s, 253 /16s and 49 /24s Percentage of available APNIC address space announced: 75.0 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 APNIC Address Blocks 58/8, 59/8, 60/8, 61/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 120109 Total ARIN prefixes after maximum aggregation: 65072 ARIN Deaggregation factor: 1.85 Prefixes being announced from the ARIN address blocks: 89906 Unique aggregates announced from the ARIN address blocks: 34679 ARIN Region origin ASes present in the Internet Routing Table: 12213 ARIN Prefixes per ASN: 7.36 ARIN Region origin ASes announcing only one prefix: 4736 ARIN Region transit ASes present in the Internet Routing Table: 1147 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 356411552 Equivalent to 21 /8s, 62 /16s and 104 /24s Percentage of available ARIN address space announced: 73.3 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 ARIN Address Blocks 24/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 173/8, 174/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 55926 Total RIPE prefixes after maximum aggregation: 34008 RIPE Deaggregation factor: 1.64 Prefixes being announced from the RIPE address blocks: 51103 Unique aggregates announced from the RIPE address blocks: 34277 RIPE Region origin ASes present in the Internet Routing Table: 11456 RIPE Prefixes per ASN: 4.46 RIPE Region origin ASes announcing only one prefix: 5988 RIPE Region transit ASes present in the Internet Routing Table: 1725 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 18 Number of RIPE addresses announced to Internet: 360988032 Equivalent to 21 /8s, 132 /16s and 61 /24s Percentage of available RIPE address space announced: 82.8 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-48127 RIPE Address Blocks 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 20218 Total LACNIC prefixes after maximum aggregation: 5155 LACNIC Deaggregation factor: 3.92 Prefixes being announced from the LACNIC address blocks: 18456 Unique aggregates announced from the LACNIC address blocks: 10363 LACNIC Region origin ASes present in the Internet Routing Table: 954 LACNIC Prefixes per ASN: 19.35 LACNIC Region origin ASes announcing only one prefix: 305 LACNIC Region transit ASes present in the Internet Routing Table: 160 Average LACNIC Region AS path length visible: 4.1 Max LACNIC Region AS path length visible: 15 Number of LACNIC addresses announced to Internet: 52287232 Equivalent to 3 /8s, 29 /16s and 215 /24s Percentage of available LACNIC address space announced: 51.9 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 3895 Total AfriNIC prefixes after maximum aggregation: 1200 AfriNIC Deaggregation factor: 3.25 Prefixes being announced from the AfriNIC address blocks: 4168 Unique aggregates announced from the AfriNIC address blocks: 1875 AfriNIC Region origin ASes present in the Internet Routing Table: 243 AfriNIC Prefixes per ASN: 17.15 AfriNIC Region origin ASes announcing only one prefix: 80 AfriNIC Region transit ASes present in the Internet Routing Table: 47 Average AfriNIC Region AS path length visible: 3.9 Max AfriNIC Region AS path length visible: 14 Number of AfriNIC addresses announced to Internet: 12316160 Equivalent to 0 /8s, 187 /16s and 238 /24s Percentage of available AfriNIC address space announced: 36.7 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4755 1618 387 89 Videsh Sanchar Nigam Ltd. Aut 9498 1181 550 62 BHARTI BT INTERNET LTD. 17488 1120 78 76 Hathway IP Over Cable Interne 9583 1116 110 450 Sify Limited 4766 850 6006 343 Korea Telecom (KIX) 4134 824 12915 321 CHINANET-BACKBONE 23577 820 34 702 Korea Telecom (ATM-MPLS) 18101 693 167 36 Reliance Infocom Ltd Internet 9829 598 450 12 BSNL National Internet Backbo 1221 550 1919 423 Telstra Pty Ltd Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 209 3009 3874 620 Qwest 6389 2355 3138 188 bellsouth.net, inc. 4323 1469 1045 378 Time Warner Telecom 2386 1453 660 875 AT&T Data Communications Serv 7018 1370 5810 980 AT&T WorldNet Services 11492 1228 148 12 Cable One 1785 1066 510 105 AppliedTheory Corporation 18566 1044 296 10 Covad Communications 20115 1040 1062 564 Charter Communications 7011 1034 289 569 Citizens Utilities Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 3292 412 1772 371 TDC Tele Danmark 8452 347 188 7 TEDATA 3301 338 1460 308 TeliaNet Sweden 8866 319 77 21 Bulgarian Telecommunication C 3320 315 7045 265 Deutsche Telekom AG 3215 285 2742 89 France Telecom Transpac 8551 283 269 38 Bezeq International 5462 275 666 27 Telewest Broadband 680 274 2047 264 DFN-IP service G-WiN 9155 268 45 10 QualityNet AS number Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1245 2464 227 UniNet S.A. de C.V. 11830 603 299 9 Instituto Costarricense de El 22047 566 270 14 VTR PUNTO NET S.A. 7303 468 229 66 Telecom Argentina Stet-France 16814 426 27 10 NSS, S.A. 6471 413 85 46 ENTEL CHILE S.A. 11172 411 118 69 Servicios Alestra S.A de C.V 10620 392 100 71 TVCABLE BOGOTA 14117 375 23 9 Telefonica del Sur S.A. 20299 340 24 92 NEWCOM AMERICAS Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 475 61 30 LINKdotNET AS number 3741 282 853 223 The Internet Solution 20858 220 34 3 EgyNet 2018 192 189 82 Tertiary Education Network 5713 163 558 99 Telkom SA Ltd 6713 143 135 11 Itissalat Al-MAGHRIB 33783 134 10 12 EEPAD TISP TELECOM & INTERNET 5536 121 8 16 Internet Egypt Network 29571 103 13 8 Ci Telecom Autonomous system 33776 100 6 3 Starcomms Nigeria Limited Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 209 3009 3874 620 Qwest 6389 2355 3138 188 bellsouth.net, inc. 4755 1618 387 89 Videsh Sanchar Nigam Ltd. Aut 4323 1469 1045 378 Time Warner Telecom 2386 1453 660 875 AT&T Data Communications Serv 7018 1370 5810 980 AT&T WorldNet Services 8151 1245 2464 227 UniNet S.A. de C.V. 11492 1228 148 12 Cable One 9498 1181 550 62 BHARTI BT INTERNET LTD. 17488 1120 78 76 Hathway IP Over Cable Interne Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 6389 2355 2167 bellsouth.net, inc. 4755 1618 1529 Videsh Sanchar Nigam Ltd. Aut 11492 1228 1216 Cable One 9498 1181 1119 BHARTI BT INTERNET LTD. 4323 1469 1091 Time Warner Telecom 17488 1120 1044 Hathway IP Over Cable Interne 18566 1044 1034 Covad Communications 8151 1245 1018 UniNet S.A. de C.V. 1785 1066 961 AppliedTheory Corporation 22773 957 895 Cox Communications, Inc. Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 701 UUNET Technologies, 22492 UNALLOCATED 12.2.46.0/24 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13632 UNALLOCATED 12.20.55.0/24 6517 Yipes Communications 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 13632 UNALLOCATED 12.31.25.0/24 6517 Yipes Communications 27220 UNALLOCATED 12.35.204.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.51.159.0/24 7843 Adelphia Corp. 24.54.224.0/19 20001 HoldCo LLC - Road Runner 24.75.160.0/19 7843 Adelphia Corp. 24.75.192.0/18 7843 Adelphia Corp. 24.142.40.0/21 7018 AT&T WorldNet Services 24.142.160.0/19 7018 AT&T WorldNet Services 24.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services 62.61.220.0/24 24974 Tachyon Europe BV - Wireless 63.140.213.0/24 22555 Universal Talkware Corporatio Complete listing at http://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:18 /9:9 /10:16 /11:42 /12:142 /13:279 /14:514 /15:1028 /16:9958 /17:4337 /18:7359 /19:15676 /20:18305 /21:17924 /22:22319 /23:23253 /24:135965 /25:841 /26:1035 /27:782 /28:81 /29:10 /30:1 /31:0 /32:7 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 209 1764 3009 Qwest 6389 1452 2355 bellsouth.net, inc. 11492 1210 1228 Cable One 2386 1150 1453 AT&T Data Communications Serv 18566 1025 1044 Covad Communications 4755 973 1618 Videsh Sanchar Nigam Ltd. Aut 9583 971 1116 Sify Limited 6298 946 961 Cox Communicatons 6478 941 942 AT&T Worldnet Services 17488 932 1120 Hathway IP Over Cable Interne Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:9 8:114 12:2049 13:1 15:22 16:3 17:5 18:13 20:35 24:1075 25:1 32:61 33:3 38:440 40:92 41:645 43:1 44:2 47:12 52:3 55:4 56:3 57:23 58:458 59:475 60:443 61:991 62:1100 63:2030 64:3275 65:2419 66:3636 67:1211 68:695 69:2273 70:679 71:126 72:1815 73:5 74:1002 75:220 76:299 77:727 78:706 79:194 80:914 81:849 82:563 83:392 84:565 85:1011 86:422 87:694 88:313 89:1257 90:12 91:1267 92:186 93:574 94:16 96:34 97:23 98:200 99:3 100:1 111:1 112:1 113:1 114:34 116:695 117:326 118:143 119:460 120:59 121:525 122:781 123:346 124:850 125:1137 128:331 129:204 130:130 131:401 132:67 133:9 134:177 135:33 136:218 137:91 138:151 139:78 140:498 141:99 142:403 143:335 144:356 145:51 146:363 147:154 148:505 149:191 150:130 151:193 152:143 153:136 154:10 155:273 156:174 157:273 158:168 159:239 160:266 161:105 162:232 163:184 164:530 165:447 166:316 167:328 168:615 169:138 170:429 171:29 172:10 189:196 190:2103 192:5792 193:4094 194:3200 195:2488 196:1065 198:3740 199:3273 200:5541 201:1441 202:7631 203:7925 204:3986 205:2122 206:2412 207:2795 208:3365 209:3477 210:2520 211:1018 212:1399 213:1662 214:163 215:48 216:4426 217:1196 218:348 219:416 220:1083 221:469 222:308 End of report

1 0