[PROXYPER] port 2064 w/firwalls

DHSinclair dx7 at earthlink.net
Sun Dec 5 16:23:20 EST 1999


I've gone back and reread the instructions for both the v311 perproxy and
the v2.447 clients to understand what I am seeing. I do not seem to have any
problems. This is just a very confusing observation.

My 4 machines run W95 OSR2.1.  My master console contains both a client and
the perproxy. This machine also runs the BlackIce Defender firewall. It is
the only machine I have with a connection to the internet.

I know that all 4 clients and the perproxy are set to communicate via port
2064, but while reviewing my perproxy logs and client logs, I see that
interchanges between them used ports other than 2064. From my past cycle, I
see:

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,

Looks like the clients and perproxy will communicate with each other no
matter what! I suppose this is normal and part of the overall design. I
suppose that if I figure out how to 'allow' port 2064 via BlackIce Defender,
I will not see this "brute force" behavior any longer. (?) Pretty
impressive.
Duncan


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



More information about the proxyper mailing list