You are not logged in.

Pages: 1

#1 2012-08-26 16:33:11

bruno321
Member
Registered: 2010-03-05
Posts: 89

Can't open ports

I'm trying to open ports for a bittorrent application, but for some reason it doesn't work.

I've used the port forwarding option of my router to open port 50010, both tcp and udp.

I have configured an application (qbittorrent) to use it, and it seems to be listening (if I'm interpreting the following right):

 # netstat -tnlp | grep qbittorrent
tcp        0      0 0.0.0.0:4433            0.0.0.0:*               LISTEN      799/qbittorrent     
tcp        0      0 0.0.0.0:50010           0.0.0.0:*               LISTEN      799/qbittorrent     
tcp6       0      0 :::4434                 :::*                    LISTEN      799/qbittorrent     
tcp6       0      0 :::50010                :::*                    LISTEN      799/qbittorrent

However, canyouseeme.org times out on port 50010. Same thing happens with another app.

I have no iptables or any other firewall installed on my system.

How can I effectively open ports?

Thanks.

Offline

#2 2012-08-27 00:20:40

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: Can't open ports

1) That output shows that TCP is listening. Add -u to the netstat command to confirm UDP is also listening.
2) Run `tcpdump -lnn -i eth0 port 500101` while you are doing your tests to confirm that your router is forwarding packets correctly.

EDIT: replace 'eth0' in the above command with your actual network interface.

Last edited by fukawi2 (2012-08-27 00:21:08)

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#3 2012-12-20 21:36:36

bruno321
Member
Registered: 2010-03-05
Posts: 89

Re: Can't open ports

I know it's been a few months since this post, but I had forgotten about it, and now I'm ready to continue fighting this problem that persists.

 $ sudo netstat -tnlpu | grep qbittorrent
tcp        0      0 0.0.0.0:4433            0.0.0.0:*               LISTEN      984/qbittorrent     
tcp        0      0 0.0.0.0:50010           0.0.0.0:*               LISTEN      984/qbittorrent     
tcp6       0      0 :::4434                 :::*                    LISTEN      984/qbittorrent     
tcp6       0      0 :::50010                :::*                    LISTEN      984/qbittorrent     
udp        0      0 192.168.1.143:38701     0.0.0.0:*                           984/qbittorrent     
udp        0      0 0.0.0.0:50010           0.0.0.0:*                           984/qbittorrent     
udp        0      0 127.0.0.1:60930         0.0.0.0:*                           984/qbittorrent     
udp        0      0 192.168.1.143:6771      0.0.0.0:*                           984/qbittorrent     
udp        0      0 127.0.0.1:6771          0.0.0.0:*                           984/qbittorrent     
udp        0      0 0.0.0.0:6771            0.0.0.0:*                           984/qbittorrent

and the tcpdump command outputs a lot of these lines:

 19:31:06.199748 IP 98.102.191.178.34496 > 192.168.1.143.50010: UDP, length 131
19:31:06.203639 IP 98.102.191.178.34496 > 192.168.1.143.50010: UDP, length 20
19:31:06.224201 IP 198.203.29.133.51413 > 192.168.1.143.50010: UDP, length 20
19:31:06.229585 IP 188.165.12.62.63917 > 192.168.1.143.50010: UDP, length 20
19:31:06.280724 IP 121.221.223.46.44443 > 192.168.1.143.50010: UDP, length 294
19:31:06.280755 IP 192.168.1.143.50010 > 121.221.223.46.44443: UDP, length 88

The problem must be a problem with my PC, because another PC (using Ubuntu) is connected the same way as mine and doesn't have any port problems. I've checked the setup on the router configuration a gazillion times. Please, how can I fix this?

Edited to add: canyouseeme.org outputs "Error: I could not see your service on (ip) on port (50010)
Reason: Connection refused".

Last edited by bruno321 (2012-12-20 21:41:24)

Offline

#4 2012-12-20 22:19:33

fukawi2
Ex-Administratorino
From: .vic.au
Registered: 2007-09-28
Posts: 6,224
Website

Re: Can't open ports

 19:31:06.199748 IP 98.102.191.178.34496 > 192.168.1.143.50010: UDP, length 131
19:31:06.203639 IP 98.102.191.178.34496 > 192.168.1.143.50010: UDP, length 20
19:31:06.224201 IP 198.203.29.133.51413 > 192.168.1.143.50010: UDP, length 20
19:31:06.229585 IP 188.165.12.62.63917 > 192.168.1.143.50010: UDP, length 20
19:31:06.280724 IP 121.221.223.46.44443 > 192.168.1.143.50010: UDP, length 294
19:31:06.280755 IP 192.168.1.143.50010 > 121.221.223.46.44443: UDP, length 88

qbittorrent must be doing something strange; all of these show the traffic reaching your PC successfully, but only the last one actually gets a response from qbittorrent. You can see on the last line that 121.221.223.46 sent a packet from port 44443 to you on port 50010, and then qbittorrent responded back to that address on port 44443.

If it wasn't for that last line, I would say you had iptables or similar blocking traffic, but that last line (packet) confirms that qbittorrent is getting the incoming packets, it's just not responding to a lot/most of them.

Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?

BlueHackers // fscanary // resticctl

Offline

#5 2012-12-21 00:41:10

bruno321
Member
Registered: 2010-03-05
Posts: 89

Re: Can't open ports

How odd. Here's another batch of those:

 22:31:14.310418 IP 95.105.75.105.59637 > 192.168.1.143.50010: UDP, length 335
22:31:14.310445 IP 192.168.1.143.50010 > 95.105.75.105.59637: UDP, length 20
22:31:14.333942 IP 192.168.1.143.50010 > 68.48.22.151.51777: UDP, length 487
22:31:14.338803 IP 216.58.62.116.59266 > 192.168.1.143.50010: UDP, length 20
22:31:14.349821 IP 85.48.244.231.64545 > 192.168.1.143.50010: UDP, length 232
22:31:14.349852 IP 192.168.1.143.50010 > 85.48.244.231.64545: UDP, length 20
22:31:14.349989 IP 192.168.1.143.50010 > 85.48.244.231.64545: UDP, length 20
22:31:14.433972 IP 192.168.1.143.50010 > 24.84.237.186.51413: UDP, length 20
22:31:14.462503 IP 107.193.193.210.51324 > 192.168.1.143.50010: UDP, length 303
22:31:14.462543 IP 192.168.1.143.50010 > 107.193.193.210.51324: UDP, length 20
22:31:14.475157 IP 184.38.107.32.6688 > 192.168.1.143.50010: UDP, length 223
22:31:14.475262 IP 192.168.1.143.50010 > 184.38.107.32.6688: UDP, length 20
22:31:14.480576 IP 192.168.1.143.50010 > 87.188.196.90.56447: UDP, length 101
22:31:14.483699 IP 151.237.15.155.51650 > 192.168.1.143.50010: UDP, length 275
22:31:14.483761 IP 192.168.1.143.50010 > 178.117.96.158.58431: UDP, length 101
22:31:14.495147 IP 2.137.166.192.12808 > 192.168.1.143.50010: UDP, length 20
22:31:14.495174 IP 192.168.1.143.50010 > 2.137.166.192.12808: UDP, length 20
22:31:14.499612 IP 80.213.243.80.49203 > 192.168.1.143.50010: UDP, length 20
22:31:14.533986 IP 192.168.1.143.50010 > 184.38.107.32.6688: UDP, length 552
22:31:14.534014 IP 192.168.1.143.50010 > 107.193.193.210.51324: UDP, length 513
22:31:14.578595 IP 192.168.1.143.50010 > 68.57.50.174.22135: UDP, length 101

As I didn't know what to look for, perhaps the few lines I pasted on my previous post were not representative. This one doesn't seem to have so few outgoing packets.


The other PC has no problem and I also used qbittorrent for testing.

Well, I tried it now with deluge and it works fine (canyouseeme succeeds).

Last edited by bruno321 (2012-12-21 01:09:24)

Offline

Pages: 1

Board footer

Powered by FluxBB