Search the Community
Showing results for tags 'forwarded ports'.
Found 7 results
-
Hi, I have a problem that may come from eddie or my system. I recently switched to linux from windows, so I’m not well known in how things are working. I’ve configured the OpenSSH server on my laptop. I’m not using the port 22 but another port X. It’s working when ssh-ing on it’s local IP from another device on my LAN (and also from itself on localhost). I have eddie installed on the laptop, configured and working on the device "Laptop". ❯ sudo ip addr show dev Eddie 10: Eddie: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1320 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet [IPv4]/32 scope global Eddie valid_lft forever preferred_lft forever inet6 [IPv6]/128 scope global valid_lft forever preferred_lft forever I have a forwarded port set in the client area from port Y :2 to port X, set to the correct device "Laptop". I’ve set a [ABC].airdns.org DDNS on that forwarded port. That forwarding was working when I was on windows to connect to a ssh server listening on the same port X. I’ve added UFW rules to allow connections from Anywhere to port X for IPv4 and IPv6. ❯ sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), disabled (routed) New profiles: skip To Action From -- ------ ---- [port X]/tcp ALLOW IN Anywhere (log) [port X]/tcp (v6) ALLOW IN Anywhere (v6) (log) When ssh-ing to the [ABC].airdns.org on port Y from another device not using a vpn, UFW is receiving the connection on port X and allowing it(I’ve anonymized the IP and ports in the following logs.) 2025-02-14T17:20:12.329780+01:00 laptop kernel: [UFW ALLOW] IN=Eddie OUT= MAC= SRC=[device IPv6] DST=[local Eddie IPv6] LEN=80 TC=40 HOPLIMIT=50 FLOWLBL=855788 PROTO=TCP SPT=42266 DPT=[port X] WINDOW=65535 RES=0x00 SYN URGP=0 2025-02-14T17:20:43.790702+01:00 laptop kernel: [UFW ALLOW] IN=Eddie OUT= MAC= SRC=[device IPv4] DST=[local Eddie IPv4] LEN=60 TOS=0x08 PREC=0x20 TTL=55 ID=43836 DF PROTO=TCP SPT=43944 DPT=[port X] WINDOW=65535 RES=0x00 SYN URGP=0 sshd is not getting the connections as the output stays listening. ❯ sudo /usr/sbin/sshd -d debug1: sshd version OpenSSH_9.6, OpenSSL 3.0.13 30 Jan 2024 debug1: private host key #0: [CENSORED] debug1: private host key #1: [CENSORED] debug1: private host key #2: [CENSORED] debug1: Set /proc/self/oom_score_adj from 200 to -1000 debug1: Bind to port [PORT X] on 0.0.0.0. Server listening on 0.0.0.0 port [PORT X]. debug1: Bind to port [PORT X] on ::. Server listening on :: port [PORT X]. The ssh client is trying the server IPv4, then IPv6, before timing out. ❯ ssh lapa -v OpenSSH_9.6p1 Ubuntu-3ubuntu13.5, OpenSSL 3.0.13 30 Jan 2024 debug1: Reading configuration data [HOME]/.ssh/config debug1: [HOME]/.ssh/config line 6: Applying options for lapa debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to [ABC].airdns.org [IPv4] port [port Y]. debug1: connect to address [IPv4] port [port Y]: Connection timed out debug1: Connecting to [ABC].airdns.org [IPv6] port [port Y]. debug1: connect to address [IPv6] port [port Y]: Connection timed out ssh: connect to host 41r.airdns.org port 55107: Connection timed out ssh-ing from my laptop to [ABC].airdns.org on port Y does not work either, but it’s not logged by the firewall. Either it’s not going through the firewall because it’s routing to the local Eddie interface, or it’s blocked by the VPN config. When trying the "Test open" functionality in the client area for that forwarded port, both IPv4 and IPv6 are shown as opened. The sshd receives the test connections as can be seen by the output of the debug mode (only the IPv4 is shown here as the sshd quit after the first connection in debug mode). ❯ sudo /usr/sbin/sshd -d debug1: sshd version OpenSSH_9.6, OpenSSL 3.0.13 30 Jan 2024 debug1: private host key #0: [CENSORED] debug1: private host key #1: [CENSORED] debug1: private host key #2: [CENSORED] debug1: Set /proc/self/oom_score_adj from 200 to -1000 debug1: Bind to port [PORT X] on 0.0.0.0. Server listening on 0.0.0.0 port [PORT X]. debug1: Bind to port [PORT X] on ::. Server listening on :: port [PORT X]. debug1: Server will not fork when running in debugging mode. Connection from 142.93.172.65 port 44700 on [IPv4] port [PORT X] rdomain "" debug1: Local version string SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.5 kex_exchange_identification: Connection closed by remote host Connection closed by 142.93.172.65 port 44700 It generates the following UFW logs: 2025-02-14T17:31:46.608668+01:00 laptop kernel: [UFW ALLOW] IN=Eddie OUT= MAC= SRC=142.93.172.65 DST=[local Eddie IPv4] LEN=60 TOS=0x00 PREC=0x00 TTL=55 ID=33260 DF PROTO=TCP SPT=44700 DPT=[port X] WINDOW=64240 RES=0x00 SYN URGP=0 2025-02-14T17:31:46.616753+01:00 laptop kernel: [UFW ALLOW] IN=Eddie OUT= MAC= SRC=2a03:b0c0:0003:00d0:0000:0000:0d02:6001 DST=[local Eddie IPv6] LEN=80 TC=0 HOPLIMIT=56 FLOWLBL=721782 PROTO=TCP SPT=35088 DPT=[port X] WINDOW=64800 RES=0x00 SYN URGP=0 I’m out of ideas where to look next. If someone knows where the problem could lay, I would greatly appreciate.
-
Hello everyone, I’m facing an issue with my current setup and would appreciate your help. Here’s my configuration: • NAS Synology, DSM 7.2.2 • OpenVPN profile set up in the network interface • I followed this tutorial for the setup: (How-to: AirVPN on Synology DSM6 and DSM7 complete guide) • Port forwarding works fine with Download Station For several weeks now, I’ve been experiencing frequent VPN disconnections without any clear explanation. For over a year, I didn’t have any issues—my sessions were stable for weeks or even months. However, recently, my connections keep dropping, and I lose port forwarding. Oddly, on the AirVPN “Session” page, the connection still appears active. On the port forwarding page, I get the error “Connection timed out 110.” In DSM, the default gateway switches to LAN when the connection drops, even though the network interface shows that I’m still connected. I’ve tried changing servers and updating everything, but the problem persists. This is quite frustrating because when the connection drops, port forwarding with Download Station becomes ineffective, leaving me unprotected. If anyone has any ideas or solutions, I’d greatly appreciate your input. Thanks in advance for your help!
-
I have a computer connected to AirVPN using openvpn. I forwarded a port into the "Client Area configurations" and if I check the port by click on "Test open" I receive "Open!" for both ipv4 and ipv6 protocols: my computer is listening the open port correctly on both IP protocol. If I use another computer connected to internet out of AirVPN and I check the open port using ipv4 protocol: nmap <ipv4_of_AirVPN_device> -sV -Pn -p <port_to_check> -4 I receive "open" but if check using ipv6 protocol: nmap <ipv6_of_AirVPN_device> -sV -Pn -p <port_to_check> -6 I receive "filtered". I also can't use the service listening on that port unless I force the use of the ipv4 protocol. What could be the problem? Why is my ip not correctly forwarded despite the AirVPN check being successful?
-
I have the following set up: ISP Modem --> Protectli(OPNsense-AirVPN Wireguard) --> Netgear R7000 Access Point(Fresh Tomato) --> My Lan (of which there is one hardwired computer running an apache webserver) I have a nextcloud instance running on the apache webserver. I want to be able to access the nextcloud instance remotely. OPNsense has an option available for various Dynamic DNS (DDNS) services. I had the DDNS service for duckdns working and I could access my nextcloud server remotely before I changed to AirVPN as my VPN (I was using Mulvad). Now I want to accomplish the same thing with AirVPN without using duckdns but by using AirVPN's DDNS. The problem is that I cannot even get started. When I go to the AirVPN ports page, click on "Request a new port" and then click on "Test open". The connection times out (110) for TCP but seems to work for UDP (at least I don't see any error for UDP). This happens regardless of whether I leave the local port empty, fill in the local port with the same port number as the assigned port or use port 80 for the local port. Also it doesn't matter if I fill in the xxxx.airdns,org or not. "CanYouSeeMe" reports the ports as closed for for all my attempts. I have tried this on my local internet as well as on my cell phone data plan without any difference. I feel like I am missing something fundamental but have no idea what it is. Any help would be much appreciated. Thanks. bdika
-
ANSWERED Help with SoulSeek and forward porting
nubdubnub posted a topic in Troubleshooting and Problems
Hi everyone, I purchased AirVPN recently to use it with a p2p file sharing application SoulSeek. I'm very new to this stuff and really in need of some guidance. I was able to add my 2 ports in the "client area" section of the AirVPN website. Then I ran a TCP test check and recieved the message, "Not reachable on server IP over the external port #####, tcp protocol. Error 110 - connection timed out". I'm not into torrenting, I just want to use this VPN for Soulseek. I haven't done anything to my router since I'm not comfortable messing with the settings on it. Also when I check the ports on SoulSeek it also says the ports are closed. Any guidance is most welcomed! -Nub -
Hi i have problem with start qbittorrent. Connection works fine, for webbrowsing, but qbittorrent have no connection. I created forwarded port (testing always have: 110 connection timeout), I updated this port in my bittorrent settings (port used for incomming connections), I disabled all firewalls for test (windows and comodo), I disabled upnp and nat-pmp in qbittorrent,In bittorrent i have yellow circle: No direct connections. In airvpn site, when im testing forwarded port i have always black circle with 110 error). PROBLEM SOLVED : i think trackers was blocking me, i generated new torrents and works fine, thanks
-
Hello, I'm having an issue where I cannot download torrents since I did port forwarding. I forwarded my port through the website because qBittorrent had a yellow "connection status." I set the port in qBittorrent, and now the "connection status" is green, but torrents are not downloading. I did this yesterday, and when I initially forwarded my port, it was working just fine, and today it's not. Also, I was able to run the "TCP Test" and got a green light yesterday. I ran it today, and it stays gray. Not sure what that means, but figured I should include that info. Any suggestions? Thank you, all