Jump to content
Not connected, Your IP: 216.73.216.49

Leaderboard


Popular Content

Showing content with the highest reputation on 10/11/22 in Posts

  1. 1 point
    Hello! You need the default option in the command. Check also https://eddie.website/support/cli/ In case you run Linux (your mention of eth0 makes us think of *BSD and Linux) you might like to consider the AirVPN Suite as a total replacement, in particular Goldcrest and Bluetit included in the suite, which will provide you with the maximum flexibility you're looking for and at the same time the security provided by a robust client-server architecture: https://airvpn.org/suite/readme/ The AirVPN Suite, currently, does not offer a GUI at all and is specifically aimed at those many users who prefer a command line interface over a GUI. However, currently it does not support WireGuard (next version will). Kind regards
  2. 1 point
    This is normal for Google. Since geoIP is such a mess, they don't completely trust what geoIP databases report. Instead they use the data they get from browsers visiting from each IP and try to guess if some IP is now being used elsewhere. Since Russia is currently heavily censoring internet access, AirVPN likely has a lot of Russian users who happen to be using NL servers. Google detects a lot of users with Russian locale are using NL node IPs -> they start offering Russian site by default. Not sure if there are workarounds for this, other than logging in. But this is not a sign of compromise, so no need to be paranoid. If Russia really was listening, they wouldn't route traffic through Russia. ;)
  3. 1 point
    For your comfort and peace of mind, check with traceroute (tracert in Windows) or mtr, and/or access various end points which tell you the IP address your packets come from. Typical speed tests sites and "what is my address" web services are perfect. Compare the IP address you get with the supposed exit-IP address of the VPN server you're connected to and verify they match. Finally, query the IANA database (with whois) for a final cross-check. Repeat multiple times for each server to minimize the likelihood that you end up to services which are accomplices of the attackers and therefore mask your IP address making you believe that you have a perfectly fine IP address while in reality your packet has come out from inside the evil Russian network. As a welcome and smart side-effect, while the attackers could do nothing with the data in transit inside their nodes because of end-to-end encryption, a re-routing of such a kind which would add an additional exit node would turn infringement notices against us exactly to zero, and alas this is not what we observe, not at all 🙄. We have never met such kind and gentle attackers, unfortunately. Kind regards 😋
×
×
  • Create New...