Jump to content
Not connected, Your IP: 18.205.109.152
larsvontrier

ANSWERED Cannot access vpn server: 'checking route ipv6 failed'

Recommended Posts

I have installed eddie-ui and have opened it successfully.

But every time Airvpn tries to connect to a server it keeps giving the error message: 'checking route ipv6 failed'.
Unfortunately, there are no messages to help me remedy this problem.
Can someone please help?
 

Share this post


Link to post

Hello again :D

In the Logs tab there's is a red ring button which generates a support file. Click it, copy the contents and paste them here.


» I am not an AirVPN team member. All opinions are my own and are not to be considered official. Only the AirVPN Staff account should be viewed as such.

» The forums is a place where you can ask questions to the community. You are not entitled to guaranteed answer times. Answer quality may vary, too. If you need professional support, please create tickets.

» If you're new, take some time to read LZ1's New User Guide to AirVPN. On questions, use the search function first. On errors, search for the error message instead.

» If you choose to create a new thread, keep in mind that we don't know your setup. Give info about it. Never forget the OpenVPN logs or, for Eddie, the support file (Logs > lifebelt icon).

» The community kindly asks you to not set up Tor exit relays when connected to AirVPN. Their IP addresses are subject to restrictions and these are relayed to all users of the affected servers.

 

» Furthermore, I propose that your paranoia is to be destroyed. If you overdo privacy, chances are you will be unique amond the mass again.

Share this post


Link to post
Posted ... (edited)

Sorry for late reply. I could not copy and paste the log file - but I was able to save the log file to a directory.

The log file is as follows:
 

Eddie System/Environment Report - 29/10/2019 13:39 UTC

Eddie version: 2.16.3
Eddie OS build: linux_x64
Eddie architecture: x64
OS type: Linux
OS name: Debian GNU/Linux 8 \n \l
OS version: Linux debian3 3.16.0-10-amd64 #1 SMP Debian 3.16.74-1 (2019-09-24) x86_64 GNU/Linux
OS architecture: x64
Mono /.Net Framework: 3.2.8 (Debian 3.2.8+dfsg-10+deb8u1); Framework: v4.0.30319
OpenVPN driver: Found, /dev/net/tun
OpenVPN: 2.3.4 - OpenSSL 1.0.1t  3 May 2016, LZO 2.08 (/usr/sbin/openvpn)
SSH: OpenSSH_6.7p1 Debian-5+deb8u8, OpenSSL 1.0.1t  3 May 2016 (/usr/bin/ssh)
SSL: stunnel 5.06 (/usr/bin/stunnel4)
curl: 7.38.0 (/usr/bin/curl)
Profile path: /home/ricardo/.airvpn/default.xml
Data path: /home/ricardo/.airvpn
Application path: /usr/lib/eddie-ui
Executable path: /usr/lib/eddie-ui/Eddie-UI.exe
Command line arguments: (5 args) path="/home/ricardo/.airvpn" path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui" console.mode="none" linux.dbus="unix:abstract=/tmp/dbus-uhecKhDz9D,guid=50f68bbe1defade93d6158175db80ec3"
Network Lock Active: No
Connected to VPN: No
Detected DNS: 192.168.1.1
Test DNS IPv4: Ok
Test DNS IPv6: Ok
Test Ping IPv4: 21 ms
Test Ping IPv6: -1 ms
Test HTTP IPv4: Ok
Test HTTP IPv6: Error:curl: (7) Couldn't connect to server
Test HTTPS: Ok
----------------------------
Important options not at defaults:

login: (omissis)
password: (omissis)
servers.whitelist: fea70eb2867e7ec9dc65155db4b171d9706a2b09880f5c62ad2a5fbb308cef64

----------------------------
Logs:

. 2019.10.29 13:37:15 - Eddie version: 2.16.3 / linux_x64, System: Linux, Name: Debian GNU/Linux 8 \n \l, Version: Linux debian3 3.16.0-10-amd64 #1 SMP Debian 3.16.74-1 (2019-09-24) x86_64 GNU/Linux, Mono/.Net: 3.2.8 (Debian 3.2.8+dfsg-10+deb8u1); Framework: v4.0.30319
. 2019.10.29 13:37:15 - Reading options from /home/ricardo/.airvpn/default.xml
. 2019.10.29 13:37:16 - Command line arguments (5): path="/home/ricardo/.airvpn" path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui" console.mode="none" linux.dbus="unix:abstract=/tmp/dbus-uhecKhDz9D,guid=50f68bbe1defade93d6158175db80ec3"
. 2019.10.29 13:37:16 - Profile path: /home/ricardo/.airvpn/default.xml
. 2019.10.29 13:37:18 - OpenVPN Driver - Found, /dev/net/tun
. 2019.10.29 13:37:18 - OpenVPN - Version: 2.3.4 - OpenSSL 1.0.1t  3 May 2016, LZO 2.08 (/usr/sbin/openvpn)
. 2019.10.29 13:37:18 - SSH - Version: OpenSSH_6.7p1 Debian-5+deb8u8, OpenSSL 1.0.1t  3 May 2016 (/usr/bin/ssh)
. 2019.10.29 13:37:18 - SSL - Version: stunnel 5.06 (/usr/bin/stunnel4)
. 2019.10.29 13:37:18 - curl - Version: 7.38.0 (/usr/bin/curl)
. 2019.10.29 13:37:18 - Certification Authorities: /usr/share/eddie-ui/cacert.pem
. 2019.10.29 13:37:18 - Updating systems & servers data ...
I 2019.10.29 13:37:18 - Ready
. 2019.10.29 13:37:18 - Systems & servers data update completed
I 2019.10.29 13:38:13 - Checking login ...
! 2019.10.29 13:38:14 - Logged in.
I 2019.10.29 13:38:26 - Session starting.
I 2019.10.29 13:38:26 - Checking authorization ...
! 2019.10.29 13:38:27 - Connecting to Gorgonea (Canada, Toronto, Ontario)
. 2019.10.29 13:38:27 - OpenVPN > OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 26 2017
. 2019.10.29 13:38:27 - OpenVPN > library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.08
. 2019.10.29 13:38:27 - Connection to OpenVPN Management Interface
. 2019.10.29 13:38:27 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2019.10.29 13:38:27 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2019.10.29 13:38:27 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:27 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:27 - OpenVPN > Socket Buffers: R=[212992->131072] S=[212992->131072]
. 2019.10.29 13:38:27 - OpenVPN > UDPv4 link local: [undef]
. 2019.10.29 13:38:27 - OpenVPN > UDPv4 link remote: [AF_INET]104.254.90.250:443
. 2019.10.29 13:38:27 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2019.10.29 13:38:27 - OpenVPN > TLS: Initial packet from [AF_INET]104.254.90.250:443, sid=a8be2914 ff38b52f
. 2019.10.29 13:38:27 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2019.10.29 13:38:27 - OpenVPN > Validating certificate key usage
. 2019.10.29 13:38:27 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2019.10.29 13:38:27 - OpenVPN > VERIFY KU OK
. 2019.10.29 13:38:27 - OpenVPN > Validating certificate extended key usage
. 2019.10.29 13:38:27 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2019.10.29 13:38:27 - OpenVPN > VERIFY EKU OK
. 2019.10.29 13:38:27 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2019.10.29 13:38:28 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2019.10.29 13:38:28 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:28 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2019.10.29 13:38:28 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:28 - OpenVPN > Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
. 2019.10.29 13:38:28 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]104.254.90.250:443
. 2019.10.29 13:38:30 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2019.10.29 13:38:30 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway  def1 bypass-dhcp,dhcp-option DNS 10.18.24.1,route-gateway 10.18.24.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.18.24.40 255.255.255.0'
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: route options modified
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2019.10.29 13:38:30 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2019.10.29 13:38:30 - OpenVPN > ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=eth0 HWADDR=1c:6f:65:80:a9:fb
. 2019.10.29 13:38:31 - OpenVPN > TUN/TAP device tun0 opened
. 2019.10.29 13:38:31 - OpenVPN > TUN/TAP TX queue length set to 100
. 2019.10.29 13:38:31 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2019.10.29 13:38:31 - OpenVPN > /sbin/ip link set dev tun0 up mtu 1500
. 2019.10.29 13:38:31 - OpenVPN > /sbin/ip addr add dev tun0 10.18.24.40/24 broadcast 10.18.24.255
. 2019.10.29 13:38:36 - OpenVPN > /sbin/ip route add 104.254.90.250/32 via 192.168.1.1
. 2019.10.29 13:38:36 - OpenVPN > /sbin/ip route add 0.0.0.0/1 via 10.18.24.1
. 2019.10.29 13:38:36 - OpenVPN > /sbin/ip route add 128.0.0.0/1 via 10.18.24.1
. 2019.10.29 13:38:36 - /etc/resolv.conf moved to /etc/resolv.conf.eddie as backup
. 2019.10.29 13:38:36 - DNS of the system updated to VPN DNS (Rename method: /etc/resolv.conf generated)
. 2019.10.29 13:38:36 - Routes, added a new route, 104.254.90.251 for gateway 10.18.24.1
. 2019.10.29 13:38:36 - Unable to compute route for 2606:6080:2001:a:9374:410c:ca5:d631: IPv6 VPN gateway not available.
. 2019.10.29 13:38:36 - Flushing DNS
I 2019.10.29 13:38:38 - Checking route IPv4
I 2019.10.29 13:38:38 - Checking route IPv6
. 2019.10.29 13:38:38 - curl: (7) Couldn't connect to server
. 2019.10.29 13:38:38 - Checking route (2° try)
. 2019.10.29 13:38:39 - curl: (7) Couldn't connect to server
. 2019.10.29 13:38:39 - Checking route (3° try)
. 2019.10.29 13:38:41 - curl: (7) Couldn't connect to server
E 2019.10.29 13:38:41 - Checking route IPv6 failed.
. 2019.10.29 13:38:41 - OpenVPN > Initialization Sequence Completed
! 2019.10.29 13:38:41 - Disconnecting
. 2019.10.29 13:38:41 - Routes, removed a route previously added, 104.254.90.251 for gateway 10.18.24.1
. 2019.10.29 13:38:41 - Sending management termination signal
. 2019.10.29 13:38:41 - Management - Send 'signal SIGTERM'
. 2019.10.29 13:38:41 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2019.10.29 13:38:41 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2019.10.29 13:38:41 - OpenVpn Management > SUCCESS: signal SIGTERM thrown
. 2019.10.29 13:38:46 - OpenVPN > /sbin/ip route del 104.254.90.250/32
. 2019.10.29 13:38:46 - OpenVPN > /sbin/ip route del 0.0.0.0/1
. 2019.10.29 13:38:46 - OpenVPN > /sbin/ip route del 128.0.0.0/1
. 2019.10.29 13:38:46 - OpenVPN > Closing TUN/TAP interface
. 2019.10.29 13:38:46 - OpenVPN > /sbin/ip addr del dev tun0 10.18.24.40/24
. 2019.10.29 13:38:46 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2019.10.29 13:38:46 - Connection terminated.
. 2019.10.29 13:38:46 - DNS of the system restored to original settings (Rename method)
I 2019.10.29 13:38:49 - Checking authorization ...
! 2019.10.29 13:38:49 - Connecting to Gorgonea (Canada, Toronto, Ontario)
. 2019.10.29 13:38:49 - OpenVPN > OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 26 2017
. 2019.10.29 13:38:49 - OpenVPN > library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.08
. 2019.10.29 13:38:49 - Connection to OpenVPN Management Interface
. 2019.10.29 13:38:49 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2019.10.29 13:38:49 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2019.10.29 13:38:49 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:49 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:49 - OpenVPN > Socket Buffers: R=[212992->131072] S=[212992->131072]
. 2019.10.29 13:38:49 - OpenVPN > UDPv4 link local: [undef]
. 2019.10.29 13:38:49 - OpenVPN > UDPv4 link remote: [AF_INET]104.254.90.250:443
. 2019.10.29 13:38:49 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2019.10.29 13:38:49 - OpenVPN > TLS: Initial packet from [AF_INET]104.254.90.250:443, sid=41be2df2 ccf6d9d5
. 2019.10.29 13:38:49 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2019.10.29 13:38:49 - OpenVPN > Validating certificate key usage
. 2019.10.29 13:38:49 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2019.10.29 13:38:49 - OpenVPN > VERIFY KU OK
. 2019.10.29 13:38:49 - OpenVPN > Validating certificate extended key usage
. 2019.10.29 13:38:49 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2019.10.29 13:38:49 - OpenVPN > VERIFY EKU OK
. 2019.10.29 13:38:49 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2019.10.29 13:38:50 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2019.10.29 13:38:50 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:50 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2019.10.29 13:38:50 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2019.10.29 13:38:50 - OpenVPN > Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
. 2019.10.29 13:38:50 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]104.254.90.250:443
. 2019.10.29 13:38:53 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2019.10.29 13:38:53 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway  def1 bypass-dhcp,dhcp-option DNS 10.18.24.1,route-gateway 10.18.24.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.18.24.40 255.255.255.0'
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: route options modified
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2019.10.29 13:38:53 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2019.10.29 13:38:53 - OpenVPN > ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=eth0 HWADDR=1c:6f:65:80:a9:fb
. 2019.10.29 13:38:53 - OpenVPN > TUN/TAP device tun0 opened
. 2019.10.29 13:38:53 - OpenVPN > TUN/TAP TX queue length set to 100
. 2019.10.29 13:38:53 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2019.10.29 13:38:53 - OpenVPN > /sbin/ip link set dev tun0 up mtu 1500
. 2019.10.29 13:38:53 - OpenVPN > /sbin/ip addr add dev tun0 10.18.24.40/24 broadcast 10.18.24.255
. 2019.10.29 13:38:58 - OpenVPN > /sbin/ip route add 104.254.90.250/32 via 192.168.1.1
. 2019.10.29 13:38:58 - OpenVPN > /sbin/ip route add 0.0.0.0/1 via 10.18.24.1
. 2019.10.29 13:38:58 - OpenVPN > /sbin/ip route add 128.0.0.0/1 via 10.18.24.1
. 2019.10.29 13:38:58 - /etc/resolv.conf moved to /etc/resolv.conf.eddie as backup
. 2019.10.29 13:38:58 - DNS of the system updated to VPN DNS (Rename method: /etc/resolv.conf generated)
. 2019.10.29 13:38:58 - Routes, added a new route, 104.254.90.251 for gateway 10.18.24.1
. 2019.10.29 13:38:58 - Unable to compute route for 2606:6080:2001:a:9374:410c:ca5:d631: IPv6 VPN gateway not available.
. 2019.10.29 13:38:58 - Flushing DNS
I 2019.10.29 13:39:00 - Checking route IPv4
I 2019.10.29 13:39:00 - Checking route IPv6
. 2019.10.29 13:39:00 - curl: (7) Couldn't connect to server
. 2019.10.29 13:39:00 - Checking route (2° try)
. 2019.10.29 13:39:01 - curl: (7) Couldn't connect to server
. 2019.10.29 13:39:01 - Checking route (3° try)
. 2019.10.29 13:39:03 - curl: (7) Couldn't connect to server
E 2019.10.29 13:39:03 - Checking route IPv6 failed.
. 2019.10.29 13:39:03 - OpenVPN > Initialization Sequence Completed
! 2019.10.29 13:39:03 - Disconnecting
. 2019.10.29 13:39:03 - Routes, removed a route previously added, 104.254.90.251 for gateway 10.18.24.1
. 2019.10.29 13:39:03 - Sending management termination signal
. 2019.10.29 13:39:03 - Management - Send 'signal SIGTERM'
. 2019.10.29 13:39:03 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2019.10.29 13:39:03 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2019.10.29 13:39:08 - OpenVPN > /sbin/ip route del 104.254.90.250/32
. 2019.10.29 13:39:08 - OpenVPN > /sbin/ip route del 0.0.0.0/1
. 2019.10.29 13:39:08 - OpenVPN > /sbin/ip route del 128.0.0.0/1
. 2019.10.29 13:39:08 - OpenVPN > Closing TUN/TAP interface
. 2019.10.29 13:39:08 - OpenVPN > /sbin/ip addr del dev tun0 10.18.24.40/24
. 2019.10.29 13:39:08 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2019.10.29 13:39:08 - Connection terminated.
. 2019.10.29 13:39:08 - DNS of the system restored to original settings (Rename method)
I 2019.10.29 13:39:10 - Cancel requested.
! 2019.10.29 13:39:10 - Session terminated.

----------------------------
Network Interfaces and Routes:

{
    "support_ipv4": true,
    "support_ipv6": true,
    "routes": [
        {
            "address": "0.0.0.0\/0",
            "gateway": "192.168.1.1",
            "interface": "eth0",
            "metric": "1024"
        }
    ],
    "interfaces": [
        {
            "friendly": "lo",
            "id": "lo",
            "name": "lo",
            "description": "lo",
            "type": "Loopback",
            "status": "Unknown",
            "bytes_received": "65982",
            "bytes_sent": "65982",
            "support_ipv4": true,
            "support_ipv6": true,
            "ips": [
                "127.0.0.1",
                "::0.0.0.1"
            ],
            "gateways": [],
            "bind": true
        },
        {
            "friendly": "eth0",
            "id": "eth0",
            "name": "eth0",
            "description": "eth0",
            "type": "Ethernet",
            "status": "Up",
            "bytes_received": "2024724835",
            "bytes_sent": "48979705",
            "support_ipv4": true,
            "support_ipv6": true,
            "ips": [
                "192.168.1.98",
                "fe80::1e6f:65ff:fe80:a9fb"
            ],
            "gateways": [
                "192.168.1.1"
            ],
            "bind": true
        }
    ],
    "ipv4-default-gateway": "192.168.1.1",
    "ipv4-default-interface": "eth0"
}
----------------------------
UID: 0
Run as normal user: True; ID:1000; Name:yayoi
----------------------------
ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 1c:6f:65:80:a9:fb brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.98/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 159864sec preferred_lft 159864sec
    inet6 fe80::1e6f:65ff:fe80:a9fb/64 scope link
       valid_lft forever preferred_lft forever
----------------------------
ip link show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 1c:6f:65:80:a9:fb brd ff:ff:ff:ff:ff:ff
----------------------------
ip -4 route show:

default via 192.168.1.1 dev eth0  proto static  metric 1024
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.98
----------------------------
ip -6 route show: fe80::/64 dev eth0  proto kernel  metric 256root@debian3:~#


Can you please advise what is wrong?

It has been several days and I am not able to use the vpn service. Edited ... by giganerd
Formatting of paste from Code -> Log

Share this post


Link to post

I have sent a reply on this thread over 24 hours ago.
However the post has not yet been 'approved by a moderator'.

I have PAID money for a service.
But I am not getting that service.
I am a little frustrated that there isn't a speedy reply.
However, they do say 'patience is a virtue'.
 

Share this post


Link to post
Posted ... (edited)
On 10/30/2019 at 5:53 PM, Ricardo Gomez said:

I have sent a reply on this thread over 24 hours ago.
However the post has not yet been 'approved by a moderator'.


When I was about to become moderator, I pledged to review the approval queue more often so that no one shall wait more than 24 hours for their posts to get looked upon. But I and all the moderators here are only humans who have only these 24 hours to get anything done in our lives. You must apologize our tendency to prioritize, and work/sleep for example are definitely more important than a forum. We are volunteers who pledge our precious time, a resource you never get back once spent, to helping ladies, or gentlemen, whichever you are, with their issues. It's one of the redeeming qualities of AirVPN: The community is helping the community.
 
On 10/30/2019 at 5:53 PM, Ricardo Gomez said:

I have PAID money for a service.
But I am not getting that service.


Did you open a support ticket with your problem?
The forums are a courtesy of Air to let the community communicate and often contemplate about and solve problems. You don't buy guaranteed reply times on the forums with your subscription, anyone can register and start posting here, which makes them all volunteers. So I'd advise patience.
 

Now, to your problem. It seems your system has IPv6 enabled, but your network doesn't have IPv6 connectivity. Eddie still tries to apply IPv6 routes but fails to do so.
I'd say, in Eddie preferences > Networking, set IPv6 to Block. Edited ... by giganerd

» I am not an AirVPN team member. All opinions are my own and are not to be considered official. Only the AirVPN Staff account should be viewed as such.

» The forums is a place where you can ask questions to the community. You are not entitled to guaranteed answer times. Answer quality may vary, too. If you need professional support, please create tickets.

» If you're new, take some time to read LZ1's New User Guide to AirVPN. On questions, use the search function first. On errors, search for the error message instead.

» If you choose to create a new thread, keep in mind that we don't know your setup. Give info about it. Never forget the OpenVPN logs or, for Eddie, the support file (Logs > lifebelt icon).

» The community kindly asks you to not set up Tor exit relays when connected to AirVPN. Their IP addresses are subject to restrictions and these are relayed to all users of the affected servers.

 

» Furthermore, I propose that your paranoia is to be destroyed. If you overdo privacy, chances are you will be unique amond the mass again.

Share this post


Link to post
On 11/1/2019 at 12:26 AM, giganerd said:

When I was about to become moderator, I pledged to review the approval queue more often so that no one shall wait more than 24 hours for their posts to get looked upon. But I and all the moderators here are only humans who have only these 24 hours to get anything done in our lives. You must apologize our tendency to prioritize, and work/sleep for example are definitely more important than a forum. We are volunteers who pledge our precious time, a resource you never get back once spent, to helping ladies, or gentlemen, whichever you are, with their issues. It's one of the redeeming qualities of AirVPN: The community is helping the community.
 
Did you open a support ticket with your problem?
The forums are a courtesy of Air to let the community communicate and often contemplate about and solve problems. You don't buy guaranteed reply times on the forums with your subscription, anyone can register and start posting here, which makes them all volunteers. So I'd advise patience.
 
I was about to edit this out, to be honest, because we're not having this kind of tone around here. It's not fair towards the rest of the community, and the sincerest comment is only sincere from the commenter's own perspective and may not be true in its core.

Now, to your problem. It seems your system has IPv6 enabled, but your network doesn't have IPv6 connectivity. Eddie still tries to apply IPv6 routes but fails to do so.
I'd say, in Eddie preferences > Networking, set IPv6 to Block.

When eddie-ui opened up, I selected the 'Settings' icon - this brought up the 'Settings Menu'.
On the Settings Menu, there is a 'Layer IPv6' option. On the drop-down tab next to it, I selected 'Blocked'.
After that, I was able to access the Airvpn service.

Thank you very much for your kind help.
I was a little worried things wouldn't work out - but I'm very happy to report I now have a properly running Airvpn service.
This would not be possible without your contribution.
Thank you so much! I am eternally grateful :)

 

Share this post


Link to post
Guest
This topic is now closed to further replies.

×
×
  • Create New...