[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ISP port blocking practice

Subject: ISP port blocking practice
From: bill at herrin.us (William Herrin)
Date: Fri, 3 Sep 2010 11:23:00 -0400
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On Thu, Sep 2, 2010 at 11:04 PM, Daniel Senie <dts at senie.com> wrote:
> Ingress filtering is the correct tool for the job.

Not really. Ingress filtering only ever protected you from being the
source of spooding attacks, not the destination. The point of Zhiyun's
results is that it doesn't fully protect you from being the source
either.

Frankly, Zhiyun offers the first truly rational case I've personally
seen for packet filtering based on the TCP source port. You should
give his work more careful scrutiny.

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin at dirtside.com? bill at herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004

Follow-Ups:
- ISP port blocking practice
  - From: rdobbins at arbor.net (Dobbins, Roland)

References:
- ISP port blocking practice
  - From: zhiyunq at umich.edu (Zhiyun Qian)
- ISP port blocking practice
  - From: ops.lists at gmail.com (Suresh Ramasubramanian)
- ISP port blocking practice
  - From: zhiyunq at umich.edu (Zhiyun Qian)
- ISP port blocking practice
  - From: ops.lists at gmail.com (Suresh Ramasubramanian)
- ISP port blocking practice
  - From: zhiyunq at umich.edu (Zhiyun Qian)
- ISP port blocking practice
  - From: dts at senie.com (Daniel Senie)

Prev by Date: largest OSPF core
Next by Date: ISP port blocking practice
Previous by thread: ISP port blocking practice
Next by thread: ISP port blocking practice
Index(es):
- Date
- Thread