I found a solution using wingate for inet connection sharing.
I have Wingate 4.5 running on my server (2 nics 1 to inet - 1 to lan), and 4 systems on the house lan that use the WG Inet Client. I tried a host of setting changes trying to get the WG gatekeeper firewall to allow BitTornado to run correctly. I don't think its possible.
However, I now get a green light when I run it on my server. ( but only on my server, never been able to get the clients to work )
1st I turned off the gatekeeper firewall. To turn it off double click the extended networking** WG service. On the general tab under firewall select disable WG firewall.
2nd Since its not a smart move to be fully exposed to the inet without a firewall, I installed Kerio Personal Firewall 2.1.5.
Adding the following 4 rules to the firewall to allow the wingate to fully work with this firewall and still remain fairly secure. ( this should work with zone alarm also )
protcol | local | remote | application
tcp - out | any port | any address | c:\path to\wingate.exe
tcp - in | any port | lan subnet* | c:\path to\wingate.exe
udp - both | any port | lan subnet* | c:\path to\wingate.exe
udp/tcp - both | any port | 127.0.0.1 | c:\path to\gatekeeper.exe
*lan subnet is servers lan ip with a 255.255.255.0 subnet mask
ie (10.0.0.1/255.255.255.0) or (192.168.1.1/255.255.255.0)
**If you don't know where the extended networking service is at. Under the view menu (up top) click control panel, make sure the system tab is selected (bottom left of gatekeeper screen ). now you should be able to see it in the WG system service list.
|