AS212813 - Lindner Lindner-RecyclingtechPARFC 4890 ✓RPKI ✓ 1/1ASPA -

AS overview

Test target: 2a10:2680::16 · (SPF ip6: literal) · address space: PA · prefixes announced: 1

prefix(es): 2a10:2680::/29

VIX / AAIX / SAIX / TIROL-IX / ERA-IX peering

Random-IP probe (yarrp) into the AS' prefixes

We probed 35 arbitrary IPv6 address(es) inside AS212813's announced prefix(es). No router inside the prefix responded. The deepest visible hop was 2a00:11c0:47:3::10d at hop 11 - that router answers ICMPv6 Echo. This is not in AS212813's announced prefix; operationally it's the AS-edge / peering interface (often on an IXP 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:

• SRB host (SOX, Belgrade): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
• DE host (Berlin): Type 2 NOT honored. Forged PTB had no effect (filtered en route or stack ignored it). (ICMPv6 Echo + forged PTB)
• DE host (Düsseldorf): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)
• 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): Type 2 honored. Forged PTB accepted; next response shrunk. (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)
• SLO host (T-2): Type 2 honored. Forged PTB accepted; next response shrunk. (ICMPv6 Echo + forged PTB)

Why they disagree - path-asymmetric Type 2 filtering: Both vantages used the ICMPv6 Echo + forged-PTB method on the same destination IP, but reached different verdicts. The destination's stack is the same in both cases - so the difference is in the path: a transit AS on one route filters our forged Type 2 (or its return ICMPv6 carrying the embedded packet) while the other route delivers it intact. The vantage that says honored shows what the destination's stack actually does; the one that says not honored shows that the path between us and them drops Type 2.

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 2a01:261:313:b814:2a0:98ff:fe5b:13e4 or src host 2a06:d1c1:10b::cccc or src host 2a06:d1c1:10d::aaaa or src host 2a09:ab81::91 or src host 2a12:d8c0:105a:9001::a154)'

sudo ip6tables -L INPUT -nv | grep -iE 'icmpv6|packet-too-big'
sudo nft list ruleset 2>/dev/null | grep -A1 'icmpv6'

sudo sysctl net.ipv6.conf.all.accept_redirects net.ipv4.ip_no_pmtu_disc net.ipv6.route.mtu_expires

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 or src host 2a09:ab81::91 or src host 2a01:261:313:b814:2a0:98ff:fe5b:13e4 or src host 2a06:d1c1:10a::bbbb or src host 2a06:d1c1:10d::aaaa or src host 2a06:d1c1:10b::cccc)'

Multi-vantage path map

Every hop of all vantages’ traceroutes toward the target, drawn left→right, grouped into per-AS bubbles (a hop seen from several vantages is one shared bubble, so converging paths merge). It answers two questions per vantage — shown on each source bubble as echo ✓/⚠/✗ · trace ✓/✗: did the destination reply to ICMPv6 Echo (✓ honored, ⚠ replied but PTB not honored, ✗ no reply), and did the traceroute reach it. A line to the target is drawn only when that vantage got an echo reply — solid if the PTB was honored, dashed if not (reachable but a broken-PMTUD / RFC 4890 violation). The path depth still shows how far the traceroute itself got, and runs of unanswered (* *) hops collapse into one dashed “silent” bubble. Open full size ↗

• ● SRB host (SOX, Belgrade)
• ● DE host (Berlin)
• ● DE host (Düsseldorf)
• ● NL host (go6lab)
• ● ITA host (Karsolink)
• ● SLO host (6connect)
• ● SLO host (T-2)
• ── solid line = echo reply, PTB honored (clean reach)
• — — dashed line = echo reply but PTB not honored (RFC 4890 violation)
• no line = no echo reply (never reached)
• ◉ target: green = clean, amber = reachable-but-violation / unreachable
• ⚠ suspected drop AS
• ⋯ silent (unanswered) hops
• ● IXP hop

From SRB host (SOX, Belgrade)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

tracepath -6

 1?: [LOCALHOST]                        0.010ms pmtu 1500
 1:  _gateway                                              0.572ms 
 1:  _gateway                                              0.529ms 
 2:  2001:7f8:1e::4                                        0.875ms 
 3:  et-2-0-5-1337.bbr01.anx03.vie.at.anexia-it.net       14.086ms 
 4:  2a00:11c0:47:1:47::135                               13.327ms 
 5:  2a00:11c0:47:1:47::129                               11.724ms asymm  6 
 6:  2a00:11c0:47:3::10d                                  21.627ms asymm  8 
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

From DE host (Berlin)   openRFC 4890 ✗

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

Rate-limited ICMPv6: hop 7 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.013ms pmtu 1500
 1:  xe-0-0-13-178.gw01.ber01.as59645.net                  0.347ms 
 1:  xe-0-0-13-178.gw01.ber01.as59645.net                  0.301ms 
 2:  ae0-2453.cr10.ber01.lwlcom.net                        0.940ms 
 3:  retn.bcix.de                                         10.701ms asymm  5 
 4:  RT.ESH.FKT.DE.retn.net                               11.054ms asymm  5 
 5:  GW-AS47147.retn.net                                  11.172ms asymm  4 
 6:  2a00:11c0:47:1:47::146                               22.544ms asymm  5 
 7:  2a00:11c0:47:1:47::151                               27.578ms asymm 10 
 8:  2a00:11c0:47:1:47::129                               22.224ms 
 9:  2a00:11c0:47:3::10d                                  29.790ms 
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

From DE host (Düsseldorf)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

tracepath -6

 1?: [LOCALHOST]                        0.022ms pmtu 1500
 1:  xe-0-0-12-142.gw01.dus01.as59645.net                  0.361ms 
 1:  xe-0-0-12-142.gw01.dus01.as59645.net                  0.327ms 
 2:  eth1-0-12-h5594.edge5-dus1.bb.wiit.network            1.279ms 
 3:  no reply
 4:  lag30.core3-dus1.bb.wiit.network                      0.594ms 
 5:  lag2.core1-dus-ix.bb.wiit.network                     0.618ms 
 6:  ae3-1337.bbr02.anx25.fra.de.anexia-it.net             4.288ms 
 7:  2a00:11c0:47:1:47::148                                4.915ms asymm  3 
 8:  2a00:11c0:47:1:47::146                                4.832ms asymm  4 
 9:  2a00:11c0:47:1:47::136                               15.600ms asymm  7 
10:  2a00:11c0:47:1:47::129                               15.515ms asymm  7 
11:  2a00:11c0:47:3::10d                                  23.939ms asymm  8 
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

From NL host (go6lab)   openRFC 4890 ✗

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

Rate-limited ICMPv6: hop 9 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.034ms pmtu 1500
 1:  2a00:8642:42::2                                       1.781ms 
 1:  2a00:8642:42::2                                       1.372ms 
 2:  no reply
 3:  ccr2-ccr1.dc1.nogalliance.org                         2.992ms asymm  2 
 4:  ae3-1337.bbr02.anx63.ams.nl.anexia-it.net             6.482ms asymm  5 
 5:  2a00:11c0:47:1:47::213                               27.024ms asymm 10 
 6:  2a00:11c0:47:1:47::136                               30.628ms asymm 11 
 7:  2a00:11c0:47:1:47::130                               30.015ms asymm 11 
 8:  2a00:11c0:47:3::10d                                  38.205ms asymm 12 
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

From ITA host (Karsolink)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

Rate-limited ICMPv6: hop 5 (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:  no reply
 3:  2a12:d8c0:109f:106::a2                                3.731ms 
 4:  ae0-303.RT.VSX.PDA.IT.retn.net                        4.166ms 
 5:  RT.ESH.FKT.DE.retn.net                               16.805ms 
 6:  2a02:2d8:0:a014:232a::1                              21.057ms asymm 10 
 7:  2a00:11c0:47:1:47::143                               45.463ms asymm  8 
 8:  2a00:11c0:47:3::10d                                  20.826ms asymm 11 
 9:  2a00:11c0:47:1:47::151                               96.793ms asymm 10 
10:  2a00:11c0:47:1:47::129                               31.093ms asymm  8 
11:  2a00:11c0:47:3::10d                                  30.222ms 
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

From SLO host (6connect)   openRFC 4890 ✗

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

Rate-limited ICMPv6: hop 3, hop 11 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.017ms pmtu 9000
 1:  fw1-lju.6connect.com                                  0.474ms 
 1:  fw1-lju.6connect.com                                  0.558ms 
 2:  ccr-to-fw-ccr1-gw-lju.6connect.com                    0.785ms 
 3:  no reply
 4:  2a00:ee0:1:15::2                                      1.533ms asymm  3 
 5:  2a00:ee0:1:10::2                                     11.790ms pmtu 1500
 5:  ae3-1337.bbr02.anx25.fra.de.anexia-it.net            12.478ms asymm  7 
 6:  2a00:11c0:47:1:47::140                               17.486ms asymm 11 
 7:  2a00:11c0:47:1:47::145                               15.031ms asymm 11 
 8:  2a00:11c0:47:1:47::151                               25.939ms asymm 12 
 9:  2a00:11c0:47:1:47::129                               31.337ms asymm 12 
10:  2a00:11c0:47:3::10d                                  23.885ms 
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500

From SLO host (T-2)   openRFC 4890 ✓

filter likely at: (none) · min PMTU on path: 1500

Path (traceroute + mtr + PTR)

tracepath -6

 1?: [LOCALHOST]                        0.028ms pmtu 1500
 1:  no reply
 2:  2a01:260:1::225                                       2.562ms 
 3:  2a01-260-1-1--9c.core6.t-2.net                        2.592ms 
 4:  2a01-260-1-1--38.core6.t-2.net                        3.033ms asymm  3 
 5:  et-2-0-5-1337.bbr01.anx03.vie.at.anexia-it.net       12.188ms 
 6:  et-2-0-5-1337.bbr01.anx03.vie.at.anexia-it.net       11.862ms asymm  5 
 7:  2a00:11c0:47:1:47::135                                9.601ms asymm  6 
 8:  2a00:11c0:47:1:47::130                               12.865ms asymm  6 
 9:  2a00:11c0:47:3::10d                                  19.106ms asymm  7 
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500