This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[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 ]

Jen Linkova furry13 at gmail.com
Mon Nov 16 16:05:13 CET 2015

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?


-- 
SY, Jen Linkova aka Furry

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 ]