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: SYN spoofing

  • From: Deepak Jain
  • Date: Wed Jul 28 16:57:23 1999


The thread I was responding to refered to filtering all routes 
(outbound) except those sourced from customers'/internal addresses.

Regards,

Deepak Jain
AiNET

On Wed, 28 Jul 1999, Mike Heller wrote:

> I have an access list that I apply to all of our incoming interfaces that 
> blocks the announcement of 127.0.0.1, 192.168.0.0, 10.0.0.0, and 
> 172.16.0.0.  It never changes. I don't see the stated impact on management.
> 
> Mike
> 
> On Wed, 28 Jul 1999, Dan Hollis wrote:
> 
> > 
> > On Wed, 28 Jul 1999, Deepak Jain wrote:
> > > While it is easy, it is not always practical because you often have 
> > > customers who advertise thousands of prefixes. 
> > 
> > Why would this have any impact on filtering rfc1918 and other invalid nets
> > like 127.0.0.0/8 and 255.255.255.255?
> > 
> > Or perhaps someone could explain a valid reason to route these addresses.
> > 
> > -Dan
> > 
> > 
> > 
> 





Discussion Communities


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


Merit Network, Inc.