[PROXYPER] port 2064 w/firwalls

DHS dx7 at earthlink.net
Mon Dec 6 19:58:57 EST 1999


Meelis,
  Thank you for you explanation of TCP behavior. These random ports seem to
completely fool the 'firewall' and generate no promiscuous hits in the BID
tracking log. This is the first time I have seen it in action. On the
previous clients (2.7106.435), they always used port 2064 (as recorded in
their logs). I may turn off my 'firewall' and see if these new clients
continue this 'normal' port behavior. I'm still learning. I find this
brute-force dedication to return work to the proxy interesting in spite of
the 'firewall' application I also have running. Sometimes I just sit back,
watch the machines, and say, "Far F*(king Out!"
Duncan

-----Original Message-----
From: Meelis Roos <mroos at cs.ut.ee>
To: proxyper at lists.distributed.net <proxyper at lists.distributed.net>
Date: Sunday, December 05, 1999 18:20 PM
Subject: Re: [PROXYPER] port 2064 w/firwalls


>> client01 used: 2214, 2480, 2650, 2651, 2652, 2653, 2654, 2658, 2711,
2756,
>> 2915, 3081, 3086,
>>
>> client012 used: 2234, 2235, 2236, 2237, 2238, 2239, 2240, 2241, 2242,
2243,
>> 2244,
>>
>> client013 used: 1637, 1638, 1639, 1640, 1641, 1642, 1643, 1644,
>>
>> client014 used: 1058, 1059, 1060, 1061, 1062, 1063, 1064, 1065, 1066,
1067,
>> 1068, 1069, 1070, 1071,
>
>These are probably the source ports where the connection comes from. The
>destination port on the perproxy is 2064. The source port is
>random. This is normal TCP behaviour.
>
>---
>Meelis Roos             e-mail: mroos at ut.ee
>                        www:    http://www.cs.ut.ee/~mroos/
>
>--
>To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net
>
>

--
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net



More information about the proxyper mailing list