Search the Community

Hi, I'm on Linux Mint 21.1 and I've installed the Eddie client (version 2.21.8, installed via apt). When I open the Eddie window, I can use it to connect to the VPN, but if I close the window, it closes the VPN connection. I would expect the connection to stay up when the client window is closed. Is there any way to do that? I've looked it up and it doesn't seem to be a common issue. If this is a normal feature of Eddie, would switching to a CLI client solve the problem? Or would I need that terminal window to stay up as well? Thanks! Edit : I found the answer, im putting it here in case other people have the same question : simply right-click the tray icon and select "hide main window", very easy

Hey guys Long term user of AirVPN here. I love it, never EVER had any issues with it. I currently use on a media server that sits in the corner of a room. No monitor, etc. I use TeamViewer to connect to the machine (Peppermint Linux) and connect Eddie. When I activate the network lock, over TeamViewer, the connection stays up and I can click the "Connect to recommended server" no problem. However, when I'm finished, and I disconnect Eddie, the TeamViewer connection drops and I cannot use it to deactivate the network lock (clearly because the network lock has stopped TeamViewer from connecting) My questions are: Why doesn't activating the network lock block TeamViewer before connecting (although I'm not overly fussed about knowing why) Is there a way of telling the network lock to allow connections from the LAN? At least if TeamViewer dropped off, I could then perhaps SSH in from another machine and deactivate the network block, for instance Anyway, its a pure annoyance, and not really AirVPN's fault - its doing its job. I'd just like to know if there is a solution, currently I have to hard reset the server when it happens (I could turn on the monitor but more often than not, it doesn't receive a signal from the graphics card - dodgy GVX card I think) I'm using Eddie 2.19.7 Thanks in advance, uwu73

Hi guys! So I am attempting to setup my Transmission bittorrent client with Transdrone (Transdroid) app on Android. I want to be able to use this android remote app to connect to my desktop (where Transmission is running) while I am connected to this VPN. So I: 1) Connected to a server (say Server A). 2) Configured port forwarding on AirVPN's site (AirVPN > Client Area > Forwarded ports). Let's say I forwarded port 7712 and 7713. 3) Logged into Transmission and set port 7712 as the Incoming port (Transmission > Preferences > Network) and made sure 'Pick a random port at startup' was unchecked. 4) Allowed remote access (HTTP) from port 7713 and configured username/password authentication. Made sure 'Only allow these IP addresses' was unchecked. 5) Then set my firewall to allow incoming connections from port 7712 and 7713 (TCP). * I DID NOT log into my router and configure port forwarding for these ports (or any for that matter). When I hit the 'Test Port' button (Transmission > Network) to test port 7712, it says 'Port is OPEN'. Cool. ----- So what is my post about? Well there are some instructions on this page that confuse the heck outta me: https://airvpn.org/faq/p2p/ I do not understand what is being communicated here... "If you forward a port for a p2p torrent client, do NOT remap it to a different local port and make sure that the torrent client port matches the remotely forwarded port number" - What is meant by "do not remap it to a different local port"? Am I supposed to log into my router and setup port forwarding for port 7712 & 7713? "do NOT forward on your router the same ports you use on your Bittorrent or eMule client (or any other listening service) while connected to the VPN" - Doesn't this contradict the previous instruction? What is the correct way to configure port forwarding so that my P2P client will work with my android remote app? (and seed)