380.68_4 - Transmission port is always closed

[Kanuki]

Hi..

Something wrong with my 3200 and Transmission.

Transmission is always showing that the port is closed

even though I've already open the port in firewall-start script.

#!/bin/sh
iptables -I INPUT -p tcp --destination-port 10501 -j ACCEPT
iptables -I INPUT -p udp --destination-port 10501 -j ACCEPT

I don't have any problem with downloading at all.

Restarting the router will not help. The only way to open
it back is to change the port number. But it only help for 10-15 mins
then it will be closed back again.

I also have already checked the port whether it's blocked by my ISP
or not by using this website. http://www.portchecktool.com/ and
it's not blocked

 

[joegreat]

Transmission is always showing that the port is closed

I noticed the same on my setup recently: Transmission claims that the 51413 port is closed. Was setting the firewall rules in the firewall-start script:
chief@RT-AC87U:/tmp/home/root# iptables -L | grep 51413
ACCEPT udp -- anywhere anywhere udp dpts:51413:51414
ACCEPT tcp -- anywhere anywhere tcp dpts:51413:51414

But the Transmission still claims that the port is closed.

Only after I added the firewall rules via the GUI under WAN / Virtual Server / Port Forwarding (with additional 6881 TCP port) towards the local router IP it says now the port is open - but iptables does not show it...

 

[st3v3n]

Kanuki, joegreat, my 3200 on 380-69_4 has exibited similar issues; changing ports doesn't make a difference and the problem reoccurs. I use the GUI, but when I saw your post wondered if it could be related to why time lookups occaisionally fail. Just a shot in the dark, but until today, haven't heard of this happening to another other model, except for your AC87. Cheers.

 

[Omega69]

My AC56U has same "issue". Already for several versions. But using it rarely so haven't met any trouble

Odesláno z mého ONEPLUS A5000 pomocí Tapatalk

 

[accolito]

Try this:

iptables -t nat -I VSERVER -p udp -m udp --dport (PORT2OPEN) -j DNAT --to-destination (LANIP):(PORT2OPEN)
iptables -t nat -I VSERVER -p tcp -m tcp --dport (PORT2OPEN) -j DNAT --to-destination (LANIP):(PORT2OPEN)

Where (LANIP) is the IP address of your lan PC and (PORT2OPEN) is the port you want to open - example:

iptables -t nat -I VSERVER -p udp -m udp --dport 49999 -j DNAT --to-destination 192.168.2.99:49999

To remove the rule, just replace -I with -D
Hope it helps

 

[Kanuki]

Try this:

iptables -t nat -I VSERVER -p udp -m udp --dport (PORT2OPEN) -j DNAT --to-destination (LANIP):(PORT2OPEN)
iptables -t nat -I VSERVER -p tcp -m tcp --dport (PORT2OPEN) -j DNAT --to-destination (LANIP):(PORT2OPEN)

Where (LANIP) is the IP address of your lan PC and (PORT2OPEN) is the port you want to open - example:

iptables -t nat -I VSERVER -p udp -m udp --dport 49999 -j DNAT --to-destination 192.168.2.99:49999

To remove the rule, just replace -I with -D
Hope it helps

If the Transmission is an Entware on the router itself mean that LANIP is the router local IP right?

 

[accolito]

If the Transmission is an Entware on the router itself mean that LANIP is the router local IP right?

No, in such case you've to use this:

iptables -I INPUT -i eth0 -p udp -m udp --dport (PORT2OPEN) -j ACCEPT
iptables -I INPUT -i eth0 -p tcp -m tcp --dport (PORT2OPEN) -j ACCEPT

 

[Kanuki]

I noticed the same on my setup recently: Transmission claims that the 51413 port is closed. Was setting the firewall rules in the firewall-start script:
chief@RT-AC87U:/tmp/home/root# iptables -L | grep 51413
ACCEPT udp -- anywhere anywhere udp dpts:51413:51414
ACCEPT tcp -- anywhere anywhere tcp dpts:51413:51414

But the Transmission still claims that the port is closed.

Only after I added the firewall rules via the GUI under WAN / Virtual Server / Port Forwarding (with additional 6881 TCP port) towards the local router IP it says now the port is open - but iptables does not show it...

No, in such case you've to use this:

iptables -I INPUT -i eth0 -p udp -m udp --dport (PORT2OPEN) -j ACCEPT
iptables -I INPUT -i eth0 -p tcp -m tcp --dport (PORT2OPEN) -j ACCEPT

Doen't work for me.

Do I need to remove these 2 lines first?

iptables -I INPUT -p tcp --destination-port 10501 -j ACCEPT
iptables -I INPUT -p udp --destination-port 10501 -j ACCEPT

 

[st3v3n]

Just noticed this thread, and am beginning to wonder if this is somehow related to the date/time change bug and/or hack that's been popping up on my AC3200? Happened again yesterday. v380.68_4 has been great, no other issues, but when this port/time swap thing happens each month, it's starting to be part of a routine that isn't fun.

 

[accolito]

Doen't work for me.

Do I need to remove these 2 lines first?

iptables -I INPUT -p tcp --destination-port 10501 -j ACCEPT
iptables -I INPUT -p udp --destination-port 10501 -j ACCEPT

It depends on how your wan connection is configured. Do you use PPTP or PPPoE?

 

[Kanuki]

It depends on how your wan connection is configured. Do you use PPTP or PPPoE?

It's PPPoE.

 

[accolito]

I was suspecting that.
Use this, it will work

iptables -I INPUT -i ppp0 -p udp -m udp --dport (PORT2OPEN) -j ACCEPT
iptables -I INPUT -i ppp0 -p tcp -m tcp --dport (PORT2OPEN) -j ACCEPT

 

[joegreat]

I also changed to the firewall rules with WLAN interface information (in my case vlan2) and now it works for me also.

# Transmission ports enabled
/usr/sbin/iptables -I INPUT -i vlan2 -p tcp -m tcp --dport 51413 -j ACCEPT
/usr/sbin/iptables -I INPUT -i vlan2 -p udp -m udp --dport 51413 -j ACCEPT

 

[Kanuki]

Nothing here works

 

[joegreat]

Nothing here works

Great to hear! Can you specify 'nothing' for others to follow your recommendation...

 

[TeHashX]

Try to switch nat loopback to Merlin or Asus under Firewall settings

 

[Kanuki]

Try to switch nat loopback to Merlin or Asus under Firewall settings

switched from ASUS to Merlin still not fixed. T_T

 

[TeHashX]

In the screenshot I see you didn't check: Use port forwarding from my router

 

[Kanuki]

In the screenshot I see you didn't check: Use port forwarding from my router

Checked it but doesn't help.

 

[TeHashX]

Maybe transmissionbt detection method is not accurate. Start a torrent then go to http://canyouseeme.org and see if the port is open.