[ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
- Previous message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
- Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
woeber at cc.univie.ac.at
Tue Nov 17 14:48:52 CET 2015
Hi Jen and v6 aficionados, please disregard, there seems to be a mix-up with the versions of traceroute and tcptraceroute I did install just recently. tcptraceroute seems to have no support for -6 and traceroute seems to recognize -4 and -6, but -P tcp fails for both. Sorry, Wilfried On 2015-11-16 17:05, Jen Linkova wrote: > On Mon, Nov 16, 2015 at 3:22 PM, Wilfried Woeber <woeber at cc.univie.ac.at> wrote: >> I may be looking at something that isn't expected to work in this set-up at all, but still: >> >> traceroute to my workstation back home in "default" command-line does not work, it comes >> back with "network is unreachable". Adding -6 flag to force using the AAAA DNS response >> makes it work. According to the man page it should select the version automatically. >> >> Requesting TCP mode fails completely to come back with answers, even when forcing -6 > > So does TCP mode work for Ipv6 address on the dual-stack network?
- Previous message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
- Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]