Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 2901

System and Network configuration • Re: KDE Plasma VPN connection successful but no access to remote network resources with Netgear Nighthawk X10 as VPN ser

$
0
0
Hi @Aki,
Thanks for the advice. Looks like the subject change has worked.

Yeah, totally understand. I tried running it via command line and got the following:

Code:

2024-02-27 22:11:33 us=192420 OpenVPN 2.6.3 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO]2024-02-27 22:11:33 us=192472 library versions: OpenSSL 3.0.11 19 Sep 2023, LZO 2.102024-02-27 22:11:33 us=192520 DCO version: N/A2024-02-27 22:11:33 us=199654 LZO compression initializing2024-02-27 22:11:33 us=199868 Control Channel MTU parms [ mss_fix:0 max_frag:0 tun_mtu:1250 tun_max_mtu:0 headroom:126 payload:1600 tailroom:126 ET:0 ]2024-02-27 22:11:33 us=330052 Data Channel MTU parms [ mss_fix:0 max_frag:0 tun_mtu:1500 tun_max_mtu:1600 headroom:136 payload:1800 tailroom:568 ET:32 ]2024-02-27 22:11:33 us=330284 TCP/UDP: Preserving recently used remote address: [AF_INET]MY_IP_ADDRESS2024-02-27 22:11:33 us=330378 Socket Buffers: R=[212992->212992] S=[212992->212992]2024-02-27 22:11:33 us=330439 UDPv4 link local: (not bound)2024-02-27 22:11:33 us=330481 UDPv4 link remote: [AF_INET]MY_IP_ADDRESSWR2024-02-27 22:11:33 us=366200 TLS: Initial packet from [AF_INET]MY_IP_ADDRESS, sid=1ea48043 e761fea4WRRWR2024-02-27 22:11:33 us=411355 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=netgear, OU=netgear, CN=netgear CA, name=EasyRSA, emailAddress=mail@netgear2024-02-27 22:11:33 us=411585 VERIFY KU OK2024-02-27 22:11:33 us=411603 Validating certificate extended key usage2024-02-27 22:11:33 us=411615 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication2024-02-27 22:11:33 us=411627 VERIFY EKU OK2024-02-27 22:11:33 us=411637 VERIFY OK: depth=0, C=TW, ST=TW, L=Taipei, O=netgear, OU=netgear, CN=server, name=EasyRSA, emailAddress=mail@netgearWRWWRRWR2024-02-27 22:11:33 us=534540 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, peer certificate: 1024 bit RSA, signature: RSA-SHA2562024-02-27 22:11:33 us=534635 [server] Peer Connection Initiated with [AF_INET]MY_IP_ADDRESS2024-02-27 22:11:33 us=534698 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=12024-02-27 22:11:33 us=534844 TLS: tls_multi_process: initial untrusted session promoted to trustedW2024-02-27 22:11:34 us=672272 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)WRR2024-02-27 22:11:34 us=716169 PUSH: Received control message: 'PUSH_REPLY,ping 10,ping-restart 120,route-delay 10,route-gateway 192.168.0.1,redirect-gateway def1,peer-id 0,cipher AES-256-GCM'2024-02-27 22:11:34 us=716285 OPTIONS IMPORT: route options modified2024-02-27 22:11:34 us=716301 OPTIONS IMPORT: route-related options modified2024-02-27 22:11:34 us=716327 net_route_v4_best_gw query: dst 0.0.0.02024-02-27 22:11:34 us=716437 net_route_v4_best_gw result: via 192.168.136.4 dev wlp2s02024-02-27 22:11:34 us=716510 ROUTE_GATEWAY 192.168.136.4/255.255.255.0 IFACE=wlp2s0 HWADDR=9c:b6:d0:14:9a:c52024-02-27 22:11:34 us=727454 TUN/TAP device tap0 opened2024-02-27 22:11:34 us=727500 do_ifconfig, ipv4=0, ipv6=02024-02-27 22:11:34 us=727598 Data Channel MTU parms [ mss_fix:1367 max_frag:0 tun_mtu:1500 tun_max_mtu:1600 headroom:136 payload:1800 tailroom:568 ET:32 ]2024-02-27 22:11:34 us=728008 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key2024-02-27 22:11:34 us=728053 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key2024-02-27 22:11:34 us=728095 Data Channel: cipher 'AES-256-GCM', peer-id: 0, compression: 'lzo'2024-02-27 22:11:34 us=728147 Timers: ping 10, ping-restart 120WR2024-02-27 22:11:45 us=79138 net_route_v4_add: MY_IP_ADDRESS/32 via 192.168.136.4 dev [NULL] table 0 metric -12024-02-27 22:11:45 us=79426 net_route_v4_add: 0.0.0.0/1 via 192.168.0.1 dev [NULL] table 0 metric -12024-02-27 22:11:45 us=79585 sitnl_send: rtnl: generic error (-101): Network is unreachable2024-02-27 22:11:45 us=79642 ERROR: Linux route add command failed2024-02-27 22:11:45 us=79673 net_route_v4_add: 128.0.0.0/1 via 192.168.0.1 dev [NULL] table 0 metric -12024-02-27 22:11:45 us=79775 sitnl_send: rtnl: generic error (-101): Network is unreachable2024-02-27 22:11:45 us=79817 ERROR: Linux route add command failed2024-02-27 22:11:45 us=79870 Initialization Sequence Completed
Please note I omitted the preceding config lines to minimise the amount of output.

I hope this helps?

Many thanks!

Statistics: Posted by dukman — 2024-02-27 11:31



Viewing all articles
Browse latest Browse all 2901

Trending Articles