Port fowarding question (KTorrent)

[purps]

Hi chaps, hopefully an easy one. Not getting very good speeds with KTorrent on the Core.

I have an external Netgear router providing Internet to eth0 on the Core. Do I have to worry about port forwarding on both the Core and the Netgear router?

On the Netgear router (accessed via 192.168.1.1), I currently have...
Service type: TCP/UDP
Starting port: 6881
Ending port: 6881
Server IP Address: 192.168.1.3 (this is the IP of eth0 on the Core)

On the Core (192.168.80.1), I currently have...
tcp     6881 to 6881     6881  192.168.80.1     port_forward
udp    6881 to 6881    6881    192.168.80.1    port_forward
tcp    6881 to 6881     0         0                   core_input
udp    6881 to 6881    0         0                   core_input

Does that all look right?

Cheers,
Matt.

[bongowongo]

Use this "tool" to verify if your port is open
http://canyouseeme.org/

If not
It can also be that you have settings in your router to forward in firewall or maybe nat

[purps]

What a useful tool!

It gave me:

Success: I can see your service on 82.xxx.xxx.xxx on port (6881)
Your ISP is not blocking port 6881

Why else might I be getting slow download speeds?

Cheers,
Matt.

[bongowongo]

The available connections per minute....normally around 800 per second | do not set it on 800 per second around 300 is ok
Your available upload speed. Do not set it to the max, because it influences your download speed.
Tweak it to satisfactory. It can also be that your ISP is blocking standard torrent ports, you can google that, or try different ports.

[Zaerc]

Get rid of the "port_forward" rules, you only need "core_input", only for tcp even.

And try using a non-standard port, as 6881 gets squeezed by a lot of ISPs by default.  Depending on your ISP, turning on some sort of encryption in the client might also help.

[purps]

Thank you for the advice.

That is good to know; I now only have a single tcp core input.

The ports are still giving me jip though. I'm staying away from the 6XXX range completely as I read that some ISPs (I am with Virgin) often block all of those. I tried in the 12XXX range as well. Then I had a go with 444 (as I knew 443 was working for my remote HTTPS access), but still no joy with the http://canyouseeme.org/ tool.

Is forwarding a given port for torrents exactly the same process as forwarding the 443 port for HTTPS access? if I can get 443 working, I should be able to get any other port working right?

On the Netgear router, is 192.168.1.3 the correct IP to use when port forwarding? This is the IP of eth0 on the core.

Cheers,
Matt.

[bongowongo]

Yes, I see no errors in your logic.

[purps]

Ok cheers, I will persevere.

[purps]

I tried changing the torrent port to 443 (which I know is open) and it is SLIGHTLY better, but I'm still not convinced.

One other thing that I can't work out (maybe related?) is why the vast majority of my torrents are "Stalled"? Is it safe to update KTorrent to the latest version? I read that that might be the reason.

Cheers,
Matt.

[merkur2k]

if you have an external router then you can save yourself a whole lot of heartache by disabling the lmce firewall entirely. theres no need to be running 2 firewalls.

[purps]

The best solutions are usually the simplest!

May I ask why you suggested disabling the LMCE firewall, and not the Netgear router one?

Cheers,
Matt.