Hi, On 19/01/2019 17:26, ripe@brite.cz wrote:

Traceroute to 2001:503:ba3e::2:30 (2001:503:ba3e::2:30), 40 byte packets 1 * 2a00:1028:8d1c:90da:220:4aff:fee0:2026 dynamic-2a00-1028-8d1c-90da-0220-4aff-fee0-2026.ipv6.broadband.iol.cz AS5610 2191.889ms !H 3010.564ms !H

From `man traceroute6`:

!H  Address unreachable         The  host  address  is not reachable for some other reasons, particularly a link-         layer failure (e.g. Neighbor discovery failure).

Obviously that's not great! The probe has a v6 address, so it's solicited and received some network config when it was booted or when your network config changed a couple days ago. Question is, what happened next. Guessing around the symptoms, if it's not receiving subsequent periodic RAs (either the router isn't sending them or something is preventing the probe from receiving them), then its local routing state will expire. Questions I'd try and answer are: when you connect a device to the same network, does it a) receive a v6 network & generate an address, then b) does v6 work immediately after that, and c) does it fail after a while? S.

______________________________________________________________

...

Od: ripe@brite.cz Komu: ripe-atlas@ripe.net Datum: 19.01.2019 17:23 Předmět: Re: [atlas] IPv6 Doesn't Work

No filtering here. Furthermore it seems the Atlas Probe is not able to get anywhere out via IPv6 too. I'm wondering is the Gateway setting correct? [Gateway(s) fe80::1]

--------------------------------- Peter Eckel lists at eckel-edv.de Sat Jan 19 11:26:33 CET 2019

Hi Jiri,

for me it looks like you're not reachable indeed:

...

pete at charon.net.hindenburgring.com> traceroute inet6 2a00:1028:8d1c:90da:220:4aff:fee0:2026 traceroute6 to 2a00:1028:8d1c:90da:220:4aff:fee0:2026 (2a00:1028:8d1c:90da:220:4aff:fee0:2026) from <xxx>, 64 hops max, 12 byte packets [...] 3 2a00:19e0:ffff:fffc::1 (2a00:19e0:ffff:fffc::1) 23.579 ms 23.308 ms 23.495 ms 4 2a00:19e0:ffff:ffff::3 (2a00:19e0:ffff:ffff::3) 29.521 ms 29.738 ms 29.822 ms 5 ae0-401.fra10.core-backbone.com (2a01:4a0:1338:2::1) 30.063 ms 29.215 ms 36.436 ms 6 ae2-2001.nbg30.core-backbone.com (2a01:4a0:0:2001::1) 32.540 ms 31.789 ms 51.790 ms 7 ae1-2053.prg10.core-backbone.com (2a01:4a0:0:2053::22) 37.175 ms 36.355 ms 35.141 ms 8 nix4-ipv6.pater.iol.cz (2001:7f8:14::29:1) 39.033 ms 36.891 ms 37.997 ms 9 dynamic-2a00-1028-0001-0160-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:160::2) 38.403 ms 41.560 ms 37.239 ms 10 dynamic-2a00-1028-0001-02a5-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:2a5::2) 37.214 ms 50.273 ms 51.604 ms 11 * * * 12 dynamic-2a00-1028-8d1c-90d8-0000-0000-0000-0001.ipv6.broadband.iol.cz (2a00:1028:8d1c:90d8::1) 44.291 ms 58.819 ms 49.810 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * [...] Are you by any chance filtering ICMPv6 on your ingress router?

Regards,

Peter.