Applying screenshot of the logs because I couldn't find how to copy it. May be it's another issue for report
Ports don't match
-
Fingli
Ports don't match
Im using qB 2.9.5 with UPnP switched on. But the icon in status bar always stays yellow that is to say that there are not direct connections. So I checked the log and found that qB use diffident port than mapped one.
Applying screenshot of the logs because I couldn't find how to copy it. May be it's another issue for report
Applying screenshot of the logs because I couldn't find how to copy it. May be it's another issue for report
- Attachments
-
-
loki
Re: Ports don't match
My guess is it can't use a port number that low or is already in use by another program then it just picks a random port instead.
Is that port what you have specified in the settings? If so, why pick a port so low... most of the lower ports have specific uses. Also, avoid port 6881 if you prefer not to potentially be singled out or filtered by your ISP.
Is that port what you have specified in the settings? If so, why pick a port so low... most of the lower ports have specific uses. Also, avoid port 6881 if you prefer not to potentially be singled out or filtered by your ISP.
-
Fingli
Re: Ports don't match
[quote="loki"]
My guess is it can't use a port number that low or is already in use by another program then it just picks a random port instead.
Is that port what you have specified in the settings? If so, why pick a port so low... most of the lower ports have specific uses. Also, avoid port 6881 if you prefer not to potentially be singled out or filtered by your ISP.
[/quote]
Yea, in the pic port 55056 is specified in settings for incoming connections. Port 6881 is only for DHT and it's mapped correctly. The problem is with the main port for TCP conns. It picks random port every time instead of the settled one. I've tried with different ports numbers, the result is the same as in the picture.
My guess is it can't use a port number that low or is already in use by another program then it just picks a random port instead.
Is that port what you have specified in the settings? If so, why pick a port so low... most of the lower ports have specific uses. Also, avoid port 6881 if you prefer not to potentially be singled out or filtered by your ISP.
[/quote]
Yea, in the pic port 55056 is specified in settings for incoming connections. Port 6881 is only for DHT and it's mapped correctly. The problem is with the main port for TCP conns. It picks random port every time instead of the settled one. I've tried with different ports numbers, the result is the same as in the picture.
-
loki
Re: Ports don't match
It's either not able to configure the port specified, therefore falling back to random port, or you already have something else using that port.
I know you said you're using upnp... but it may be one of the cases where it doesn't work through whichever configuration you have, try manually allowing the port in your firewall/router and check to see that it does now successfully use the specified port.
I know you said you're using upnp... but it may be one of the cases where it doesn't work through whichever configuration you have, try manually allowing the port in your firewall/router and check to see that it does now successfully use the specified port.
-
Fingli
Re: Ports don't match
[quote="loki"]
It's either not able to configure the port specified, therefore falling back to random port, or you already have something else using that port.
I know you said you're using upnp... but it may be one of the cases where it doesn't work through whichever configuration you have, try manually allowing the port in your firewall/router and check to see that it does now successfully use the specified port.
[/quote]
First to say that I have no problems with my ISP filtering my traffic. With uTorrent I'm seeding like a boss
Every time with green icon, that's why it was unusual for me to saw indication for connection problem.
Today I installed the new version 2.9.7 (uninstalled 2.9.5 first) and tested it with default settings. The result was the same - in every start qB gets random port disregarding settings. Applying screenshots -
At the 1st pic default settings - UPnP turned ON.
Second pic: UPnP turned OFF, the port 6881 opened manually in router
It's either not able to configure the port specified, therefore falling back to random port, or you already have something else using that port.
I know you said you're using upnp... but it may be one of the cases where it doesn't work through whichever configuration you have, try manually allowing the port in your firewall/router and check to see that it does now successfully use the specified port.
[/quote]
First to say that I have no problems with my ISP filtering my traffic. With uTorrent I'm seeding like a boss
Every time with green icon, that's why it was unusual for me to saw indication for connection problem. Today I installed the new version 2.9.7 (uninstalled 2.9.5 first) and tested it with default settings. The result was the same - in every start qB gets random port disregarding settings. Applying screenshots -
At the 1st pic default settings - UPnP turned ON.
Second pic: UPnP turned OFF, the port 6881 opened manually in router
Last edited by Fingli on Mon Apr 02, 2012 4:02 pm, edited 1 time in total.
-
loki
Re: Ports don't match
Open the incoming port in router, not 6881... and see what it does differently, if any.
-
Fingli
Re: Ports don't match
Nope. I opened port 39894 and set it as default in options, but as you can see on the picture, qB is bound to some different (random) port
-
Splat
Re: Ports don't match
Getting the same thing here. I have 44445 set in QB's settings and port is correctly config'ed in the router. Yet QB keeps picking another port for TCP.