Re: Remotely Counting Machines Behind Nat

2004-02-22 Thread A. Wright
ting. - Original Message - From: "Todd Stratton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, February 20, 2004 5:31 PM Subject: Re: Remotely Counting Machines Behind Nat > Shouldn't the "modulate state"

Re: Remotely Counting Machines Behind Nat

2004-02-20 Thread Todd Stratton
Shouldn't the "modulate state" option foil fingerprinting via ISNs since it creates random ones? I don't think there is an acceptable way to normalize the TCP window size...Then you'd be messing with buffer management at the endpoints. You'd have to proxy for that. from man 8 pf.conf: Much of the

Re: Remotely Counting Machines Behind Nat

2004-02-18 Thread A. Wright
Yes, I've tried this, but have run into some troubles. My ruleset is below, and here's the setup. Box A is Windows XP behind the NAT with IP of 192.168.0.5 plugged into Hub A. Box B is the FreeBSD pf/NAT box, int_if is 192.168.0.1 plugged into Hub A, ext_if is 10.12.4.61 plugged into Hub B. Box

Re: Remotely Counting Machines Behind Nat

2004-02-17 Thread Mike Frantzen
> Is there a way with pf to "wash" these ambiguities (window size, syn packet > size, etc) away so that all outgoing TCP packets look the same? Maybe even > set them to user-defined variables, as we already can with 'max-mss' and > 'min-ttl'? Use the syn-proxy. It crafts all of the SYN's by hand

RE: Remotely Counting Machines Behind Nat

2004-02-17 Thread Dom De Vitto
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nikolay Denev Sent: Tuesday, February 17, 2004 11:20 PM To: [EMAIL PROTECTED] Subject: Re: Remotely Counting Machines Behind Nat > Hello All, > > It says in the FAQ that using the 'reassemble tcp' scrub option k

Re: Remotely Counting Machines Behind Nat

2004-02-17 Thread Nikolay Denev
> Hello All, > > It says in the FAQ that using the 'reassemble tcp' scrub option keeps an > observer from guessing how many hosts are behind a NAT gateway. The main > thing I plan to use this for is to prevent my ISP from finding out I have > more than 1 computer connected, and then start asking m

Re: Remotely Counting Machines Behind Nat

2004-02-17 Thread Ryan McBride
On Tue, Feb 17, 2004 at 10:39:27AM -0500, A. Wright wrote: > Is there a way with pf to "wash" these ambiguities (window size, syn packet > size, etc) away so that all outgoing TCP packets look the same? Maybe even > set them to user-defined variables, as we already can with 'max-mss' and The most

Re: Remotely Counting Machines Behind Nat

2004-02-17 Thread Shawn K. Quinn
On Tuesday 2004 February 17 09:39, A. Wright wrote: > Hello All, > > It says in the FAQ that using the 'reassemble tcp' scrub option keeps > an observer from guessing how many hosts are behind a NAT gateway. > The main thing I plan to use this for is to prevent my ISP from > finding out I have mor

Re: Remotely Counting Machines Behind Nat

2004-02-17 Thread Matt Gibson
A. Wright wrote: Hello All, It says in the FAQ that using the 'reassemble tcp' scrub option keeps an observer from guessing how many hosts are behind a NAT gateway. The main thing I plan to use this for is to prevent my ISP from finding out I have more than 1 computer connected, and then start a

Remotely Counting Machines Behind Nat

2004-02-17 Thread A. Wright
Hello All, It says in the FAQ that using the 'reassemble tcp' scrub option keeps an observer from guessing how many hosts are behind a NAT gateway. The main thing I plan to use this for is to prevent my ISP from finding out I have more than 1 computer connected, and then start asking me to pay mo