Connecting to NordVPN via networkmanager

Connecting to NordVPN via networkmanager

Postby madcowsonthewall » Nov 13th, '17, 22:51

I've followed the instructions to use networkmanager to try to connect to openvpn,

viewtopic.php?f=25&t=5782

I can connect now via networkmanager to wifi-networks without any problems. Whenever I try to connect to Nordvpn, I end up without network connection.
I've followed the instructions provided here: https://nordvpn.com/nl/tutorials/linux/openvpn/

Output of
Code: Select all
systemctl status networkmanager.service -al -n150

Gives
Code: Select all
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-11-13 21:07:09 CET; 34min ago
     Docs: man:NetworkManager(8)
 Main PID: 883 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─ 883 /usr/sbin/NetworkManager --no-daemon
           ├─6259 /usr/libexec/nm-openvpn-service --bus-name org.freedesktop.NetworkManager.openvpn.Connection_2
           └─6295 /usr/sbin/openvpn --remote 185.210.217.140 443 tcp-client --remote-random --comp-lzo adaptive --ping 15 --ping-restart 0 --nobind --dev tun --cipher AES-256-CBC --auth SHA512 --auth-nocache --t

Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3554] dns-mgr[0x19e5970]: init: dns=default, rc-manager=resolvconf
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3565] rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/ieee80211/phy0/rfkill3) (driver ath
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3566] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3641] manager[0x19dd0c0]: WiFi hardware radio set enabled
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3641] manager[0x19dd0c0]: WWAN hardware radio set enabled
Nov 13 21:07:09 localhost.localdomain systemd[1]: Started Network Manager.
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3851] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list. (/
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3860] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list. (/usr/lib64/N
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3861] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3882] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-Kodak_7 (a879ed84-13f1-4019-9999-47d9f2048b50,"Kodak_7")
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3897] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-Windows_Phone3079 (5cf91ba3-800f-4422-9fd2-d5c0c52859e0,"Windows
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3913] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-Surfers_Paradise5 (804b4b64-195b-4910-b32f-3efed278d21f,"Surfers
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3922] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp1s0 (c0ab6b8c-0eac-a1b4-1c47-efe4b2d1191f,"System enp1s0")
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.3931] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-wlp2s0 (389004d4-f715-511d-a960-6b5f8fac4690,"System CNTCRB1721
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4160] keyfile: new connection /etc/NetworkManager/system-connections/us1023.nordvpn.com.udp (7c1b44e2-94b7-49f7-9c68-c56e6ebb7159,"u
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4338] keyfile: new connection /etc/NetworkManager/system-connections/be24.nordvpn.com.tcp (5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be2
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4356] settings: hostname: using hostnamed
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4357] settings: hostname changed from (none) to "localhost.localdomain"
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4358] dhcp-init: Using DHCP client 'internal'
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4358] manager: WiFi enabled by radio killswitch; enabled by state file
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4359] manager: WWAN enabled by radio killswitch; enabled by state file
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4359] manager: Networking is enabled by state file
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMBondDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMBridgeDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMDummyDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMEthernetDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4369] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4370] Loaded device plugin: NMMacsecDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4370] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4375] Loaded device plugin: NMTunDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4375] Loaded device plugin: NMVethDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4375] Loaded device plugin: NMVlanDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4375] Loaded device plugin: NMVxlanDeviceFactory (internal)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4396] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4408] device (lo): link connected
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4416] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4430] manager: (enp1s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4442] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4686] wifi-nl80211: (wlp2s0): using nl80211 for WiFi device control
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4689] device (wlp2s0): driver supports Access Point (AP) mode
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4697] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4708] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4686] wifi-nl80211: (wlp2s0): using nl80211 for WiFi device control
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4689] device (wlp2s0): driver supports Access Point (AP) mode
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4697] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Nov 13 21:07:09 localhost.localdomain NetworkManager[883]: <info>  [1510603629.4708] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 13 21:07:11 localhost.localdomain NetworkManager[883]: <info>  [1510603631.4313] device (wlp2s0): set-hw-addr: set MAC address to 62:06:F6:86:56:EC (scanning)
Nov 13 21:07:13 localhost.localdomain NetworkManager[883]: <info>  [1510603633.4424] supplicant: wpa_supplicant running
Nov 13 21:07:13 localhost.localdomain NetworkManager[883]: <info>  [1510603633.4425] device (wlp2s0): supplicant interface state: init -> starting
Nov 13 21:07:13 localhost.localdomain NetworkManager[883]: <info>  [1510603633.4727] sup-iface[0x1a85290,wlp2s0]: supports 5 scan SSIDs
Nov 13 21:07:13 localhost.localdomain NetworkManager[883]: <info>  [1510603633.4734] device (wlp2s0): supplicant interface state: starting -> ready
Nov 13 21:07:13 localhost.localdomain NetworkManager[883]: <info>  [1510603633.4735] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 13 21:07:17 localhost.localdomain NetworkManager[883]: <info>  [1510603637.2307] device (wlp2s0): supplicant interface state: ready -> inactive
Nov 13 21:07:17 localhost.localdomain NetworkManager[883]: <info>  [1510603637.2357] manager: startup complete
Nov 13 21:07:17 localhost.localdomain NetworkManager[883]: <info>  [1510603637.7053] audit: op="connection-activate" uuid="c0ab6b8c-0eac-a1b4-1c47-efe4b2d1191f" name="System enp1s0" result="fail" reason="No suit
Nov 13 21:07:17 localhost.localdomain NetworkManager[883]: <info>  [1510603637.7704] ifcfg-rh: update /etc/sysconfig/network-scripts/ifcfg-wlp2s0 (389004d4-f715-511d-a960-6b5f8fac4690,"System CNTCRB1721 (wlp2s0)
Nov 13 21:07:17 localhost.localdomain NetworkManager[883]: <info>  [1510603637.8176] audit: op="connection-activate" uuid="389004d4-f715-511d-a960-6b5f8fac4690" name="System CNTCRB1721 (wlp2s0)" result="fail" re
Nov 13 21:07:39 localhost.localdomain NetworkManager[883]: <info>  [1510603659.0446] policy: auto-activating connection 'Surfers_Paradise5'
Nov 13 21:07:39 localhost.localdomain NetworkManager[883]: <info>  [1510603659.0462] device (wlp2s0): Activation: starting connection 'Surfers_Paradise5' (804b4b64-195b-4910-b32f-3efed278d21f)
Nov 13 21:07:39 localhost.localdomain NetworkManager[883]: <info>  [1510603659.0464] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 13 21:07:39 localhost.localdomain NetworkManager[883]: <info>  [1510603659.0467] manager: NetworkManager state is now CONNECTING
Nov 13 21:07:39 localhost.localdomain NetworkManager[883]: <info>  [1510603659.0519] device (wlp2s0): set-hw-addr: reset MAC address to CC:B0:DA:AB:CF:4B (preserve)
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0130] device (wlp2s0): supplicant interface state: inactive -> disabled
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0140] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0142] device (wlp2s0): Activation: (wifi) access point 'Surfers_Paradise5' has security, but secrets are required.
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0142] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0]
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0190] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0194] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0196] device (wlp2s0): Activation: (wifi) connection 'Surfers_Paradise5' has security, and secrets exist.  No new secrets needed.
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0196] Config: added 'ssid' value 'Surfers_Paradise5'
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0196] Config: added 'scan_ssid' value '1'
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0197] Config: added 'key_mgmt' value 'WPA-PSK'
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0197] Config: added 'auth_alg' value 'OPEN'
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0197] Config: added 'psk' value '<hidden>'
Nov 13 21:07:41 localhost.localdomain NetworkManager[883]: <info>  [1510603661.0252] device (wlp2s0): supplicant interface state: disabled -> scanning
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.6986] device (wlp2s0): supplicant interface state: scanning -> authenticating
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7104] device (wlp2s0): supplicant interface state: authenticating -> associating
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7173] device (wlp2s0): supplicant interface state: associating -> associated
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7233] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7431] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7431] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Surfers_Paradi
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7432] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Nov 13 21:07:44 localhost.localdomain NetworkManager[883]: <info>  [1510603664.7437] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4600] dhcp4 (wlp2s0):   address 192.168.1.7
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4600] dhcp4 (wlp2s0):   plen 24
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4600] dhcp4 (wlp2s0):   expires in 86400 seconds
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4601] dhcp4 (wlp2s0):   nameserver '192.168.1.1'
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4601] dhcp4 (wlp2s0):   gateway 192.168.1.1
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4603] dhcp4 (wlp2s0): state changed unknown -> bound
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4618] device (wlp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4623] device (wlp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4626] device (wlp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4628] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4808] manager: NetworkManager state is now CONNECTED_SITE
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4809] policy: set 'Surfers_Paradise5' (wlp2s0) as default for IPv4 routing and DNS
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.4812] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.5611] device (wlp2s0): Activation: successful, device activated.
Nov 13 21:07:46 localhost.localdomain NetworkManager[883]: <info>  [1510603666.5770] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 13 21:40:46 localhost.localdomain NetworkManager[883]: <info>  [1510605646.5585] audit: op="connection-activate" uuid="5cdf0c6e-4347-4239-83cb-99b915a50ddb" name="be24.nordvpn.com.tcp" pid=3509 uid=1000 resu
Nov 13 21:40:46 localhost.localdomain NetworkManager[883]: <info>  [1510605646.5699] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",0]: Started the VPN service, PID 6259
Nov 13 21:40:46 localhost.localdomain NetworkManager[883]: <info>  [1510605646.5879] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",0]: Saw the service appear; activating co
Nov 13 21:40:59 localhost.localdomain NetworkManager[883]: <info>  [1510605659.9442] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",0]: VPN plugin: state changed: starting (
Nov 13 21:40:59 localhost.localdomain NetworkManager[883]: <info>  [1510605659.9442] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",0]: VPN connection: (ConnectInteractive)
Nov 13 21:40:59 localhost.localdomain nm-openvpn[6295]: OpenVPN 2.4.4 x86_64-mageia-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Oct  2 2017
Nov 13 21:40:59 localhost.localdomain nm-openvpn[6295]: library versions: OpenSSL 1.0.2m  2 Nov 2017, LZO 2.09
Nov 13 21:41:00 localhost.localdomain nm-openvpn[6295]: WARNING: --ping should normally be used with --ping-restart or --ping-exit
Nov 13 21:41:00 localhost.localdomain nm-openvpn[6295]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Nov 13 21:41:00 localhost.localdomain nm-openvpn[6295]: TCP/UDP: Preserving recently used remote address: [AF_INET]185.210.217.140:443
Nov 13 21:41:00 localhost.localdomain nm-openvpn[6295]: Attempting to establish TCP connection with [AF_INET]185.210.217.140:443 [nonblock]
Nov 13 21:41:01 localhost.localdomain nm-openvpn[6295]: TCP connection established with [AF_INET]185.210.217.140:443
Nov 13 21:41:01 localhost.localdomain nm-openvpn[6295]: TCP_CLIENT link local: (not bound)
Nov 13 21:41:01 localhost.localdomain nm-openvpn[6295]: TCP_CLIENT link remote: [AF_INET]185.210.217.140:443
Nov 13 21:41:01 localhost.localdomain nm-openvpn[6295]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Nov 13 21:41:02 localhost.localdomain nm-openvpn[6295]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1604', remote='link-mtu 1636'
Nov 13 21:41:02 localhost.localdomain nm-openvpn[6295]: WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532'
Nov 13 21:41:02 localhost.localdomain nm-openvpn[6295]: [be24.nordvpn.com] Peer Connection Initiated with [AF_INET]185.210.217.140:443
Nov 13 21:41:03 localhost.localdomain nm-openvpn[6295]: TUN/TAP device tun0 opened
Nov 13 21:41:03 localhost.localdomain nm-openvpn[6295]: /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 6259 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_2 --tun -- tun0 1500 1555 10.7.7
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5246] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/4)
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5327] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",0]: VPN connection: (IP Config Get) reply
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5344] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: VPN connection: (IP4 Config Ge
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5350] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data: VPN Gateway: 185.210.217
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5350] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data: Tunnel Device: "tun0"
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data: IPv4 configuration:
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal Gateway: 10.7
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal Address: 10.7
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal Prefix: 24
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal Point-to-Poin
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5351] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Maximum Segment Size (
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Forbid Default Route:
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal DNS: 78.46.22
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   Internal DNS: 162.242.
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data:   DNS Domain: '(none)'
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: Data: No IPv6 configuration
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5352] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: VPN plugin: state changed: sta
Nov 13 21:41:03 localhost.localdomain nm-openvpn[6295]: GID set to nm-openvpn
Nov 13 21:41:03 localhost.localdomain nm-openvpn[6295]: UID set to nm-openvpn
Nov 13 21:41:03 localhost.localdomain nm-openvpn[6295]: Initialization Sequence Completed
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5414] vpn-connection[0x1b000c0,5cdf0c6e-4347-4239-83cb-99b915a50ddb,"be24.nordvpn.com.tcp",4:(tun0)]: VPN connection: (IP Config Get
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.5572] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6677] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6723] keyfile: add connection in-memory (fa3ace60-030d-4b92-8be1-b1fc8a45117d,"tun0")
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6732] device (tun0): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6749] device (tun0): Activation: starting connection 'tun0' (fa3ace60-030d-4b92-8be1-b1fc8a45117d)
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6908] device (tun0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6922] device (tun0): state change: prepare -> config (reason 'none') [40 50 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6926] device (tun0): state change: config -> ip-config (reason 'none') [50 70 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6937] device (tun0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6937] device (tun0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6949] device (tun0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.6954] device (tun0): state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.7114] policy: set 'tun0' (tun0) as default for IPv4 routing and DNS
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.7116] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.7187] device (tun0): Activation: successful, device activated.


Any ideas what I should try? I've read various threads about OpenVPN, but not clear to me what I should try.
Last edited by madcowsonthewall on Nov 20th, '17, 22:55, edited 2 times in total.
madcowsonthewall
 
Posts: 15
Joined: Sep 3rd, '11, 18:57

Re: Connecting to NordVPN via networkmanager

Postby doktor5000 » Nov 13th, '17, 23:48

madcowsonthewall wrote:Whenever I try to connect to Nordvpn, I end up without network connection.
Code: Select all
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.7187] device (tun0): Activation: successful, device activated.



How do you test the network connection? The VPN seems to be connected successfully. Although if you don't tick the checkbox "Use this connection only for resources on its network"
under routing for that VPN connection usually you end up with no internet connection and only the VPN connection, if that is what you mean.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Connecting to NordVPN via networkmanager

Postby wintpe » Nov 14th, '17, 11:46

sometimes peoples misconception of no network is that dns is not resolving.

if dns is trying to get to your router and the vpn is routing all traffic down the vpn tunnel, then you may experience that.

either your vpn provider will provide you with a dns resolver or set it to 8.8.8.8 googles dns

that should be reachable down the vpn

you can prove that im right about this

openup a konsole

su -
password:rootpassword

nslookup www.microsoft.com

if that fails to look up try

nslookup www.microsoft.com 8.8.8.8


if no nslookup then you need to urpmi bind-utils

again if that works, change your /etc/resolv.conf to point to 8.8.8.8

this will get updated everytime your network goes up and down, so if this works you need to reslve it permanently and we can help with that.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: Connecting to NordVPN via networkmanager

Postby madcowsonthewall » Nov 16th, '17, 22:27

By ticking the checkbox I can connect to the internet (as in using Firefox to browse the web, e.g. this forum), but it doesn't connect via the VPN connection. (my IP address is that of the internet provider)


doktor5000 wrote:
madcowsonthewall wrote:Whenever I try to connect to Nordvpn, I end up without network connection.
Code: Select all
Nov 13 21:41:03 localhost.localdomain NetworkManager[883]: <info>  [1510605663.7187] device (tun0): Activation: successful, device activated.



How do you test the network connection? The VPN seems to be connected successfully. Although if you don't tick the checkbox "Use this connection only for resources on its network"
under routing for that VPN connection usually you end up with no internet connection and only the VPN connection, if that is what you mean.


So I guess if I want to use VPN to hide my IP address while browsing the internet, I should uncheck the box, and resolve DNS problems. Thanks for pointing me in that direction, I'll try to figure this out further and come back.
madcowsonthewall
 
Posts: 15
Joined: Sep 3rd, '11, 18:57


Return to Networking

Who is online

Users browsing this forum: No registered users and 1 guest

cron