No subject


Tue Mar 1 03:45:00 UTC 2011


<br>
Advantages of the WideCap:<br>
System integration - WideCap is fully functional Winsock Service and<br>
Namespace provider. That means simply integration into your network<br>
subsystem. Forget about this ugly FreeCap&#39;s injection, needle to run all<br>
programs throught FreeCap, possible errors and incompatible with some<br>
firewalls and anti-viruses. WideCap acts as virtual network driver<br>
covering all your TCP/IP activity. No launchers - just run your program<br>
as usual and work via proxy.<br>
<br>
New proxy engine - fully rewritten proxy engine taken from the FreeCap<br>
to handle reloading everything on-the-fly. No more program restarts<br>
after changing the proxy chain or Widecap configuration. Plus boosted<br>
perfomance with proxies handling.<br>
<br>
<br>
<br>
Here is some things from the FAQ I thought was interesting: (it does<br>
UDP)<br>
<br>
Q: What kind of traversing WideCap does?<br>
A: Using WideCap you can traverse only TCP or UDP connections. But UDP<br>
only via SOCKSv5, only via one proxy, and without NAT in the middle.<br>
Others protocols (such as icmp, igmp etc) unable to traversing by<br>
architecture and RFC restrictions.<br>
<br>
Q: What kind of traversing WideCap does?<br>
A: Using WideCap you can traverse only TCP or UDP connections. But UDP<br>
only via SOCKSv5, only via one proxy, and without NAT in the middle.<br>
Others protocols (such as icmp, igmp etc) unable to traversing by<br>
architecture and RFC restrictions.<br>
<br>
Q: After the proxy checking I&#39;ve got that all proxies are broken. And<br>
the system event log reports about &quot;EventID 4226: TCP/IP has reached the<br>
security limit imposed on the number of concurrent TCP connect<br>
attempts&quot;. What&#39;s wrong? I have Windows XP SP2.<br>
A: It&#39;s problem related to WinXP SP2 users (and possible Win2003). In<br>
this systems the TCP/IP driver has a limitation for concurrent<br>
connection attempts. Limited to 10 concurrent connection attempts.<br>
Unfortunately there&#39;s no registry key to fix this but patch exists. Read<br>
more about Event ID 4226 + patch<br>
<br>
--&gt;That last question is the same issue I think of non-server Windows<br>
issues when acting as a Tor node. &nbsp;In my next email to the list found a<br>
great little app that will change the connect limits in the tcpip.sys<br>
file to whatever you want. &nbsp;I set mine to 100.<br>
<br>
<br>
What does everyone think?<br>
<br>
--<br>
<br>
 &nbsp;<a href="mailto:gregoron at fastmail.fm">gregoron at fastmail.fm</a><br>
<font color="#888888"><br>
--<br>
<a href="http://www.fastmail.fm" target="_blank">http://www.fastmail.fm</a> - Does exactly what it says on the tin<br>
<br>
</font></blockquote></div><br></div>

------=_Part_26366_28093035.1229658635905--



More information about the tor-talk mailing list