You are not logged in.

#1 2019-04-12 17:14:33

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 26

[SOLVED] ExpressVPN application: Internet not working

Hello, I have had some issues connecting up to ExpressVPN even though at first everything was working well. I installed ExpressVPN application from AUR and
activated it. The thing was working for one whole day after which I started experiencing troubles after connecting up to either server/either protocol combination.

I can't seem to get any pings to any server while connected. The application doesn't work; the Firefox and Chromium plugins do not work either ( anymore ).

I've tried setting it up within NetworkManager by importing ovpn configuration files in KDE Plasma's NetworkManager app. It does indicate as connected but actually it is not.

Manual connecting reveals some problems with routing though, but I don't know how to deal with it.

~ [ sudo openvpn arch/expressvpn/Configurations/my_expressvpn_uk_-_docklands_udp.ovpn 

Fri Apr 12 18:06:29 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Fri Apr 12 18:06:29 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Fri Apr 12 18:06:29 2019 library versions: OpenSSL 1.1.1b  26 Feb 2019, LZO 2.10
Enter Auth Username: ukc8g6o6agoo1qdz7k4y13nl
Enter Auth Password: ************************
Fri Apr 12 18:06:49 2019 WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Fri Apr 12 18:06:49 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Apr 12 18:06:49 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Apr 12 18:06:49 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.217.117.38:1195
Fri Apr 12 18:06:49 2019 Socket Buffers: R=[212992->425984] S=[212992->425984]
Fri Apr 12 18:06:49 2019 UDP link local: (not bound)
Fri Apr 12 18:06:49 2019 UDP link remote: [AF_INET]185.217.117.38:1195
Fri Apr 12 18:06:49 2019 TLS: Initial packet from [AF_INET]185.217.117.38:1195, sid=05771a85 1acb3a0f
Fri Apr 12 18:06:49 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Apr 12 18:06:49 2019 VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Fri Apr 12 18:06:49 2019 VERIFY OK: nsCertType=SERVER
Fri Apr 12 18:06:49 2019 VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3112-0a, emailAddress=support@expressvpn.com
Fri Apr 12 18:06:49 2019 VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3112-0a, emailAddress=support@expressvpn.com
Fri Apr 12 18:06:49 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Apr 12 18:06:49 2019 [Server-3112-0a] Peer Connection Initiated with [AF_INET]185.217.117.38:1195
Fri Apr 12 18:06:50 2019 SENT CONTROL [Server-3112-0a]: 'PUSH_REQUEST' (status=1)
Fri Apr 12 18:06:50 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.80.0.1,comp-lzo no,route 10.80.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.80.0.10 10.80.0.9,peer-id 1,cipher AES-256-GCM'
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: timers and/or timeouts modified
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: compression parms modified
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: --ifconfig/up options modified
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: route options modified
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: peer-id set
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: adjusting link_mtu to 1629
Fri Apr 12 18:06:50 2019 OPTIONS IMPORT: data channel crypto options modified
Fri Apr 12 18:06:50 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Apr 12 18:06:50 2019 NCP: overriding user-set keysize with default
Fri Apr 12 18:06:50 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Apr 12 18:06:50 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Apr 12 18:06:50 2019 ROUTE_GATEWAY 192.168.1.254/255.255.255.0 IFACE=enp0s25 HWADDR=a0:b3:cc:29:9e:4e
Fri Apr 12 18:06:50 2019 TUN/TAP device tun0 opened
Fri Apr 12 18:06:50 2019 TUN/TAP TX queue length set to 100
Fri Apr 12 18:06:50 2019 /usr/bin/ip link set dev tun0 up mtu 1500
Fri Apr 12 18:06:50 2019 /usr/bin/ip addr add dev tun0 local 10.80.0.10 peer 10.80.0.9
Fri Apr 12 18:06:53 2019 /usr/bin/ip route add 185.217.117.38/32 via 192.168.1.254
Fri Apr 12 18:06:53 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.80.0.9
Error: Nexthop has invalid gateway.
Fri Apr 12 18:06:53 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Fri Apr 12 18:06:53 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.80.0.9
Error: Nexthop has invalid gateway.
Fri Apr 12 18:06:53 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Fri Apr 12 18:06:53 2019 /usr/bin/ip route add 10.80.0.1/32 via 10.80.0.9
Error: Nexthop has invalid gateway.
Fri Apr 12 18:06:53 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Fri Apr 12 18:06:53 2019 Initialization Sequence Completed


$ expressvpn connect   # tried different servers, tried setting protocol to either UDP or TCP

$ cat resolv.conf   # after connecting through the application:

# Generated by expressvpn
search expressvpn
nameserver 10.156.0.1

$ cat /etc/hosts

# Static table lookup for hostnames.
# See hosts(5) for details.
127.0.0.1       localhost tlilnemesis
::1             localhost

$ ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether a0:b3:cc:29:9e:4e brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 8c:70:5a:aa:04:ca brd ff:ff:ff:ff:ff:ff
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 100
    link/none 

$ ping google.com
[ BLANK ]

$ ping 10.150.0.1      # expressvpn's nameserver as per resolv.conf

$ ping 10.156.0.1
PING 10.156.0.1 (10.156.0.1) 56(84) bytes of data.
^C^C
--- 10.156.0.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 132ms


$ expressvpn disconnect

$ cat /etc/resolv.conf     # after disconnecting / normal connection to the internet

# Generated by NetworkManager
search home
nameserver 192.168.1.254
nameserver fe80::1%enp0s25


$ cat /etc/NetworkManager/NetworkManager.conf                              ] 4:08 PM

# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.

There seems to be a problem with routing/default gateway but I am really not sure how to fix it. Obviously the default route to 192.168.1.254 ( my router )
gets lost after connecting. How can I fix this - automating adding the route without needing to edit resolv.conf by hand every time I use the VPN?

Thanks a million!

Last edited by tlillenuit (2019-04-24 18:36:57)

Offline

#2 2019-04-13 12:27:43

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,307
Website

Re: [SOLVED] ExpressVPN application: Internet not working

The ExpressVPN client shouldn't touch your default gateway (at least, in my experience).

Remove all the stuff you've done with NetworkManager in regards to the ovpn config, disconnect from ExpressVPN, stop expressvpn.service, and get your networking back to the state it was in before you started using it.

Then post the outputs from the following:

$ ip link
$ ip addr
$ ip route
$ nmcli c show
$ nmcli c show <id of your active connection>

Then start expressvpn.service, run `expressvpn connect smart`, and post the output's of the above commands now, as well as the output of.

$ expressvpn diagnostics
$ expressvpn preferences
$ journalctl -u expressvpn.service --since -10m #adjust as required

Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2019-04-13 21:43:50

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 26

Re: [SOLVED] ExpressVPN application: Internet not working

I have some ( rather bad ) news in regards to the aforementioned ability of my system to connect to ExpressVPN using browser plugin, for it won't anymore. The end result after connecting up is the same as when trying to connect using the application.
I can't seem to connect to ProtonVPN, either. Hm.

I did as you suggested.

P.S. I need to add that this is my only system I can't connect to VPN on. I normally use it on my OpenBSD box and on my mobile phones.

~ [ ip link                                                                 ] 10:27 PM
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether a0:b3:cc:29:9e:4e brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 8c:70:5a:aa:04:ca brd ff:ff:ff:ff:ff:ff


~ [ ip addr                                                                 ] 10:28 PM
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether a0:b3:cc:29:9e:4e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.4/24 brd 192.168.1.255 scope global dynamic enp0s25
       valid_lft 258596sec preferred_lft 258596sec
    inet6 2001:bb6:3408:bf58:a2b3:ccff:fe29:9e4e/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6598sec preferred_lft 2998sec
    inet6 2001:bb6:3408:bf58:1c6d:58b7:912a:67f2/64 scope global dynamic noprefixroute 
       valid_lft 7091sec preferred_lft 3491sec
    inet6 fe80::aeef:d1c0:700a:ea60/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 8c:70:5a:aa:04:ca brd ff:ff:ff:ff:ff:ff


~ [ ip route                                                                ] 10:29 PM
default via 192.168.1.254 dev enp0s25 proto dhcp metric 100 
default via 192.168.1.254 dev enp0s25 proto dhcp src 192.168.1.4 metric 1024 
192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.4 
192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.4 metric 100 
192.168.1.254 dev enp0s25 proto dhcp scope link src 192.168.1.4 metric 1024

~ [ nmcli c show                                                            ] 10:45 PM
NAME                UUID                                  TYPE      DEVICE  
Wired connection 1  40921302-fd99-3ec8-8656-99f54e471ffd  ethernet  enp0s25 


~ [ nmcli c show Wired\ connection\ 1  
                                                 ] 10:33 PM
connection.id:                          Wired connection 1
connection.uuid:                        40921302-fd99-3ec8-8656-99f54e471ffd
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        -100
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   1555191065
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   100
802-3-ethernet.duplex:                  half
802-3-ethernet.auto-negotiate:          no
802-3-ethernet.mac-address:             A0:B3:CC:29:9E:4E
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist:   --
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:        --
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:            --
802-3-ethernet.wake-on-lan:             default
802-3-ethernet.wake-on-lan-password:    --
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       ""
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.dad-timeout:                       -1 (default)
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       ""
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.dhcp-duid:                         --
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.token:                             --
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --
GENERAL.NAME:                           Wired connection 1
GENERAL.UUID:                           40921302-fd99-3ec8-8656-99f54e471ffd
GENERAL.DEVICES:                        enp0s25
GENERAL.STATE:                          activated
GENERAL.DEFAULT:                        yes
GENERAL.DEFAULT6:                       yes
GENERAL.SPEC-OBJECT:                    --
GENERAL.VPN:                            no
GENERAL.DBUS-PATH:                      /org/freedesktop/NetworkManager/ActiveConnection/3
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/Settings/1
GENERAL.ZONE:                           --
GENERAL.MASTER-PATH:                    --
IP4.ADDRESS[1]:                         192.168.1.4/24
IP4.GATEWAY:                            192.168.1.254
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 192.168.1.254, mt = 100
IP4.ROUTE[2]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 0
IP4.ROUTE[3]:                           dst = 192.168.1.254/32, nh = 0.0.0.0, mt = 1024
IP4.ROUTE[4]:                           dst = 0.0.0.0/0, nh = 192.168.1.254, mt = 1024
IP4.ROUTE[5]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.DNS[1]:                             192.168.1.254
IP4.DOMAIN[1]:                          home
DHCP4.OPTION[1]:                        domain_name = home
DHCP4.OPTION[2]:                        domain_name_servers = 192.168.1.254 192.168.1.254
DHCP4.OPTION[3]:                        expiry = 1555449588
DHCP4.OPTION[4]:                        ip_address = 192.168.1.4
DHCP4.OPTION[5]:                        requested_broadcast_address = 1
DHCP4.OPTION[6]:                        requested_dhcp_server_identifier = 1
DHCP4.OPTION[7]:                        requested_domain_name = 1
DHCP4.OPTION[8]:                        requested_domain_name_servers = 1
DHCP4.OPTION[9]:                        requested_domain_search = 1
DHCP4.OPTION[10]:                       requested_host_name = 1
DHCP4.OPTION[11]:                       requested_interface_mtu = 1
DHCP4.OPTION[12]:                       requested_ms_classless_static_routes = 1
DHCP4.OPTION[13]:                       requested_nis_domain = 1
DHCP4.OPTION[14]:                       requested_nis_servers = 1
DHCP4.OPTION[15]:                       requested_ntp_servers = 1
DHCP4.OPTION[16]:                       requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[17]:                       requested_root_path = 1
DHCP4.OPTION[18]:                       requested_routers = 1
DHCP4.OPTION[19]:                       requested_static_routes = 1
DHCP4.OPTION[20]:                       requested_subnet_mask = 1
DHCP4.OPTION[21]:                       requested_time_offset = 1
DHCP4.OPTION[22]:                       requested_wpad = 1
DHCP4.OPTION[23]:                       routers = 192.168.1.254
DHCP4.OPTION[24]:                       subnet_mask = 255.255.255.0
IP6.ADDRESS[1]:                         2001:bb6:3408:bf58:1c6d:58b7:912a:67f2/64
IP6.ADDRESS[2]:                         2001:bb6:3408:bf58:a2b3:ccff:fe29:9e4e/64
IP6.ADDRESS[3]:                         fe80::aeef:d1c0:700a:ea60/64
IP6.GATEWAY:                            fe80::1
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]:                           dst = 2001:bb6:3408:bf58::/64, nh = ::, mt = 100
IP6.ROUTE[3]:                           dst = ::/0, nh = fe80::1, mt = 100
IP6.ROUTE[4]:                           dst = 2001:bb6:3408:bf58::/64, nh = ::, mt = 1024
IP6.ROUTE[5]:                           dst = ::/0, nh = fe80::1, mt = 1024
IP6.ROUTE[6]:                           dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.DNS[1]:                             fe80::1
DHCP6.OPTION[1]:                        dhcp6_name_servers = fe80::1


~ [ expressvpn connect smart                                                ] 10:37 PM
Connecting to Smart Location...
Connecting to UK - East London...       100.0%                       
Connected to UK - East London

   - To check your connection status, type 'expressvpn status'.
   - If your VPN connection unexpectedly drops, internet traffic will be blocked to protect your privacy.
   - To disable Network Lock, disconnect ExpressVPN then type 'expressvpn preferences set network_lock off'.


~ [ expressvpn diagnostics                                                  ] 10:38 PM
Client Version: 2.1.0
Client Shared Version: v1.5.2
OS Name: linux
OS Version: Arch Linux 
Internal diagnostics data:
D01: 1378, OK
D02: 1378, OK
D03: 1377
D04: 1377, OK
D05: 1377, OK
D06: 1377
D07: 1377, OK
D08: 1377, OK
D09: 1377, OK
D10: 1377, OK
D11: 1377, OK
D12: 7, 53
D13: https://www.hgm2akdl.net
D14: UK - East London
D15: auto


==============================================

Connecting to UK - East London, ip: 24.23.152.133x, protocol: udp

Sat Apr 13 22:37:56 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Sat Apr 13 22:37:56 2019 OpenVPN 2.4.7 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Feb 28 2019
Sat Apr 13 22:37:56 2019 library versions: OpenSSL 1.1.1b  26 Feb 2019, LZO 2.10
Sat Apr 13 22:37:56 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:42193
Sat Apr 13 22:37:56 2019 WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Sat Apr 13 22:37:56 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sat Apr 13 22:37:56 2019 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sat Apr 13 22:37:56 2019 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sat Apr 13 22:37:57 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:57 2019 Socket Buffers: R=[212992->425984] S=[212992->425984]
Sat Apr 13 22:37:57 2019 UDP link local: (not bound)
Sat Apr 13 22:37:57 2019 UDP link remote: [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:57 2019 TLS: Initial packet from [AF_INET]24.23.152.133:43218, sid=dec104d3 aa4c7607
Sat Apr 13 22:37:57 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Apr 13 22:37:57 2019 VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 VERIFY OK: nsCertType=SERVER
Sat Apr 13 22:37:57 2019 VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3636-0a, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3636-0a, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sat Apr 13 22:37:57 2019 [Server-3636-0a] Peer Connection Initiated with [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:58 2019 SENT CONTROL [Server-3636-0a]: 'PUSH_REQUEST' (status=1)
Sat Apr 13 22:37:58 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.142.0.1,route 10.142.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.142.0.126 10.142.0.125,peer-id 29,cipher AES-256-GCM'
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: timers and/or timeouts modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: --ifconfig/up options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: route options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: peer-id set
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: adjusting link_mtu to 1628
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: data channel crypto options modified
Sat Apr 13 22:37:58 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Sat Apr 13 22:37:58 2019 NCP: overriding user-set keysize with default
Sat Apr 13 22:37:58 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Apr 13 22:37:58 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Apr 13 22:37:58 2019 TUN/TAP device tun0 opened
Sat Apr 13 22:37:58 2019 TUN/TAP TX queue length set to 100
Sat Apr 13 22:37:58 2019 /sbin/ip link set dev tun0 up mtu 1500
Sat Apr 13 22:37:58 2019 /sbin/ip addr add dev tun0 local 10.142.0.126 peer 10.142.0.125
Sat Apr 13 22:37:58 2019 /usr/sbin/expressvpnd --update-resolv-conf tun0 1500 1556 10.142.0.126 10.142.0.125 init
dhcp-option DNS 10.142.0.1
Sat Apr 13 22:37:58 2019 /sbin/ip route add 24.23.152.133/32 via 192.168.1.254
Sat Apr 13 22:37:58 2019 /sbin/ip route add 0.0.0.0/1 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 /sbin/ip route add 128.0.0.0/1 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 /sbin/ip route add 10.142.0.1/32 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 Initialization Sequence Completed


~ [ journalctl -u expressvpn.service --since -15m                           ] 10:40 PM
-- Logs begin at Wed 2019-04-10 19:06:58 IST, end at Sat 2019-04-13 22:40:33 IST. --
Apr 13 22:37:43 tlilnemesis systemd[1]: Started ExpressVPN Daemon.


~ [ journalctl -u expressvpn.service --since -48h                           ] 10:40 PM
-- Logs begin at Wed 2019-04-10 19:06:58 IST, end at Sat 2019-04-13 22:40:42 IST. --
Apr 11 23:27:07 archlinux systemd[1]: Stopping ExpressVPN Daemon...
Apr 11 23:27:07 archlinux systemd[1]: expressvpn.service: Main process exited, code=ki>
Apr 11 23:27:07 archlinux systemd[1]: expressvpn.service: Succeeded.
Apr 11 23:27:07 archlinux systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 11 23:28:22 archlinux systemd[1]: Started ExpressVPN Daemon.
Apr 11 23:28:22 archlinux expressvpnd[515]: # Generated by expressvpn
Apr 11 23:36:38 archlinux systemd[1]: Stopping ExpressVPN Daemon...
Apr 11 23:36:38 archlinux systemd[1]: expressvpn.service: Main process exited, code=ki>
Apr 11 23:36:38 archlinux systemd[1]: expressvpn.service: Succeeded.
Apr 11 23:36:38 archlinux systemd[1]: Stopped ExpressVPN Daemon.
Apr 11 23:36:38 archlinux systemd[1]: Started ExpressVPN Daemon.
Apr 11 23:51:36 archlinux systemd[1]: Stopping ExpressVPN Daemon...
Apr 11 23:51:36 archlinux systemd[1]: expressvpn.service: Main process exited, code=ki>
Apr 11 23:51:36 archlinux systemd[1]: expressvpn.service: Succeeded.
Apr 11 23:51:36 archlinux systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 12 00:01:28 archlinux systemd[1]: Started ExpressVPN Daemon.
Apr 12 00:01:29 archlinux expressvpnd[560]: cat: /etc/resolv.conf: No such file or dir>
Apr 12 00:01:29 archlinux expressvpnd[560]: cat: /etc/resolv.conf: No such file or dir>
Apr 12 00:13:23 archlinux systemd[1]: Stopping ExpressVPN Daemon...
Apr 12 00:13:23 archlinux systemd[1]: expressvpn.service: Main process exited, code=ki>
Apr 12 00:13:23 archlinux systemd[1]: expressvpn.service: Succeeded.
Apr 12 00:13:23 archlinux systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 12 11:41:32 archlinux systemd[1]: Started ExpressVPN Daemon.
Apr 12 12:34:53 tlilnemesis systemd[1]: Stopping ExpressVPN Daemon...
Apr 12 12:34:53 tlilnemesis systemd[1]: expressvpn.service: Main process exited, code=>
~ [ journalctl -u expressvpn.service --since -24h                           ] 10:40 PM
-- Logs begin at Wed 2019-04-10 19:06:58 IST, end at Sat 2019-04-13 22:40:54 IST. --
Apr 13 00:41:48 tlilnemesis systemd[1]: Stopping ExpressVPN Daemon...
Apr 13 00:41:48 tlilnemesis systemd[1]: expressvpn.service: Main process exited, code=>
Apr 13 00:41:48 tlilnemesis systemd[1]: expressvpn.service: Succeeded.
Apr 13 00:41:48 tlilnemesis systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 13 12:37:49 tlilnemesis systemd[1]: Started ExpressVPN Daemon.
Apr 13 15:28:19 tlilnemesis systemd[1]: Stopping ExpressVPN Daemon...
Apr 13 15:28:19 tlilnemesis systemd[1]: expressvpn.service: Main process exited, code=>
Apr 13 15:28:19 tlilnemesis systemd[1]: expressvpn.service: Succeeded.
Apr 13 15:28:19 tlilnemesis systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 13 15:34:22 tlilnemesis systemd[1]: Started ExpressVPN Daemon.
Apr 13 15:34:22 tlilnemesis expressvpnd[573]: # Generated by expressvpn
Apr 13 17:28:22 tlilnemesis systemd[1]: Stopping ExpressVPN Daemon...
Apr 13 17:28:22 tlilnemesis systemd[1]: expressvpn.service: Main process exited, code=>
Apr 13 17:28:22 tlilnemesis systemd[1]: expressvpn.service: Succeeded.
Apr 13 17:28:22 tlilnemesis systemd[1]: Stopped ExpressVPN Daemon.
-- Reboot --
Apr 13 22:06:06 tlilnemesis systemd[1]: Started ExpressVPN Daemon.
Apr 13 22:22:27 tlilnemesis systemd[1]: Stopping ExpressVPN Daemon...
Apr 13 22:22:27 tlilnemesis systemd[1]: expressvpn.service: Main process exited, code=>
Apr 13 22:22:27 tlilnemesis systemd[1]: expressvpn.service: Succeeded.
Apr 13 22:22:27 tlilnemesis systemd[1]: Stopped ExpressVPN Daemon.
Apr 13 22:37:43 tlilnemesis systemd[1]: Started ExpressVPN Daemon.

Last edited by tlillenuit (2019-04-18 12:22:34)

Offline

#4 2019-04-24 18:35:14

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 26

Re: [SOLVED] ExpressVPN application: Internet not working

This issue was solved by disabling systemd-networkd and systemd-resolved services since both systemd-networkd and NetworkManager were active at the same time, causing conflict.

Last edited by tlillenuit (2019-04-24 18:36:28)

Offline

#5 2020-01-12 16:41:08

ifly_777
Member
Registered: 2020-01-05
Posts: 1

Re: [SOLVED] ExpressVPN application: Internet not working

I had the same problem and I disabled systemd-networkd but still, no luck..  kind of stuck here and support cannot figure out what's wrong.  The VPN connects but there is no internet.

Offline

#6 2020-01-12 16:50:48

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,307
Website

Re: [SOLVED] ExpressVPN application: Internet not working

Please open a new thread instead of necrobumping an old, solved one.

https://wiki.archlinux.org/index.php/Co … bumping%22

Closing.


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Board footer

Powered by FluxBB