Search the Community
Showing results for tags 'device manager'.
Found 2 results
Hello, I have a couple of questions regarding AirVPN's port forwarding/DDNS service and the "new" multiple Device keys per user feature: From your "What is Dynamic DNS" section I can read: When a Premium member connects to an Air VPN server, the .airdns.org DNS record is updated to the exit-IP address of that server. Therefore, be aware that this service may be unusable when you establish multiple connections to different servers from different devices with the same account (in such cases, you need to point directly to the exit-IP address of the server, or use some third-party DDNS which you manually set). I understand how this worked before the multiple Device keys feature came into play but now we can have multiple devices connected to the same server, in which case my guess is that not even trying to point directly to the exit-IP address would make the port forwarding work. My suggestion is to relate de DDNS service to a Device key. For example, adding a "Device key" selector to the port forwarding menu. This way we would have 2 benefits. First, DDNS service would work as long as there were only one device using the related Device key, letting the user have some other connections at the same time. Second, even if a user ended up with a second connection to the very same server, the port forwarding feature would still work for the device with the proper Device key. Thanks in advance for your comments.
Guys, It seems I have had the problem of several other people concerning connection issues. After Installing the AirVPN client which in turn installs the open VPN driver. After the first server connection with seems to corrupt my secondary adapter which is a broadcom ethernet adapter. I have found a workaround by going to device manager and deleting both the Broadcom driver and the TAP_V9 driver. Then I performed a scan for hardware change and Windows will reinstall my ethernet driver. Everything will function normally until the next time I connect via AirVPN. Additional notes: on my custom gig I have the option to connect either through a ethernet cable or Wi-Fi. I find that even when unable to connect via the ethernet, I am still able to connect via Wi-Fi. This leads me to believe that there is a conflict between the Broadcom driver and the TAP-V9 (OpenVPN driver). Y'all have a nice day, Greg