AS198524 - iLOLPIRFC 4890 ✓RPKI ✓ 1/1ASPA ✓

AS overview

Test target: 2001:67c:2730:2::3 · ns2.ilol.si · address space: PI · prefixes announced: 1

prefix(es): 2001:67c:2730::/48

SIX peering

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

At least one router inside AS198524's announced prefix replied during the random-target probe. Hop(s): 2001:67c:2730:f9::1, 2001:67c:2730:f9::2, 2001:67c:2730:fb::2. These are candidate targets for direct testing.

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): inconclusive: no Echo Reply to 1300-byte probe. (ICMPv6 Echo + forged PTB)
• ITA host (Karsolink): Type 2 partial. Some shrinkage but not down to 1280 bytes. (TLS handshake + forged PTB)
• SLO host (6connect): Type 2 partial. Some shrinkage but not down to 1280 bytes. (TLS handshake + forged PTB)

Why they disagree - different probe methods: These vantages picked different probe methods, so their verdicts are not directly comparable. The active test tries methods in order (icmp6-echo → dns-tcp → tls → http) and stops at the first that produces a definitive verdict; if the chosen method differs, the underlying evidence differs too. Most often this is because the path PMTU on one vantage is below 1500 B, so the natural Echo Reply is already fragmented and the icmp6-echo method falls through to a TCP-based one. This is largely a measurement artifact, not a destination-behaviour difference.

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)'

From NL host (go6lab)   openRFC 4890 ✓

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

Path (traceroute + mtr + PTR)

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

tracepath -6

 1?: [LOCALHOST]                        0.037ms pmtu 1500
 1:  2a00:8642:42::3                                       2.112ms 
 1:  2a00:8642:42::3                                       3.460ms 
 2:  no reply
 3:  no reply
 4:  be1.core3.ams1.he.net                                 6.189ms 
 5:  be2.core4.fra1.he.net                                10.566ms 
 6:  be3.core2.fra2.he.net                                11.882ms 
 7:  100ge0-0-0-3.core1.vie1.he.net                       23.194ms 
 8:  100ge0-0-0-23.core1.vie1.he.net                      23.653ms asymm  7 
 9:  2001:7f8:46::19:8524                                 25.776ms 
10:  2001:7f8:46::19:8524                                 25.782ms asymm  9 
11:  2001:67c:2730:ff::ff                                 26.385ms 
12:  2001:67c:2730:ff::ff                                 25.573ms asymm 11 
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  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)

tracepath -6

 1?: [LOCALHOST]                        0.032ms pmtu 1500
 1:  no reply
 2:  2a12:d8c0:109f:121::a1                                0.870ms 
 3:  2a12:d8c0:101f:6::1                                  10.298ms 
 4:  no reply
 5:  e0-35.core1.zag2.he.net                              19.523ms 
 6:  no reply
 7:  e0-35.core1.lju1.he.net                              22.549ms 
 8:  2001:7f8:46::19:8524                                 21.122ms 
 9:  2001:67c:2730:fa::2                                  21.900ms 
10:  2001:67c:2730:ff::ff                                 21.995ms 
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  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 7 (loss between 5% and 95% across mtr cycles - the router replies but only sometimes).

tracepath -6

 1?: [LOCALHOST]                        0.014ms pmtu 1500
 1:  fw1-lju.6connect.com                                  0.493ms 
 1:  fw1-lju.6connect.com                                  0.464ms 
 2:  no reply
 3:  no reply
 4:  2001:7f8:46::19:8524                                  1.610ms 
 5:  2001:67c:2730:fa::2                                   1.293ms 
 6:  2001:67c:2730:ff::ff                                  1.849ms 
 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
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500