Hi, yesterday I thought about naming my different tunX devices for various tunnels to qualified identifiers. Used Versions are: - OpenVPN 2.0.6 - Linux Kernel 2.6.20 My current setup is working ok, if I do not mangle the name of the tun-Interface: Using the above, I get an Interface "tun0" and the script binds the IPv6 IP and the route to the /64-subnet via that interface correctly. As soon as the tunnel is established, I am able to ping6/traceroute6 through that tunnel from the oher side or even my LAN at home that gets the subnet advertised through radvd. Now the problem: If I set a name to the tun interface - like "tunv6" or "homev6" and change the config file like: Then I bring up the named tun Interface and start the OpenVPN daemon with the modified config file. As a result, I get a tun interface named "homev6" with everything set up like as it had been with "tun0".. the log file says connection established and according to "ip -6 a s" and "ip -6 r s" output everything seems to be ok. Alas, I'm not even able to ping6 through the tunnel... not even from endpoint to endpoint using the /112 v6-IP pair.. As a sidenote: The renaming of plain IPv4 tun interfaces for the other three IPv4-OpenVPN-Tunnels on this machine worked like charm using the very same procedure... Is that supposed to be a bug in: a) OpenVPN? b) Linux Kernel tuntap device? c) ..? or is it simply PEBKAC..? O-) Christian