[24650] in North American Network Operators' Group
Re: SYN spoofing
daemon@ATHENA.MIT.EDU (Deepak Jain)
Wed Jul 28 14:08:30 1999
Date: Wed, 28 Jul 1999 14:05:14 -0400 (EDT)
From: Deepak Jain <deepak@ai.net>
To: Joe Shaw <jshaw@insync.net>
Cc: John Fraizer <John.Fraizer@EnterZone.Net>,
Dan Hollis <goemon@sasami.anime.net>, bandregg@redhat.com,
nanog@merit.edu
In-Reply-To: <Pine.SOL.4.10.9907280925060.20827-100000@vellocet.insync.net>
Errors-To: owner-nanog-outgoing@merit.edu
While it is easy, it is not always practical because you often have
customers who advertise thousands of prefixes.
Or, in the simpler case, if you transit 500,000 pps on a single outbound
link/router, it becomes very expensive to do per packet filtering
outbound.
At our ingress points, for example, (from peers and customers) we do
filter bogus traffic so we in turn, do not pass undesirable traffic on.
At ingress points where you are only seeing 150,000 pps its not so bad
doing per packet filtering.
Just an opinion,
Deepak Jain
AiNET
On Wed, 28 Jul 1999, Joe Shaw wrote:
>
>
> Any provider who allows the passing of address space that isn't his own
> (beyond whatever transit they may provide to their peers) is shameful.
>
> How hard is it really to put a filter on your outbound links that says
> drop all ip traffic heading out these links that isn't from my IP space?
> It's just like martian filters for your inbound links, and we'd see a
> significant decrease in spoofing based attacks if it was more widely
> adopted. Not to mention it'll keep peers from dumping traffic on you.
>
> --
> Joseph W. Shaw - jshaw@insync.net
> Freelance Computer Security Consultant and Perl Programmer
> Free UNIX advocate - "I hack, therefore I am."
>
> On Wed, 28 Jul 1999, John Fraizer wrote:
>
> > Perhaps if you were to NAME these networks, they may be shamed into doing
> > something about the problem. Then again, they should be ashamed to begin
> > with for passing RFC1918 traffic, let alone loopback space.
>
>
>
