|
From: Holger K. <Hol...@So...> - 2015-06-26 17:07:58
|
Hello, Am 26.06.2015 um 13:24 schrieb Gert Doering: > And I actually *do* test for this in one of my t_client test runs... :-) > > openvpn --client ... --nobind --comp-lzo --verb 3 --dev tun3 --proto tcp6-client --remote conn-test-server.openvpn.org --port 51194 --server-poll-timeout 10 > > ... and it "just works" - "ip -6 addr add ... dev tun3" on connect, nothing > special on disconnect, and "no problems" (on Gentoo Linux, but "ip" should > be sufficiently standard): > > Fri Jun 26 13:18:05 2015 /bin/ip -6 addr add fd00:abcd:194:1::100c/64 dev tun3 > Fri Jun 26 13:18:05 2015 /bin/ip -6 route add fd00:abcd:194::/48 dev tun3 > ... > Fri Jun 26 13:18:46 2015 event_wait : Interrupted system call (code=4) > Fri Jun 26 13:18:46 2015 /bin/ip route del 10.194.0.0/16 > Fri Jun 26 13:18:46 2015 /bin/ip route del 10.194.1.1/32 > Fri Jun 26 13:18:46 2015 delete_route_ipv6(fd00:abcd:194::/48) > Fri Jun 26 13:18:46 2015 /bin/ip -6 route del fd00:abcd:194::/48 dev tun3 > Fri Jun 26 13:18:46 2015 Closing TUN/TAP interface > Fri Jun 26 13:18:46 2015 /bin/ip addr del dev tun3 local 10.194.1.54 peer 10.194.1.53 > > So, what is different on your end? Why is the tun<x> keeping its address? This looks similar on my machine. But the difference comes when after the disconnect a new connect is forced which failed on my site. Holger |