Traffic shaping (pipex)

Indy500 · 11 Apr 2007 at 20:05

USB modems and long RJ11 cables can hurt your connection speeds.

z0mbi3 · 11 Apr 2007 at 20:07

It might be a case that you haven't opened the right ports on your firewall / router.

Do you know what port your using for bitcommet? You should be able to find out from one of the sub menus.

knip · 11 Apr 2007 at 20:07

And if I plugged it into the wireless router I have would that help?
Really should get the phone socket up here fixed.

knip · 11 Apr 2007 at 20:09

z0mbi3 said:
Do you know what port your using for bitcommet? You should be able to find out from one of the sub menus.

I have a listening port option that says this:-
Listen port 22025, there is an option to choose a random port, or have no listening mode but that says it will slow down my download speed.

z0mbi3 · 11 Apr 2007 at 21:33

knip said:
I have a listening port option that says this:-
Listen port 22025, there is an option to choose a random port, or have no listening mode but that says it will slow down my download speed.

Put that port number into http://whatsmyip.org/ports/ and see what it comes back with.

knip · 11 Apr 2007 at 21:50

In the custom port test it says Status OPEN.

z0mbi3 · 11 Apr 2007 at 22:01

I'm at a loss then. Just try torrents with more seeders.

knip · 11 Apr 2007 at 22:01

I ran the test for P2P ports and I got this if it makes any sense to anyone

375
to
425 Timeout
-
Timeout Direct Connect
(Ports between 375 and 425 not checked)
1214 Timeout Kazaa (aka FastTrack)
412
1412
2412 Timeout
Timeout
Timeout DC++
4661
4662
4665 Timeout
Timeout
Timeout eDonkey
5500 Timeout Hotline Server
6346 Timeout Gnutella (aka LimeWire) (aka Acquisition)
6881 Timeout
6882 Timeout
6883 Timeout
6884 Timeout Bitcomet
6885 Timeout
6886 Timeout
6887 Timeout
6888 Timeout
6889 Timeout

knip · 11 Apr 2007 at 22:02

z0mbi3 said:
I'm at a loss then. Just try torrents with more seeders.

Bloody pipex if you ask me.
Grrr!
Thanks anyway.