[SOLVED] Closed Ports Issue

luceph · 2017-05-19 02:29:23

I have a port forwarded on the router for bittorrents and a static IP set; the port is recognized open on Windows. When I check if this port is open on Arch, however, it is closed. Searching tells me that all ports should be open by default. iptables -L gives:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Wondering what might be wrong?

Last edited by luceph (2017-05-19 20:57:11)

seth · 2017-05-19 06:23:48

And do you have a torrent client operating on that port running...?

luceph · 2017-05-19 17:14:21

Yes/no, it was closed both ways. Checking other free range ports, they're closed, too.

Okay so, I have an rtorrent user running via screen and rtorrent loaded with systemctl as per the wiki. I have rutorrent set up with nginx as per the wiki, as well. ruTorrent reports no issues, aside from the port being closed. Seeing that port 80 is described in the nginx.conf and when I check, it is open (I have 80, and 6881-6999 ports forwarded, not sure if that is necessary), I'm guessing that I probably need to declare my chosen port as well in the conf file? I've no experience with nginx, I'm just looking to get rutorrent up and running. I've had rtorrent up and running without rutorrent fine. Is this the case?

Thanks.

Last edited by luceph (2017-05-19 17:15:21)

seth · 2017-05-19 17:28:23

You do usually not need to forward ports just to use a random torrent client.
They'll UPnP out - unless you deactivate the feature in your router.

nginx is a http server and has nothing to do with bittorrent. If you need to forward ports, you'll have to configure your torrent client to a port or port range that matches the forwarding in the router.
I don't know rutorrent, but it seems like a web frontend to rtorrent, which you'll usually use locally (ie. from localhost or at least in the same LAN) - you do not have to forward anything in this case - port forwarding is for NAT, it's not a firewall (though it provides soem implicit protection)

luceph · 2017-05-19 17:54:18

EDIT: Looks to be a router issue. I'll have to mess around with it. Thanks for the help. I wasn't sure if it could be software-side, so you confirmed it couldn't be. Cheers

Last edited by luceph (2017-05-19 18:07:57)

luceph · 2017-05-19 18:21:49

UPDATE: Trying to setup a systemd service as a user file instead of a system file, I get this :

[rtorrent@arch user]$ systemctl --user enable rtorrent.service
Failed to connect to bus: Permission denied

As root:

root@arch /etc/systemd/user # systemctl --user enable rtorrent.service
Failed to connect to bus: Operation not permitted

Could this be related? Any ideas of what could be the cause?

Thanks.

EDIT: Nevermind, running the command as my main user succeeds.

Last edited by luceph (2017-05-19 18:27:43)

seth · 2017-05-19 18:58:32

You need rtorrent running, either as user or root. Either directly or via service. Unless there's a torrent client running, no port will be opened.
Please read on at https://wiki.archlinux.org/index.php/RTorrent

If you want to figure whether it's working, just try to fetch the arch iso, see https://www.archlinux.org/download/

luceph · 2017-05-19 20:56:01

Thanks, I do already know that rtorrent needs to be running. I have it automatically run via an rtorrent user with tmux as described in the wiki (I tried screen, but it wasn't working properly).

It's actually all working now, it was definitely a router issue. I didn't realize the router had an innate firewall.

Last edited by luceph (2017-05-19 21:13:58)

Arch Linux

#1 2017-05-19 02:29:23

[SOLVED] Closed Ports Issue

#2 2017-05-19 06:23:48

Re: [SOLVED] Closed Ports Issue

#3 2017-05-19 17:14:21

Re: [SOLVED] Closed Ports Issue

#4 2017-05-19 17:28:23

Re: [SOLVED] Closed Ports Issue

#5 2017-05-19 17:54:18

Re: [SOLVED] Closed Ports Issue

#6 2017-05-19 18:21:49

Re: [SOLVED] Closed Ports Issue

#7 2017-05-19 18:58:32

Re: [SOLVED] Closed Ports Issue

#8 2017-05-19 20:56:01

Re: [SOLVED] Closed Ports Issue

Board footer