Jump to content
Not connected, Your IP: 3.136.19.203

Recommended Posts

I'm running Arch Linux and when I connect to a server with openvpn, traffic will not go through. I've pinged airvpn.org and nothing will go through, but when I ping its IP, it will work. I've tried changing the settings on my router, and changing from UPD to TCP and ports, but still nothing will work.

 

-----openvpn log------

 

OpenVPN 2.3.14 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [iPv6] built on Dec  7 2016
library versions: OpenSSL 1.0.2j  26 Sep 2016, LZO 2.09
Control Channel Authentication: tls-auth using INLINE static key file
Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Socket Buffers: R=[212992->212992] S=[212992->212992]
UDPv4 link local: [undef]
UDPv4 link remote: [AF_INET]71.19.252.26:443
TLS: Initial packet from [AF_INET]71.19.252.26:443, sid=338868f6 e1cdcca0
VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
Validating certificate key usage
++ Certificate has key usage  00a0, expects 00a0
VERIFY KU OK
Validating certificate extended key usage
++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
VERIFY EKU OK
VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
[server] Peer Connection Initiated with [AF_INET]71.19.252.26:443
SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
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.37.76 255.255.0.0'
OPTIONS IMPORT: timers and/or timeouts modified
OPTIONS IMPORT: LZO parms modified
OPTIONS IMPORT: --ifconfig/up options modified
OPTIONS IMPORT: route options modified
OPTIONS IMPORT: route-related options modified
OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
ROUTE_GATEWAY 10.224.0.1/255.224.0.0 IFACE=wlo1 HWADDR=4c:34:88:a6:c4:30
TUN/TAP device tun0 opened
TUN/TAP TX queue length set to 100
do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
/usr/bin/ip link set dev tun0 up mtu 1500
/usr/bin/ip addr add dev tun0 10.4.37.76/16 broadcast 10.4.255.255
/usr/bin/ip route add 71.19.252.26/32 via 10.224.0.1
/usr/bin/ip route add 0.0.0.0/1 via 10.4.0.1
/usr/bin/ip route add 128.0.0.0/1 via 10.4.0.1
Initialization Sequence Completed

 

---route---

 

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.4.0.1        128.0.0.0       UG    0      0        0 tun0
0.0.0.0         10.224.0.1      0.0.0.0         UG    302    0        0 wlo1
10.4.0.0        0.0.0.0         255.255.0.0     U     0      0        0 tun0
10.224.0.0      0.0.0.0         255.224.0.0     U     302    0        0 wlo1
71.19.252.21    10.224.0.1      255.255.255.255 UGH   0      0        0 wlo1
128.0.0.0       10.4.0.1        128.0.0.0       UG    0      0        0 tun0

 

 

Share this post


Link to post

I've added 10.4.0.1 to my resolv.conf, but it didn't change anything

 

# Generated by resolvconf
nameserver 75.75.75.75
nameserver 75.75.76.76
nameserver 10.4.0.1
 

Share this post


Link to post

I've added 10.4.0.1 to my resolv.conf, but it didn't change anything

 

# Generated by resolvconf

nameserver 75.75.75.75

nameserver 75.75.76.76

nameserver 10.4.0.1

 

Try commenting these lines:

#nameserver 75.75.75.75

#nameserver 75.75.76.76

nameserver 10.4.0.1

Share this post


Link to post

Hello!

 

Have you turned off IPv6?


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

Did you also use -netlock command in the terminal?

 

First you must use your own dns servers, the change to 10.4.0.1 is only if and after you execute airvpn in the terminal and it doesn't change your nameservers. Try with opendns 208.67.222.222 208.67.220.220

If you can't connect (use netlock in the terminal too) then check your /etc/resolv.conf and if 10.4.0.1 is not there, then it's when you must change to 10.4.0.1 and delete the rest. And then inmediately try if it connects.

Share this post


Link to post

My vpn is finally working, I went over the resolv.conf page on Arch Linux wiki and it recommended to add some DNS servers in my resolv. I get great speeds, but I can only connect using TCP not UDP which is very odd, just something else to fix.

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...