Jump to content
Not connected, Your IP: 3.135.209.20
butter122383

Can not access the web after connecting through vpn

Recommended Posts

first off thanks for your time for trying to help with this issue.

 

long story short I use debian linux to conntect through open vpn

 

I go and disable IPv6,

 

I try to connect to the vpn via command line.

 

But when I do this I cant do anything on the web, or use ping or nothing.

 

when i connect using the terminal i due the ifconfig and see the tunnel is active.

 

it only when i quit the connecting is when everything return to normal ( web, ping, ect).

 

any ideals on this one cause i been trying to figure this one out for couple of days and i cant find the answer.

 

 

Share this post


Link to post

Hello!

 

Have you tried using the portable version of the AirVPN client?

 

Sent to you from me with datalove


Moderators do not speak on behalf of AirVPN. Only the Official Staff account does. Please also do not run Tor Exit Servers behind AirVPN, thank you.
Did you make a guide or how-to for something? Then contact me to get it listed in my new user guide's Guides Section, so that the community can find it more easily.

Share this post


Link to post

This might be a DNS issue.

What is the content of your /etc/resolv.conf file?

 

Attach your client logs, they should indicate if something went wrong.

 

this is my resolv.conf

 

# Generated by NetworkManager

search hsd1.de.comcast.net

nameserver 75.75.75.75

nameserver 75.75.76.76

nameserver 2001:558:feed::1

# NOTE: the libc resolver may not support more than 3 nameservers.

# The nameservers listed below may not be recognized.

nameserver 2001:558:feed::2

 

 

this is the sequence that happen when i log in through vpn

 

Thu Aug 18 23:22:43 2016 OpenVPN 2.3.11 i686-pc-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [iPv6] built on May 23 2016

Thu Aug 18 23:22:43 2016 library versions: OpenSSL 1.0.2h  3 May 2016, LZO 2.08

Thu Aug 18 23:22:43 2016 Control Channel Authentication: tls-auth using INLINE static key file

Thu Aug 18 23:22:43 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

Thu Aug 18 23:22:43 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

Thu Aug 18 23:22:43 2016 Socket Buffers: R=[163840->163840] S=[163840->163840]

Thu Aug 18 23:22:43 2016 UDPv4 link local: [undef]

Thu Aug 18 23:22:43 2016 UDPv4 link remote: [AF_INET]62.102.148.135:443

Thu Aug 18 23:22:43 2016 TLS: Initial packet from [AF_INET]62.102.148.135:443, sid=a2822b04 ad90129f

Thu Aug 18 23:22:43 2016 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org

Thu Aug 18 23:22:43 2016 Validating certificate key usage

Thu Aug 18 23:22:43 2016 ++ Certificate has key usage  00a0, expects 00a0

Thu Aug 18 23:22:43 2016 VERIFY KU OK

Thu Aug 18 23:22:43 2016 Validating certificate extended key usage

Thu Aug 18 23:22:43 2016 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication

Thu Aug 18 23:22:43 2016 VERIFY EKU OK

Thu Aug 18 23:22:43 2016 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org

Thu Aug 18 23:22:47 2016 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

Thu Aug 18 23:22:47 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

Thu Aug 18 23:22:47 2016 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

Thu Aug 18 23:22:47 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

Thu Aug 18 23:22:47 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA

Thu Aug 18 23:22:47 2016 [server] Peer Connection Initiated with [AF_INET]62.102.148.135:443

Thu Aug 18 23:22:49 2016 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)

Thu Aug 18 23:22:49 2016 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.4.0.1,comp-lzo no,route-gateway 10.4.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.4.58.235 255.255.0.0'

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: timers and/or timeouts modified

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: LZO parms modified

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: --ifconfig/up options modified

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: route options modified

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: route-related options modified

Thu Aug 18 23:22:49 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

Thu Aug 18 23:22:49 2016 ROUTE_GATEWAY 10.0.0.1/255.255.255.0 IFACE=wlan0 HWADDR=00:26:c7:7b:4f:ca

Thu Aug 18 23:22:49 2016 TUN/TAP device tun0 opened

Thu Aug 18 23:22:49 2016 TUN/TAP TX queue length set to 100

Thu Aug 18 23:22:49 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0

Thu Aug 18 23:22:49 2016 /sbin/ip link set dev tun0 up mtu 1500

Thu Aug 18 23:22:49 2016 /sbin/ip addr add dev tun0 10.4.58.235/16 broadcast 10.4.255.255

Thu Aug 18 23:22:54 2016 /sbin/ip route add 62.102.148.135/32 via 10.0.0.1

Thu Aug 18 23:22:54 2016 /sbin/ip route add 0.0.0.0/1 via 10.4.0.1

Thu Aug 18 23:22:54 2016 /sbin/ip route add 128.0.0.0/1 via 10.4.0.1

Thu Aug 18 23:22:54 2016 Initialization Sequence Completed

Share this post


Link to post

Those are your ISP DNS servers which are not accessible for queries outside of the ISP IP pools.

Try changing it to 10.4.0.1 after you connect and check again.

 Ok this work, but when i reboot the dns changes back.  Is there away to keep this on or do i have to input this everytime i turn on the computer?

Share this post


Link to post

 

Those are your ISP DNS servers which are not accessible for queries outside of the ISP IP pools.

Try changing it to 10.4.0.1 after you connect and check again.

 Ok this work, but when i reboot the dns changes back.  Is there away to keep this on or do i have to input this everytime i turn on the computer?

 

Hello!

 

Try to take care of DNS push. The following method is perfect if your distribution can run resolvconf:

 

https://airvpn.org/topic/9608-how-to-accept-dns-push-on-linux-systems-with-resolvconf/

 

If your system is "based" on systemd instead of initd, you could experience problems even with resolvconf and the OpeNVPN script, unfortunately. In this case please see here;

https://wiki.archlinux.org/index.php/OpenVPN#DNS

 

As an alternative to all of the above, try our free and open source client Eddie for GNU/Linux. It brutally takes total control of /etc/resolv.conf to try to accept DNS push under any Linux system. Test Eddie 2.11.3 beta. Eddie 2.11.4 beta will have some addition to DNS handling to cover some more special cases.

 

Kind regards

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...