Hi. We've recently been allocated address space out of 59.0.0.0/8, which was released to APNIC by IANA about 11 months ago. Prior to that release, it was reserved, and appeared on all the public bogon filtering lists. It obviously isn't supposed to appear on them anymore. If you run any bogon filtering, can you please check your border ACLs and BGP prefix filters to ensure that you're no longer preventing access to 58.0.0.0/8 or 59.0.0.0/8 ? Thanks, - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82282999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
On Thu, Mar 10, 2005 at 11:51:40AM +1030, Mark Newton wrote:
If you run any bogon filtering, can you please check your border ACLs and BGP prefix filters to ensure that you're no longer preventing access to 58.0.0.0/8 or 59.0.0.0/8 ?
Further to this: If anyone from EV1 hosting is reading this, please get in touch ASAP? We've been talking to a few of your front-line tech support people for a couple of days now, and while it's been fun, we'd kinda like to stop doing that and start talking to someone who acknowledges that there's a problem here and knows how to fix it :-) Thanks, - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82282999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
Hi, NANOGers. ] If you run any bogon filtering, can you please check your border ACLs ] and BGP prefix filters to ensure that you're no longer preventing ] access to 58.0.0.0/8 or 59.0.0.0/8 ? Folks can keep up with the bogon filters through a wide variety of means. We have HTTP, DNS, RADb objects, RIPE NCC objects, and text files. <http://www.cymru.com/Bogons/> It can be even easier still! Why not automate the process of bogon filter updates, thus avoiding the shame of filtering good folks such as Mark? :) Take a peek at our Bogon route-server project at the following URL. <http://www.cymru.com/BGP/bogon-rs.html> Thanks, Rob, for Team Cymru. -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999.
On Thu, 10 Mar 2005, Rob Thomas wrote:
Folks can keep up with the bogon filters through a wide variety of means. We have HTTP, DNS, RADb objects, RIPE NCC objects, and text files.
I think this has been posted here more than a few dozen times. Perhaps a list of sites/Nocs that do not automate their updates could be kept so: 1. People would have a list of phone numbers to call every time a change was made. 2. People would have a list of sites that were known to be of less clue than most. This might help them make purchasing decisions in the future. -- Simon J. Lyall. | Very Busy | Mail: simon@darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.
On Fri, 11 Mar 2005, Simon Lyall wrote:
On Thu, 10 Mar 2005, Rob Thomas wrote:
Folks can keep up with the bogon filters through a wide variety of means. We have HTTP, DNS, RADb objects, RIPE NCC objects, and text files.
I think this has been posted here more than a few dozen times. Perhaps a list of sites/Nocs that do not automate their updates could be kept so:
1. People would have a list of phone numbers to call every time a change was made.
2. People would have a list of sites that were known to be of less clue than most. This might help them make purchasing decisions in the future.
Hmmmm, one wonders if the static security template has over time become responsible for more realized loss of connectivity than the attacks it theoretically protects against. Perhaps it should be distributed with only a martian and RFC1918 filter, and not the unallocated space, if everybody knows that people apply it in a write once configuration manner. Mike. +----------------- H U R R I C A N E - E L E C T R I C -----------------+ | Mike Leber Direct Internet Connections Voice 510 580 4100 | | Hurricane Electric Web Hosting Colocation Fax 510 580 4151 | | mleber@he.net http://www.he.net | +-----------------------------------------------------------------------+
On Thu, 10 Mar 2005, Mike Leber wrote:
On Fri, 11 Mar 2005, Simon Lyall wrote:
On Thu, 10 Mar 2005, Rob Thomas wrote:
Folks can keep up with the bogon filters through a wide variety of means. We have HTTP, DNS, RADb objects, RIPE NCC objects, and text files. Perhaps it should be distributed with only a martian and RFC1918 filter, and not the unallocated space, if everybody knows that people apply it in a write once configuration manner.
or there's always that internet drivers license concept... except you'd need a new class to take care of 'network operators', like 'limo' or 'bus' citations on car licenses. Seriously though, Perhaps Puck.nether.net or Mr. Lewis's 69box could be a good site to host 'slow filter updaters' contact infos?
2. People would have a list of sites that were known to be of less clue than most. This might help them make purchasing decisions in the future.
Are you suggesting that NANOG should publish a set of operational best practices and then only offer the NANOG seal of approval to companies which adhere to those best practices? If there is one thing that will stop telecoms regulators from attempting to regulate the Internet, it is this. The technical term is "industry self regulation". --Michael Dillon
On Fri, Mar 11, 2005 at 10:36:28AM +0000, Michael.Dillon@radianz.com wrote:
2. People would have a list of sites that were known to be of less clue than most. This might help them make purchasing decisions in the future.
Are you suggesting that NANOG should publish a set of operational best practices and then only offer the NANOG seal of approval to companies which adhere to those best practices?
The Good Netkeeping Seal of Approval, yes.
If there is one thing that will stop telecoms regulators from attempting to regulate the Internet, it is this. The technical term is "industry self regulation".
And it would have the side effect of assembling all of those best practices in a central place where those occasaional operators of really small networks (like me :-) who care what they are can conveniently find them. I'd recommend a wiki. Running MediaWiki. But then, I recommend that for all centralized knowledge capture situations. :-) Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Designer Baylink RFC 2100 Ashworth & Associates The Things I Think '87 e24 St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274 If you can read this... thank a system adminstrator. Or two. --me
And it would have the side effect of assembling all of those best practices in a central place where those occasaional operators of really small networks (like me :-) who care what they are can conveniently find them.
I'd recommend a wiki. Running MediaWiki.
Well, its not running MediaWiki at the present time, but anyone is welcome to add this kind of useful content to the BGP4.net wiki. http://www.bgp4.net
On Fri, 11 Mar 2005, Simon Lyall wrote:
1. People would have a list of phone numbers to call every time a change was made.
2. People would have a list of sites that were known to be of less clue than most. This might help them make purchasing decisions in the future.
In my experience with 69/8, most of the problem sites were "end users" rather than service providers...though in some cases, those end users were things like parts of the US Military and NASA, etc. The only provider I remember running into that had a static bogon issue was fast.net, but they don't even exist anymore AFAIK, as they were bought by USLEC. So while the list would be useful as a contact list for those affected, I doubt it's going to influence anyone's transit buying decisions. ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
participants (9)
-
Christopher L. Morrow -
Janet Sullivan -
Jay R. Ashworth -
Jon Lewis -
Mark Newton -
Michael.Dillon＠radianz.com -
Mike Leber -
Rob Thomas -
Simon Lyall