Hi Jari, thanks for the note!
On 09/27/2011 11:32 PM, Jari Aalto wrote: > After applying it, there is a report that it affecs the ipv4. > > [bug content is a little vague] > https://bugs.launchpad.net/ubuntu/+source/6tunnel/+bug/739471 I could reproduce this: # 6tunnel -v 84 reader.ipv6.xsnews.nl 80 resolving reader.ipv6.xsnews.nl local: default,84; remote: reader.ipv6.xsnews.nl,80; source: default # 6tunnel -6 -v 84 reader.ipv6.xsnews.nl 80 resolving reader.ipv6.xsnews.nl 6tunnel: unable to resolve host reader.ipv6.xsnews.nl As you can see, the first command works, but in the second command, we are trying to use IPv6->IPv6 connection which doesn't work. The other connection, IPv4->IPv6 works. > [*] if you would have also thoughs for http://bugs.debia.org/610979 The > Debian code is at git clone This looks like basically the same issue. Currently, IPv4->IPv4 and IPv6->IPv6 doesn't work. Only IPv4->IPv6 and IPv6->IPv4 as documented in the manual. (My patch fixed one of those two.) We have two options now: Only support the IPv4<->IPv6 connections or extend the functionality (and documentation) to the other combinations as well. It is really unfortunate that the other combinations currently don't work but tunneling between the same protocol wasn't the original intention of the program (but connection between IPv6 and IPv4). There are other solutions for that (netcat, ssh etc.). A further patch would be nice to support the additional combinations. Unfortunately, I currently don't have much time to look into it. bye, Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
