Page 1 of 1

RTNETLINK answers: File exists

Posted: Sun 5 January 2020, 15:01
by tse
Hej,

Jag får inte igång min vpn-anslutning på en RPi 4 med openvpn-klient. Det avbryts med "RTNETLINK answers: File exists", se hela loggen nedanför. Hur kan jag avhjälpa det? Tack på förhand. /Tobias

Code: Select all

Sun Jan  5 14:46:25 2020 OpenVPN 2.4.7 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Sun Jan  5 14:46:25 2020 library versions: OpenSSL 1.1.1c  28 May 2019, LZO 2.10
Enter Auth Username: *******
Enter Auth Password: ********
Sun Jan  5 14:48:06 2020 WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Sun Jan  5 14:48:06 2020 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan  5 14:48:06 2020 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan  5 14:48:06 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]98.128.186.104:1196
Sun Jan  5 14:48:06 2020 Socket Buffers: R=[163840->163840] S=[163840->163840]
Sun Jan  5 14:48:06 2020 UDP link local: (not bound)
Sun Jan  5 14:48:06 2020 UDP link remote: [AF_INET]98.128.186.104:1196
Sun Jan  5 14:48:06 2020 TLS: Initial packet from [AF_INET]98.128.186.104:1196, sid=ae1d4df5 803f4889
Sun Jan  5 14:48:06 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Jan  5 14:48:06 2020 VERIFY OK: depth=1, C=SE, ST=S, L=Stockholm, O=5july.org, OU=integrityvpn, CN=integrity, name=integrity vpn, emailAddress=admin@integrity.st
Sun Jan  5 14:48:06 2020 VERIFY OK: nsCertType=SERVER
Sun Jan  5 14:48:06 2020 VERIFY OK: depth=0, C=SE, ST=S, L=Stockholm, O=5july.org, OU=integrity_vpn, CN=integrity, name=integrity, emailAddress=admin@integrity.st
Sun Jan  5 14:48:06 2020 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA
Sun Jan  5 14:48:06 2020 [integrity] Peer Connection Initiated with [AF_INET]98.128.186.104:1196
Sun Jan  5 14:48:07 2020 SENT CONTROL [integrity]: 'PUSH_REQUEST' (status=1)
Sun Jan  5 14:48:07 2020 PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.251.2.1,topology subnet,route 98.128.186.104 255.255.255.255 net_gateway,redirect-gateway def1,dhcp-option DNS 213.80.98.2,dhcp-option DNS 213.80.101.3,dhcp-option DNS 79.136.77.113,ping 5,ping-restart 30,ifconfig 10.251.2.225 255.255.255.0,peer-id 2,cipher AES-256-GCM'
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: timers and/or timeouts modified
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: --ifconfig/up options modified
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: route options modified
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: route-related options modified
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: peer-id set
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: adjusting link_mtu to 1625
Sun Jan  5 14:48:07 2020 OPTIONS IMPORT: data channel crypto options modified
Sun Jan  5 14:48:07 2020 Data Channel: using negotiated cipher 'AES-256-GCM'
Sun Jan  5 14:48:07 2020 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Jan  5 14:48:07 2020 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Jan  5 14:48:07 2020 ROUTE_GATEWAY 10.0.1.1/255.255.255.0 IFACE=eth0 HWADDR=dc:a6:32:0a:f0:24
Sun Jan  5 14:48:07 2020 TUN/TAP device tun0 opened
Sun Jan  5 14:48:07 2020 TUN/TAP TX queue length set to 100
Sun Jan  5 14:48:07 2020 /sbin/ip link set dev tun0 up mtu 1500
Sun Jan  5 14:48:07 2020 /sbin/ip addr add dev tun0 10.251.2.225/24 broadcast 10.251.2.255
Sun Jan  5 14:48:07 2020 /sbin/ip route add 98.128.186.104/32 via 10.0.1.1
Sun Jan  5 14:48:07 2020 /sbin/ip route add 0.0.0.0/1 via 10.251.2.1
Sun Jan  5 14:48:07 2020 /sbin/ip route add 128.0.0.0/1 via 10.251.2.1
Sun Jan  5 14:48:07 2020 /sbin/ip route add 98.128.186.104/32 via 10.0.1.1
RTNETLINK answers: File exists
Sun Jan  5 14:48:07 2020 ERROR: Linux route add command failed: external program exited with error status: 2
Sun Jan  5 14:48:07 2020 Initialization Sequence Completed

Re: RTNETLINK answers: File exists

Posted: Sun 5 January 2020, 18:26
by mattias
Förmodligen för att det finns två rader med samma "sbin/ip route add"

Sun Jan 5 14:48:07 2020 /sbin/ip route add 98.128.186.104/32 via 10.0.1.1

Sun Jan 5 14:48:07 2020 /sbin/ip route add 98.128.186.104/32 via 10.0.1.1

Re: RTNETLINK answers: File exists

Posted: Sun 5 January 2020, 18:42
by tse
ip route ger det här:

Code: Select all

default via 10.0.1.1 dev eth0 proto dhcp src 10.0.1.26 metric 202 
default via 10.0.1.1 dev eth0 proto dhcp src 10.0.1.26 metric 1024
Alltså dubbla default. Kan jag ta bort en/dem? Hur gör jag det?

Re: RTNETLINK answers: File exists

Posted: Mon 6 January 2020, 08:20
by Markus
du kan radera med te.x
ip route del default via 10.0.1.1 dev eth0 proto dhcp src 10.0.1.26 metric 1024

Jag tror du använder en äldre version av openvpn konfiguration fil. Har för mig vi skickar ut två routes pga av någon bug i äldre version av mac/tunnelblick. Men jag tror det borde fungera för dig ändå trots att du får två st routes skickade.

Re: RTNETLINK answers: File exists

Posted: Wed 15 January 2020, 06:44
by tse
Tack för svar Markus.Om min konfigurationsfil är gammal, var hittar jag en ny? Den har har är nerladdad från supportsidorna ganska nyligen. /Tobias

Re: RTNETLINK answers: File exists

Posted: Thu 23 January 2020, 14:37
by peter
Hej Markus,
jag har precis samma problem som @tse. Jag försöker ansluta med openvpn på Ubunt 18.04

Code: Select all

Thu Jan 23 14:30:53 2020 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Jan 23 14:30:53 2020 /sbin/ip link set dev tun0 up mtu 1500
Thu Jan 23 14:30:53 2020 /sbin/ip addr add dev tun0 10.251.0.65/24 broadcast 10.251.0.255
Thu Jan 23 14:30:53 2020 /sbin/ip route add 155.4.89.151/32 via 192.168.1.1
Thu Jan 23 14:30:53 2020 /sbin/ip route add 0.0.0.0/1 via 10.251.0.1
Thu Jan 23 14:30:53 2020 /sbin/ip route add 128.0.0.0/1 via 10.251.0.1
Thu Jan 23 14:30:53 2020 /sbin/ip route add 155.4.89.151/32 via 192.168.1.1
RTNETLINK answers: File exists
Jag antar att de dubbla ip route add-kommandona kommer från er serverkonfig, den är inte en del av klienten.

Re: RTNETLINK answers: File exists

Posted: Thu 23 January 2020, 15:28
by peter
Såg just att man ansluta med wireguard istället -- det fungerade prima!

(jag laborerade lite med att filtrera bort en ip route NN.** från config (med pull-filter) och kunde då ansluta, men det känns som det är något fel på serverkonfigurationen)