Portál AbcLinuxu, 10. května 2025 05:35
server: ... inactive 86400 max-clients 10 keepalive 5 60 ... klient: ... nobind keepalive 5 60 ping-timer-rem persist-tun persist-key ...Zbytek konfigurace se týká hlavně zapnutí komprese, certifikátů a šifer. V čem může být problém?
Řešení dotazu:
Tue Oct 7 12:07:08 2014 Initialization Sequence Completed Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:14:34 2014 write UDPv4: Network is unreachable (code=101) Tue Oct 7 12:15:33 2014 [r.domena.cz] Inactivity timeout (--ping-restart), restarting Tue Oct 7 12:15:33 2014 SIGUSR1[soft,ping-restart] received, process restarting Tue Oct 7 12:15:35 2014 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Tue Oct 7 12:15:43 2014 UDPv4 link local: [undef] Tue Oct 7 12:15:43 2014 UDPv4 link remote: [AF_INET]X.X.X.X:1194 Tue Oct 7 12:15:45 2014 [r.domena.cz] Peer Connection Initiated with [AF_INET]X.X.X.X:1194 Tue Oct 7 12:15:47 2014 Preserving previous TUN/TAP instance: tun0 Tue Oct 7 12:15:47 2014 Initialization Sequence CompletedServer nevypisuje chybu žádnou a po výpadku začíná klasicky s:
TLS: Initial packet from ...Během výpadku jsem paralelně pingoval skze tunel a mimo přímo na server. V tunelu výsledný výpadek 74/1065 paketů, mimo vypadl pouze 1/1065.
Sep 20 19:35:28 [kernel] [ 2038.990586] wlp24s0: associated
Sep 20 19:35:28 [kernel] [ 2038.990746] wlp24s0: deauthenticating from X by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 20 19:35:32 [kernel] [ 2042.997788] wlp24s0: authenticate with X
Sep 20 19:35:32 [kernel] [ 2042.999318] wlp24s0: send auth to X (try 1/3)
Sep 20 19:35:32 [kernel] [ 2043.000350] wlp24s0: authenticated
Sep 20 19:35:32 [kernel] [ 2043.001060] wlp24s0: associate with X (try 1/3)
Sep 20 19:35:32 [kernel] [ 2043.002929] wlp24s0: RX AssocResp from X (capab=0x411 status=0 aid=6)
Sep 20 19:35:32 [kernel] [ 2043.007153] wlp24s0: associated
a tak porad dokola
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)Ale v dmesg nevidím odpojování. S tím jsem míval problémy kdysi také na intel wifi síťovce, kde ale paradoxně openvpn tohle přežívalo v pohodě (i když byly výpadky delší).
Oct 7 12:14:29 vidim-notebook NetworkManager[1391]: <info> (wlan0): DHCPv4 state changed renew -> expire Oct 7 12:14:29 vidim-notebook dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x7820b435) Oct 7 12:14:29 vidim-notebook NetworkManager[1391]: <info> (wlan0): DHCPv4 state changed expire -> preinit Oct 7 12:14:32 vidim-notebook dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 (xid=0x7820b435) Oct 7 12:14:34 vidim-notebook dhclient: DHCPREQUEST of 192.168.54.33 on wlan0 to 255.255.255.255 port 67 (xid=0x7820b435) Oct 7 12:14:34 vidim-notebook dhclient: DHCPOFFER of 192.168.54.33 from 192.168.54.1 Oct 7 12:14:34 vidim-notebook kernel: [682278.099693] [UFW BLOCK] IN=wlan0 OUT=wlan0 MAC=6c:88:14:55:34:80:00:0d:b9:0d:3e:5c:08:00 SRC=192.168.54.1 DST=192.168.54.33 LEN=389 TOS=0x10 PREC=0x00 TTL=127 ID=0 PROTO=UDP SPT=67 DPT=68 LEN=369 Oct 7 12:14:34 vidim-notebook kernel: [682278.189984] [UFW BLOCK] IN=wlan0 OUT=wlan0 MAC=6c:88:14:55:34:80:00:0d:b9:0d:3e:5c:08:00 SRC=192.168.54.1 DST=192.168.54.33 LEN=389 TOS=0x10 PREC=0x00 TTL=127 ID=0 PROTO=UDP SPT=67 DPT=68 LEN=369 Oct 7 12:14:34 vidim-notebook dhclient: DHCPACK of 192.168.54.33 from 192.168.54.1 Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> (wlan0): DHCPv4 state changed preinit -> bound Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> address 192.168.54.33 Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> prefix 24 (255.255.255.0) Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> gateway 192.168.54.1 Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> nameserver '192.168.54.1' Oct 7 12:14:34 vidim-notebook NetworkManager[1391]: <info> domain name 'in.X.net' Oct 7 12:14:34 vidim-notebook dhclient: bound to 192.168.54.33 -- renewal in 1710 seconds. Oct 7 01:26:37 vidim-notebook avahi-daemon[1051]: message repeated 2 times: [ Withdrawing workstation service for tun0.] Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: Withdrawing address record for 192.168.54.39 on wlan0. Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.54.39. Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: Interface wlan0.IPv4 no longer relevant for mDNS. Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.54.33. Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: New relevant interface wlan0.IPv4 for mDNS. Oct 7 12:14:34 vidim-notebook avahi-daemon[1051]: Registering new address record for 192.168.54.33 on wlan0.IPv4. Oct 7 12:14:35 vidim-notebook NetworkManager[1391]: <info> Policy set 'mojewifi' (wlan0) as default for IPv4 routing and DNS. Oct 7 12:14:35 vidim-notebook dbus[1011]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Oct 7 12:14:36 vidim-notebook dbus[1011]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 9 00:56:50 rimmer dhcpd: DHCPDISCOVER from 6c:88:14:55:34:80 via eth0.1 Oct 9 00:56:50 rimmer dhcpd: ICMP Echo reply while lease 192.168.54.35 valid. Oct 9 00:56:50 rimmer dhcpd: Abandoning IP address 192.168.54.35: pinged before offer Oct 9 00:56:53 rimmer dhcpd: DHCPDISCOVER from 6c:88:14:55:34:80 via eth0.1 Oct 9 00:56:55 rimmer dhcpd: DHCPOFFER on 192.168.54.43 to 6c:88:14:55:34:80 (vidim-notebook) via eth0.1 Oct 9 00:56:55 rimmer dhcpd: Added new forward map from vidim-notebook.dyn.X.net to 192.168.54.43 Oct 9 00:56:55 rimmer dhcpd: added reverse map from 43.54.168.192.in-addr.arpa to vidim-notebook.dyn.X.net Oct 9 00:56:55 rimmer dhcpd: DHCPREQUEST for 192.168.54.43 (192.168.54.1) from 6c:88:14:55:34:80 (vidim-notebook) via eth0.1 Oct 9 00:56:55 rimmer dhcpd: DHCPACK on 192.168.54.43 to 6c:88:14:55:34:80 (vidim-notebook) via eth0.1Přijde mi to ale jako nelogické chování - proč odmítat opětovně přidělit IP, která je moje? Nebo se můj dhcp klient špatně ptá a server reaguje korektně?
vytvořit skript např. /etc/pm/sleep.d/99_kill_dhclient s obsahem:
#!/bin/bash
case "$1" in
hibernate|suspend)
echo ""
;;
thaw|resume)
killall dhclient
;;
*)
;;
esac
exit $?
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.