From: Thomas S. <tsc...@t-...> - 2017-01-18 15:43:36
|
Hi, In case of being totally wrong here, please redirect me to the right place (bug-systems, forum,...). Some words about the configuration: Server: shares a private IPv4-Network and ula-IPv6-Network IPv4-Adresses also NATed to the public. proto udp6 dev tun ca ca.crt cert server.crt key server.key dh dh2048.pem server 192.168.178.128 255.255.255.128 server-ipv6 fd00::1:1/112 push "route 192.168.178.0 255.255.255.0" push "route-ipv6 fd00::/64" keepalive 10 120 verb 3 Client: client dev tun proto udp6 remote raspberrypi.XXXXXXXX.myfritz.net 1194 udp6 ca ca.crt cert client.crt key client.key remote-cert-tls server redirect-gateway verb 3 This works perfectly as long the client has still an IPv4-connection. But in case of an IPv6-only-client (not system-wide disabled, just not getting IPv4-addresses by the ISP, e.g. eduroam-IPv6) the client doesn't set the IPv4-default route, since it can not find the old one. Regards, Thomas |