Leaderboard

hello what?? I'm quite new here and have been dealing with this AirVPN for the last few days. - Port forwarding does not seem to work properly here? Or am I too stupid? - tcp works without any problems, only udp doesn't want to do it at all, it seems to me, I've solved it differently now 😉 what you need: - 2 forwarded ports https://airvpn.org/ports/ - eMule.50a.MorphXT.12.7 oder eMule.50a.UltiMatiX_v5.0_31.08.2016_by_engo3k - edit: eMule ... what you want ... ( Your VPN IPv4 ) then enter the generated ports in eMule -> connection tcp and udp - Turn off UPnP under Connection - under Options/Advanced - Server and client LAN IPs filter check box - under Options/Advanced - assign internet connection 0.0.0.0 <- change - Windows .. Enter "cmd" in the search bar of the desktop and open the command prompt with "Right-click -> Run as administrator" (alternatively, you can also call up a command line with the Windows key + R). A DOS box opens in which you now type the command netstat -an. You will now see a list of all network connections on your computer. look for a number starting with 10. ... and enter this in eMule - under Options/Advanced - assign internet connection 0.0.0.0 <- enter - Close eMule to save the settings - Establish an AirVPN connection of your choice - PS: When you change the AirVPN server, the 10th ... IP also changes consequently CMD - netstat -an 10 .. read IP and enter again in eMule I hope it helps you one or the other let's rock the ed2k X Generation edit: not you Exit IP -> Your VPN IPv4 !!!

I discovered a simple quirk of setting up eMule (P2P) on Windows 10 that causes port forwarding to fail with AirVPN. This tip that may save others a lot of time. During setup eMule creates an inbound rule in Windows firewall that applies to private networks in scope. This makes sense if using eMule without a VPN. However, Windows treats the AirVPN as a public network. Consequently port forwarding with eMule and AirVPN will not work using the default inbound rule created during eMule setup. The solution is to edit the scope of the eMule inbound rule in Windows firewall to apply to both private and public profiles. The latter is the important one. This is simple to do: In Windows Firewall, right click on the inbound rule for eMule, select Properties, Advanced. Under Profiles check both Private and Public. I am not a security expert so feel free to chime in if this setting raises any concerns. This may also apply to earlier versions of Windows.