SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
my isp kills my speed on p2p connections.
Are you sure it's your ISP? How do you know?
can i hide the p2p connections from the isp? a Protocol Ofuscation?
In theory you could piggyback any payload onto something else that is allowed. Practically speaking (performance-wise and since the other side has to recognise it ;-p) tunneling or proxying may be your only choices, but I spose that won't do for Bittorrent. If proxying does work it will be fsckin slow.
^ http/ftp transfers work fine [max speed]
p2p won`t, except for a few minutes around 2 am, but don`t ask me why.
and it`s not only bittorrent...direct connect is affected 2, and others like soulseek or gnutella.
^ http/ftp transfers work fine [max speed] p2p won`t,
...so you *dont* really know if your ISP actively blocks P2P traffic, do you?
There is a big difference between how HTTP/FTP and P2P work. HTTP/FTP is used on a path between two endpoints, you and the remote server, while P2P works between you and multiple peers. So, apart from your up and download speed and any throttling you or your ISP does, P2P throughput is affected by peer speed and its own set of rules like the availability of content by seeders and leechers, your upload ratio, snubbing and more. So in short you can't point to your ISP for throttling unless you have taken those into account and measured that.
except for a few minutes around 2 am, but don`t ask me why.
Is this constant? I mean does it happen every day and at exactly the same time? If it does are there any cronjobs running at that time? And did you check your firewall for inadvertedly blocking stuff?
...so you *dont* really know if your ISP actively blocks P2P traffic, do you?
Then what reason can explain the fact that when doing a download from someone with 10MB of uploading speed via direct connect i can`t go past the 6kb?
If it does are there any cronjobs running at that time? And did you check your firewall for inadvertedly blocking stuff? no...this happened back when i used windows 2...and my firewall rule set has the port i need open.
my ISP must be throttling p2p connections! you don`t work for them do you?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.