AS overview
Test target: 2a02:ec:260c:9002::1 · ns1.freedns.si · address space: unknown · prefixes announced: 1
prefix(es): 2a02:ec::/32
Targets & per-vantage-point probe results (1 target(s) across 3 vantage point(s))
Source codes (hover any badge for full description): CUR=curated · NS/SOA/MX=DNS records · SPF=SPF TXT · DRV=holder-derived (www, ns1, mail, gw, …) · ATL=RIPE Atlas · PDB=PeeringDB · WHOIS=RIPE whois · RDAP=RIPE RDAP · HIT=IPv6 Hitlist · RTR=in-prefix path hop (router) · PRB=static prefix probe · SYN=synthetic prefix::1 fallback
| Target IP / hostname | Source | NL host (go6lab) | ITA host (Karsolink) | SLO host (6connect) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ping | 1500B | :80 | :443 | reached | ||
2a02:ec:260c:9002::1ns1.freedns.si | NS | ✓ | ✓ | ? | ? | ✓ | ✓ | ✓ | refused | refused | ✓ | ✓ | ✓ | refused | refused | ✓ |
SIX peering
SIX member - open peering, peering member, since 2013-09-18. IPv6 LAN: 2001:7f8:46:0:0::4:3128. Locations: lj_ijs, lj_tpl.
- rs1-lan1-ipv6 →
2001:7f8:46::4:3128Established (loc: lj_ijs, since 2026-05-25) - rs1-lan1-ipv6 →
2001:7f8:46:0:1:0:4:3128Established (loc: lj_tpl, since 2026-05-16) - rs2-lan1-ipv6 →
2001:7f8:46::4:3128Established (loc: lj_ijs, since 2026-05-12) - rs2-lan1-ipv6 →
2001:7f8:46:0:1:0:4:3128Established (loc: lj_tpl, since 2026-05-12)
Announces via SIX route servers: 1 prefix(es) - 2a02:ec::/32
RPKI & ASPA
1 of 1 prefix(es) covered by a valid ROA.
| Prefix | RPKI state | Reason | Covering VRP(s) |
|---|---|---|---|
2a02:ec::/32 | ✓ valid | matched VRP (correct origin, length within maxLength) | AS43128 /32 maxLen 48 (ripe) |
Random-IP probe (yarrp) into the AS' prefixes
We probed 15 arbitrary IPv6 address(es) inside AS43128's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2001:978:2:39::a:2 at hop 14 - that router answers ICMPv6 Echo. This is not in AS43128's announced prefix; operationally it's the AS-edge / peering interface (often on a SIX peering address or an upstream's /127 link). The traceroute boundary is the AS edge: ICMPv6 Time-Exceeded responses from anything inside this AS are filtered.
ICMPv6 Type 2 (Packet Too Big) acceptance - active test
Vantage points disagree about Type 2 acceptance - transit ASes on one path may be filtering Type 2 even though the destination's stack accepts it on another path:
- NL host (go6lab): Type 2 NOT honored. Forged PTB had no effect (filtered en route or stack ignored it). (ICMPv6 Echo + forged PTB)
- ITA host (Karsolink): inconclusive: no Echo Reply to 1300-byte probe. (ICMPv6 Echo + forged PTB)
- SLO host (6connect): Type 2 NOT honored. Forged PTB had no effect (filtered en route or stack ignored it). (ICMPv6 Echo + forged PTB)
Why they disagree - reachability mismatch: One vantage couldn't drive a flow at all to this destination (no Echo Reply or no responding TCP port), so the active test had no behavioural change to observe. The other vantage's verdict is the only meaningful one here.
Failure detail — what to grep in your logs
| vantage | our source | your target | method | result | tested (UTC) |
|---|---|---|---|---|---|
| go6lab | 2a00:8642:42::75 | 2a02:ec:260c:9002::1 | icmp6-echo | not_honored | 2026-05-30T10:34:52Z |
| karsolink | 2a12:d8c0:105a:9001::a154 | 2a02:ec:260c:9002::1 | icmp6-echo | no_echo | 2026-05-30T10:44:01Z |
| odin | 2607:fae0:a000::42 | 2a02:ec:260c:9002::1 | icmp6-echo | not_honored | 2026-05-30T10:34:36Z |
Attempt log (go6lab):
icmp6-echo→ not_honored (size_before=1460, size_after=1460)dns-tcp→ inconclusive (size_before=135, size_after=None): max DNS-over-TCP segment 135B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (karsolink):
icmp6-echo→ no_echo: no Echo Reply to 1300-byte probedns-tcp→ inconclusive (size_before=135, size_after=None): max DNS-over-TCP segment 135B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
Attempt log (odin):
icmp6-echo→ not_honored (size_before=1460, size_after=1460)dns-tcp→ inconclusive (size_before=135, size_after=None): max DNS-over-TCP segment 135B; not big enough to test PMTU shrinktls→ no_tcp: TLS connect failedhttp→ no_tcp: tcp/80 not open
To match the corresponding ICMPv6 packet on your side (host firewall, AS edge, or transit tap), look for our PTBs around the timestamps above:
sudo tcpdump -i any -n -e 'icmp6 and ip6[40] = 2 and (src host 2607:fae0:a000::42 or src host 2a00:8642:42::75 or src host 2a12:d8c0:105a:9001::a154)'
If you see our PTBs arriving but the destination's TCP/Echo flow does not shrink, the drop is in the destination kernel (cause 3 below). If you don't see them at all, drop is upstream of you (cause 2). If you only see them from one of our two source IPs, the drop is path-asymmetric — one transit on the asymmetric route is filtering, the other is not.
What does "Type 2 not honored" actually mean? — click to expand
What this test does
Using the icmp6-echo method, we send a 1500-byte ICMPv6 Echo Request, then a forged ICMPv6 Type 2 (Packet Too Big) declaring path MTU=1280, and observe whether the next Echo Reply arrives split into IPv6 fragments. RFC 4890 requires hosts and intermediate networks not to filter ICMPv6 Type 2; the destination's TCP/UDP stack must act on a received PTB by lowering its Path MTU cache for that destination, which makes subsequent segments smaller.
What we measured
The TCP segment size your server emitted before our forged Type 2 was 1460 B; after, it was 1460 B. No change. RFC 4890 ("Type 2 messages MUST NOT be filtered") expects subsequent segments to shrink to fit a Path MTU of 1280 B.
Three plausible causes
- Your host firewall is dropping ICMPv6 Type 2 inbound. Many default firewall rule sets only allow Echo Request/Reply and Neighbor Discovery, silently dropping all other ICMPv6 types - including Packet Too Big.
- An upstream / transit network is dropping ICMPv6 Type 2 before it reaches you. Some transit ASes filter ICMPv6 messages other than Echo at the edge. The forged PTB never arrives, so your stack never has a chance to act on it.
- Your kernel is ignoring the PTB. Linux / BSD stacks normally accept ICMPv6 PTB and update the route cache, but a few sysctls (or a hardened kernel) can be configured to ignore PMTU updates - typically as part of an over-aggressive anti-spoofing or uRPF policy.
How to check & fix (Linux examples)
1. Confirm Type 2 is not blocked at the host firewall:
sudo ip6tables -L INPUT -nv | grep -iE 'icmpv6|packet-too-big' sudo nft list ruleset 2>/dev/null | grep -A1 'icmpv6'
If you see rules dropping ICMPv6 unconditionally, change them to permit at least icmpv6 type packet-too-big (and destination-unreachable, time-exceeded, parameter-problem per RFC 4890).
2. Confirm the kernel accepts incoming PTB:
sudo sysctl net.ipv6.conf.all.accept_redirects net.ipv4.ip_no_pmtu_disc net.ipv6.route.mtu_expires
The defaults (accept_redirects=1, ip_no_pmtu_disc=0) are the right values for honoring PTB.
3. Live trace: while we have an open TCP flow with a small MSS (we run our test from 2607:fae0:a000::42 on odin, 2a00:8642:42::75 on go6lab and 2a12:d8c0:105a:9001::a154 on karsolink), watch for our forged Type 2 arriving on your interface:
sudo tcpdump -i any -n -e 'icmp6 and ip6[40] = 2 and (src host 2607:fae0:a000::42 or src host 2a00:8642:42::75 or src host 2a12:d8c0:105a:9001::a154)'
If you see our PTBs arriving but TCP segments still stay big, the drop is in your kernel or NIC offload (cause 3). If you don't see them at all, the drop is upstream of you (cause 2) - ask your upstream(s) to permit ICMPv6 Type 2.
4. If your test target above (2026-05-30T10:34:52Z) is a host that you don't own (e.g. a third-party DNS / TLS server you happen to operate prefixes for), the verdict reflects that specific host's behaviour - try the test against a server you do own and we'll happily re-run.
RFC 4890 references: §4.3.1 (Packet Too Big - MUST NOT be dropped), and RFC 8201 for the broader PMTUD requirement.
Where the path divergence is
Per-vantage probe + verdict (headline):
- go6lab: probe
icmp6-echo→ verdictnot_honored - karsolink: probe
icmp6-echo→ verdictno_echo - odin: probe
icmp6-echo→ verdictnot_honored
Full per-method matrix (all four methods run at each vantage):
| vantage | icmp6-echo | dns-tcp | tls | http |
|---|---|---|---|---|
| go6lab | not_honored | inconclusive | no_tcp | no_tcp |
| karsolink | no_echo | inconclusive | no_tcp | no_tcp |
| odin | not_honored | inconclusive | no_tcp | no_tcp |
✓ All vantages agree on method(s): icmp6-echo — the headline-method spread above is dispatcher noise, not a real Type 2 disagreement.
These vantage-level disagreements are rooted somewhere in the forward paths. Joining each per-vantage traceroute against the IP→AS lookup from our global yarrp mesh, the first hop where the paths land in different ASes is the most likely site of the offending filter / unreachable AS / Type 2 drop.
Suspect transit ASes (ranked by how often they appear at the divergence point on the path of the worse-classifying vantage): AS43128, AS174.
- From go6lab (open/Type-2=not_honored) the path enters an opaque hop at hop 14; from karsolink (open/Type-2=no_echo) the same hop is in AS174. Last common AS: AS43128. The disagreement is most likely rooted in one of those two transit ASes.
- From go6lab (open/Type-2=not_honored) the path enters AS43128 at hop 15; from odin (open/Type-2=not_honored) the same hop is in an opaque hop. Last common AS: AS43128. The disagreement is most likely rooted in one of those two transit ASes.
- From karsolink (open/Type-2=no_echo) the path enters AS43128 at hop 16; from odin (open/Type-2=not_honored) the same hop is in an opaque hop. Last common AS: AS43128. The disagreement is most likely rooted in one of those two transit ASes.
Diagnosis is path-level, not packet-level: it tells you which transit AS is the prime suspect, not exactly which firewall rule is to blame. Use the tracepath6 output below (when available) for per-hop PMTU evidence on the same path.
✨ Diagnostic interpretation
Per-hop PTB acceptance walk
From the local vantage, we walk the forward path hop-by-hop, sending each hop a 1500-byte ICMPv6 Echo, then a forged PTB (MTU=1280) sourced from us, then another 1500-byte Echo. If the second reply arrives fragmented or smaller, that hop honoured the PTB. If unchanged, it didn't. The first ✗ in an otherwise-✓ path is the most likely filter location. Cross-country aggregation: see the global PTB filter atlas for transit ASes ranked by filter rate across all measurements.
| # | hop IP | AS | Holder | PTB acceptance |
|---|---|---|---|---|
| 1 | 2607:fae0:a000::2 | AS8038 | 6CONNECT - 6connect, Inc., US | - skipped (CoPP) |
| 2 | * | - | - (no IP) | |
| 3 | * | - | - (no IP) | |
| 4 | 2001:7f8:46::4:3128 | AS51988 | ARNES-SIX - ARNES, SI | ? no_response |
| 5 | fc00:0:1f00:b000::5 | - | NA | ? no_response |
| 6 | 2a02:ec:260c:9002::1 | AS43128 | DHH-AS - DHH-AS, SI | ? no_response |
Tests host-mode PTB acceptance (PTBs aimed at the hop itself). A router that honours PTBs to itself can still be filtering PTBs transiting through it; this is one indicator, not proof of full PTB transparency. Hops in CoPP-rate-limit ranges are skipped to avoid false signals.
From NL host (go6lab) openRFC 4890 ✗
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | 2a00:8642:42::3 | 1.2ms | 0% | AS203993 | STEFFANN-DC-AS - S.J.M. Steffann, NL |
| 2 | * | - | - | - | |
| 3 | 2a00:1ca8:1::194 | 2.1ms | 0% | AS50673 | Serverius-as - Serverius Holding B.V., NL |
| 4 | 2a03:3f40::10:41 | 2.1ms | 0% | AS50673 | Serverius-as - Serverius Holding B.V., NL |
| 5 | * | - | - | - | |
| 6 | * | - | - | - | |
| 7 | be3343.ccr41.fra05.atlas.cogentco.com 2001:550:0:1000::9a36:3e8d | 11.8ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 8 | * | - | - | - | |
| 9 | be9456.ccr82.vie01.atlas.cogentco.com 2001:550:0:1000::9a36:3f8d | 24.0ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 10 | be7244.agr62.vie01.atlas.cogentco.com 2001:550:0:1000::9a36:276e | 24.0ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 11 | be3189.rcr61.lju01.atlas.cogentco.com 2001:550:0:1000::9a36:4ac5 | 30.2ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 12 | be3191.nr61.b021176-0.lju01.atlas.cogentco.com 2001:550:0:1000::9a19:e7a | 29.3ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 13 | 2001:978:2:39::a:2 | 29.2ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 14 | fc00:0:1f00:b000::5 | 30.1ms | 0% | - | NA |
| 15 | ns1.freedns.si 2a02:ec:260c:9002::1 | 31.2ms | 0% | AS43128 | DHH-AS - DHH-AS, SI |
tracepath -6
1?: [LOCALHOST] 0.045ms pmtu 1500
1: 2a00:8642:42::3 1.575ms
1: 2a00:8642:42::3 2.159ms
2: gw.friends.steffann.nl 1.941ms
3: 2a00:1ca8:1::194 3.535ms
4: 2a03:3f40::10:41 3.085ms
5: no reply
6: no reply
7: be2950.ccr42.fra05.atlas.cogentco.com 11.914ms
8: no reply
9: be9456.ccr82.vie01.atlas.cogentco.com 24.054ms
10: be4079.agr61.vie01.atlas.cogentco.com 23.409ms
11: be3189.rcr61.lju01.atlas.cogentco.com 29.282ms
12: be9462.nr61.b021176-0.lju01.atlas.cogentco.com 30.752ms
13: 2001:978:2:39::a:2 28.466ms
14: fc00:0:1f00:b000::5 29.652ms asymm 15
15: ns1.freedns.si 30.269ms reached
Resume: pmtu 1500 hops 15 back 16 From ITA host (Karsolink) open
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | * | - | - | - | |
| 2 | * | - | 0%* | - | |
| 3 | * | - | - | - | |
| 4 | 2a03:b020:1:51::a | 10.1ms | 0% | AS41327 | FIBERTELECOM-AS - Fiber Telecom S.p.A., IT |
| 5 | 2a03:b020::246 | 10.0ms | 0% | AS41327 | FIBERTELECOM-AS - Fiber Telecom S.p.A., IT |
| 6 | 2001:978:2:2a::e7:1 | 10.7ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 7 | be4823.agr61.mil02.atlas.cogentco.com 2001:550:0:1000::9a19:8c5 | 10.5ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 8 | port-channel3336.ccr92.mil02.atlas.cogentco.com 2001:550:0:1000::9a36:4d39 | 10.3ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 9 | * | - | - | - | |
| 10 | be5456.ccr81.vie01.atlas.cogentco.com 2001:550:0:1000::9a36:48a6 | 26.3ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 11 | be7244.agr62.vie01.atlas.cogentco.com 2001:550:0:1000::9a36:276e | 24.9ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 12 | be9461.rcr62.lju01.atlas.cogentco.com 2001:550:0:1000::9a36:48a2 | 31.2ms | 10% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 13 | be3191.nr61.b021176-0.lju01.atlas.cogentco.com 2001:550:0:1000::9a19:e7a | 31.8ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 14 | 2001:978:2:39::a:2 | 31.4ms | 0% | AS174 | COGENT-174 - Cogent Communications, LLC, US |
| 15 | * | - | - | - | |
| 16 | ns1.freedns.si 2a02:ec:260c:9002::1 | 28.9ms | 0% | AS43128 | DHH-AS - DHH-AS, SI |
Rate-limited ICMPv6: hop 12 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).
tracepath -6
1?: [LOCALHOST] 0.029ms pmtu 1500
1: no reply
2: 2a12:d8c0:109f:121::a1 1.115ms
3: 2a12:d8c0:101f:6::1 10.708ms
4: 2a03:b020:1:51::a 10.666ms
5: 2a03:b020::246 10.763ms asymm 6
6: 2001:978:2:2a::e7:1 11.043ms asymm 7
7: be4918.agr62.mil02.atlas.cogentco.com 11.048ms asymm 8
8: port-channel4689.ccr91.mil02.atlas.cogentco.com 10.598ms asymm 9
9: no reply
10: be5456.ccr81.vie01.atlas.cogentco.com 26.188ms asymm 11
11: be3935.agr61.vie01.atlas.cogentco.com 25.531ms asymm 12
12: be3189.rcr61.lju01.atlas.cogentco.com 31.772ms asymm 13
13: be3191.nr61.b021176-0.lju01.atlas.cogentco.com 32.207ms asymm 14
14: 2001:978:2:39::a:2 32.305ms asymm 15
15: no reply
16: ns1.freedns.si 29.095ms reached
Resume: pmtu 1500 hops 16 back 10 From SLO host (6connect) openRFC 4890 ✗
filter likely at: (none) · min PMTU on path: 1500
Path (traceroute + mtr + PTR)
| # | IP / PTR | RTT | mtr loss | AS | AS holder |
|---|---|---|---|---|---|
| 1 | fw1-lju.6connect.com 2607:fae0:a000::2 | 0.2ms | 0%* | AS8038 | 6CONNECT - 6connect, Inc., US |
| 2 | * | - | - | - | |
| 3 | * | - | 40% | - | |
| 4 | 2001:7f8:46::4:3128 @SIX | 1.6ms | 0% | AS51988 | ARNES-SIX - ARNES, SI |
| 5 | fc00:0:1f00:b000::5 | 1.1ms | 0% | - | NA |
| 6 | ns1.freedns.si 2a02:ec:260c:9002::1 | 1.1ms | 0% | AS43128 | DHH-AS - DHH-AS, SI |
Rate-limited ICMPv6: hop 3 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).
tracepath -6
1?: [LOCALHOST] 0.025ms pmtu 1500
1: fw1-lju.6connect.com 0.492ms
1: fw1-lju.6connect.com 0.573ms
2: no reply
3: 2a03:a100:0:201:1::1 0.610ms
4: 2001:7f8:46::4:3128 1.139ms
5: fc00:0:1f00:b000::5 1.055ms
6: ns1.freedns.si 1.169ms reached
Resume: pmtu 1500 hops 6 back 6