[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Comcast throws down gauntlet to residential accounts
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Comcast throws down gauntlet to residential accounts
- From: grarpamp <grarpamp@xxxxxxxxx>
- Date: Tue, 11 Aug 2009 03:05:38 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 11 Aug 2009 03:05:43 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WC86Hu1+IBS08WuyeOp4MarBBuYikvgJYLSscJSt79k=; b=mzkS7ITO9qlKh5zOyqYoAtPAGtHrxZjdJh8hyZceRMahHav7XSG+8Zr+yKVUnzj27P IVOMXcmbHGtrfgw8GV9hf3n8YseRqzmCPnGGFXwQ+jg7B8Le37gkVRDoUwunuin3F+h4 bCk9rqoEIC0rxqQYbwl+ukn1Fmd+v+c4tTxVU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=M9ZmgQBHDehJfNIqxN8jN7QS7w9eyVL2DrxtnJGi1jCttX1gHLiV2ku67hl/jbFPqG 9GxZwh0GzJa14VHsTAexAfmfasHj/1VqL2YhvOHSockogBINWHkvYJPdhOrpv5Erc4yE jh331iFNSHfBrXl6YxJU9MNw0fqlj5e6GAJV0=
- In-reply-to: <200908110545.n7B5jtQB023671@xxxxxxxxxxxxx>
- References: <200908110545.n7B5jtQB023671@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
> How would slower speeds avoid Comcast's port scans?
Wouldn't. But since you said you saw them scanning you, fine... logon
to a route server, look up the asn of that address and anything else
comcast related, grab all their cidr blocks and sink the whole pile of
them on your packet filter. Then the only thing you have to worry
about is inbound complaints about your exit to their ticket system or
an engineer who gets bored and decides to use Tor to scan you or
netflow to see what you've been up to :)