Overnet's connection is based on P2P, which requires one of the clients to accept an incoming connection, if none of the clients can accept an incoming connection (like, port blocked by a firewall) - a P2P connection can not be created, thus you cannot communicate with that client, thus - reducing your sources list.
that probably means that you reduce your possible sources list by some percentage, which sometimes (when files are rare) is crucial
Thats, ofcourse, not based on any facts relevant to overnet - thats how any P2P network works (ed2k, kazaa, etc.)
-- Regards, Noam L.
Quoting Shlomo Solomon <[EMAIL PROTECTED]>:
> Sorry if this is a bit off topic, but a friend introduced me to > Overnet on his > Windows machine. After a short search, I found and installed a Linux client > to play around with. While GOOGLING I found instructions on how to open > appropriate ports in the firewall, but decided to see what the program would > do without touching the iptables rules. To my surprise, Overnet works "out of > the box". > > To verify that my firewall is still working properly, I went to ShieldsUp at > http://grc.com and passed all their tests (including portscans of the ports > Overnet uses). So I have 2 questions. > > 1 - Why and how is Overnet working? > 2 - Am I exposing myself in any way, and if so, what's the danger? > > TIA > > -- > Shlomo Solomon > http://come.to/shlomo.solomon > Sent by KMail 1.6.1 (KDE 3.2) on LINUX Mandrake 10.0 > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED]
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
