Jump to content
Not connected, Your IP: 35.173.35.159

Search the Community

Showing results for tags 'DNS'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP
    • Mirrors

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 181 results

  1. Yesterday, within 10 minutes, IPTABLES blocked more than 200 outbound packets on port 88 on tun0, with SRC=10.50.0.106 (AirVPN DNS through SSL tunnel) and DST= three IP addresses: 184.75.214.162 (amanah.com), 184.75.221.2 (amanah.com), and 46.19.137.114 (regika.com). I understand these are both AirVPN servers. At the time, I was connected to Carinae through an SSL tunnel. A little googling suggests the traffic was connected to recursive AirVPN DNS servers. Would the fact that the packets were blocked cause any problems? It didn't seem to, but would it be advisable to add an IPTABLES rule allowing outbound traffic on tun0 port 88 where SRC=10.50.0.0/24?
  2. Hi there, Just installed AirVPN. I can connect to airvpn.org without any issues, but not to any other site. I have tried both with UDP and TCP. I'm using Bodhi Linux. If I ping 10.4.0.1 everything seems to be fine: PING 10.4.0.1 (10.4.0.1) 56(84) bytes of data. 64 bytes from 10.4.0.1: icmp_req=1 ttl=64 time=226 ms 64 bytes from 10.4.0.1: icmp_req=2 ttl=64 time=136 ms 64 bytes from 10.4.0.1: icmp_req=3 ttl=64 time=137 ms 64 bytes from 10.4.0.1: icmp_req=4 ttl=64 time=136 ms 64 bytes from 10.4.0.1: icmp_req=5 ttl=64 time=136 ms 64 bytes from 10.4.0.1: icmp_req=6 ttl=64 time=252 ms 64 bytes from 10.4.0.1: icmp_req=7 ttl=64 time=141 ms 64 bytes from 10.4.0.1: icmp_req=8 ttl=64 time=258 ms 64 bytes from 10.4.0.1: icmp_req=9 ttl=64 time=244 ms 64 bytes from 10.4.0.1: icmp_req=10 ttl=64 time=230 ms 64 bytes from 10.4.0.1: icmp_req=11 ttl=64 time=205 ms 64 bytes from 10.4.0.1: icmp_req=12 ttl=64 time=137 ms 64 bytes from 10.4.0.1: icmp_req=13 ttl=64 time=137 ms 64 bytes from 10.4.0.1: icmp_req=14 ttl=64 time=136 ms ^C --- 10.4.0.1 ping statistics --- 14 packets transmitted, 14 received, 0% packet loss, time 13054ms rtt min/avg/max/mdev = 136.783/179.914/258.041/50.208 ms Same if I ping 8.8.8.8: PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_req=1 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=5 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=6 ttl=48 time=178 ms 64 bytes from 8.8.8.8: icmp_req=7 ttl=48 time=178 ms ^C --- 8.8.8.8 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6026ms rtt min/avg/max/mdev = 178.244/178.580/178.917/0.377 ms traceroute google.com doesn't produce any results, it just hangs in there forever. Thanks!
  3. EDIT 20:04 CET+1 06-May-13 Problem solved Hello! We regret to inform you that we are currently experiencing DNS problems on the following servers in the Netherlands: Ophiuchi LeporisLyncisOrionisCastorCorviThe problem affects DNS resolution. You might be unable to resolve some (and only some) names with our internal DNS (10.4.0.1, 10.5.0.1, ... , 10.9.0.1). The problem is external: it is not caused by our DNS or configuration. We're anyway working to solve it as soon as possible. In the meantime, as a momentary work-around (not compromising security): on Linux, OpenBSD and FreeBSD, just set a public DNS on your nameservers list after the connection. Example: in /etc/resolv.conf add the line "nameserver "on Windows, on your TAP-Win32 network interface (NOT on your physical network card) after the connection set preferred and alternate DNS IP addressalternatively, simply connect to any of our servers not included in the above list We will update this post as soon as the problem is solved. We apologize for the inconvenience not caused by us. Kind regards
  4. I thought I'd share some links I've found to check for DNS leaks: http://www.dnsleaktest.com http://ipleak.net/ If you see your real IP or another IP (other than the one that you are connected to by VPN) then you have a DNS leak. You should fix it by setting static IP and DNS server settings on your network adapter. I've written a step-by-step guide for people unfamiliar with network and IP settings. Instructions on how to make your IP settings static for Windows 7: You might be asked to elevate system priviledges or authenticate as Admin while you perform these steps, just allow it all. Click on the network icon on the taskbar (the lower right screen near the clock) -> Click on "Network and sharing center" -> Click on "Change adapter settings" on the menu to the left. You need to know your router's network settings before you continue: Right click on your network adapter (Local area connection if you're connected by a LAN cable or Wireless network connection if WiFi) and choose "Status" -> Click on "Details...". There you should notice your "IPv4 Address", "IPv4 Subnet Mask", "IPv4 Default Gateway" and "IPv4 DNS Server". Click "Close" and again "Close". Right click on your network adapter and choose "Properties" -> Click on "Internet Protocol Version 4" (don't un-check it) and click "Properties". Select the "Use the following IP address" button. IP address: When you noticed your "IPv4 Address" in the "Details" screen earler, it might have looked like this: 192.168.0.1 or 192.168.1.1. This was an IP address assigned by the DHCP pool on your router and happens automatically. You might think to put in the same IP address as you saw in the "Details" window but if you do that, the IP address might be assigned to another computer while your computer is turned off. You should choose an IP address that's much higher than your current IP address so it will be unlikely that another computer will get the same IP address from the DHCP pool. When you put in the "IP address" on the "Properties" screen, you should put in the same first three numbers (e.g. 192.168.0.) and then the last number should be a random number between 100 and 250. It doesn't really matter what number you choose, you are just choosing a number that should be unused on your local LAN. If you get an error about an "IP address conflict", you should choose another last number in the IP address. Subnet mask: Copy the "IPv4 Subnet Mask" from earlier. Default gateway: Copy the "IPv4 Default Gateway" from earlier. This is the IP address of your router. Preferred DNS server: Put in "10.4.0.1". This is AirVPN's DNS server. Alternate DNS server: Put in "10.5.0.1". AirVPN's DNS server. What you have done here is tell Windows to only use AirVPN's DNS servers instead of your routers (or ISP's) DNS servers. If you are not connected to an AirVPN server, you cannot go to the internet unless you put in your normal DNS server settings that you should have noticed in the "Details" screen before (IPv4 DNS Server above). You can also put AirVPN's website IP address in your "Hosts" file. This means that you can get to Airvpn.org to download a config without constantly changing your DNS server settings. Here's how you do it: Open notepad.exe as Admin (Right click -> Run as Administrator). Go to File -> Open. You need to navigate to this folder: "C:\Windows\System32\drivers\etc" and it might involve changing folder settings ("Organize" -> "Folder and search options") to show hidden files (View -> Show hidden files). The folder might appear to be empty but change the document type from "Text Document" to "All files" and then open the file called "hosts". Put in this lines at the bottom: 95.211.138.143 airvpn.org Then save the file as "hosts" and overwrite the old one. If you didn't run notepad.exe as Admin then you can't save the file. Hopefully this guide will help people. If there are any questions, just ask!
  5. Hi, I use the standard DNS 10.4.0.1. but it gives me troubles when in web development. The problem is that I run a certain amount of websites which I maintain. When I change DNS settings on those websites, within a few minutes I can use those settings when running on my ISP's DNS servers. When i change to the AirVPN DNS, it sometimes takes more than a day to see those changes. Is there a possibility to speed up that process? How often do you retrieve new DNS information? To be honest, it is not always like that, sometimes you do the change within the hour, but it is always slower than my ISP's one. Regards, 0fficer
  6. Well the things in THIS (https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=2353&limit=6&limitstart=6&Itemid=142) posting did not work as far as I can tell. So I did some more work and: FIRST THIS APPLIES to an OpenVPN client on a DD_WRT router NOT to the client on a PC. It is helpful to be able to telnet to the router and issue commands in this way. The notes below are done by telnet. EDIT: Please note if you use the last entry above in the firewall (iptables -I OUTPUT -o br0 ! --dst a.b.c.d -j DROP) you will lose access to the router. Thus if the tunnel goes down ...well you know. So you may want to leave this entry off the GUI and if/when you are set up properly and then run it from the telnet prompt. That way if you need router access you can reboot and be OK. First determine the router interface(s). the command is netstat -r On the far right of the output interfaces are listed. In my case I was using iptables for the tun0 interface .... the interface on the router is tun1 .. !! so the firewall commands needed to look like this: iptables -I FORWARD -i br0 -o tun1 -j ACCEPT iptables -I FORWARD -i tun1 -o br0 -j ACCEPT iptables -I INPUT -i tun1 -j REJECT iptables -t nat -A POSTROUTING -o tun1 -j MASQUERADE iptables -I OUTPUT -o br0 ! --dst a.b.c.d -j DROP # if destination for outgoing packet on eth+ is NOT a.b.c.d, drop the packet, so that nothing leaks if VPN disconnects # the above line can be duplicated for as many Air servers as you wish to connect to, just insert the appropriate Air server entry-IP Fill a.b.c.d with the remote server ip in your air.ovpn file After running these (you may want to run iptables -F first to flush previous) with YOUR interfaces determined from above, save the firewall and REBOOT. Then after reboot telnet again and run the command ps This will tell if Openvpn started .. in my case the start is unreliable. If OpenVPN is not running try this command (sleep 30 && (ps | grep openvpn | grep -v grep || openvpn --config /tmp/openvpncl/openvpn.conf --route-up /tmp/openvpncl/route-up.sh --down /tmp/openvpncl/route-down.sh --daemon))& This will check if it is running and if not will start the client. Now you can use the ps command to check and after then check your connection to AirVPN. You can also check the iptables with the command netstat -vnL. Hope this is helpful to some and saves some work/head scratching. Comments on the above very welcome, Cheers EDIT: Please note if you use the last entry above in the firewall (iptables -I OUTPUT -o br0 ! --dst a.b.c.d -j DROP) you will lose access to the router. Thus if the tunnel goes down ...well you know. So you may want to leave this entry off the GUI and if/when you are set up properly and then run it from the telnet prompt. That way if you need router access you can reboot and be OK. Also this start-up command (enter in Admin>Command window and save start-up) seems to insure the client runs .. sleep 60 (sleep 30 && (ps | grep openvpn | grep -v grep || openvpn --config /tmp/openvpncl/openvpn.conf --route-up /tmp/openvpncl/route-up.sh --down /tmp/openvpncl/route-down.sh --daemon))& It takes longer to connect but seems to do so each time correctly.
×
×
  • Create New...