Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: RFC1918 conformance

  • From: Bill Manning
  • Date: Tue Feb 11 12:10:03 1997

> My standard in & out route filters are attached.
> Everyone should use something like this.
> 	--asp@partan.com (Andrew Partan)
> 
> ! Deny martian routes
> ! 1st and last classical B and C nets (guard nets).
> access-list 180 deny   ip 128.0.0.0 0.0.255.255 255.255.0.0 0.0.255.255
> access-list 180 deny   ip 191.255.0.0 0.0.255.255 255.255.0.0 0.0.255.255
> access-list 180 deny   ip 192.0.0.0 0.0.0.255 255.255.255.0 0.0.0.255
> access-list 180 deny   ip 223.255.255.0 0.0.0.255 255.255.255.0 0.0.0.255

	In a classless environment, these prefixes are legitimate.
	Correct behaviour is now known for these subnets and so I
	wonder why you still have them in your standard list.


-- 
--bill
- - - - - - - - - - - - - - - - -




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.