kasperd on Nostr: That hostname resolves to `2a05:87c6:1:1cc8::1` for me. I confirmed that the IP ...
That hostname resolves to `2a05:87c6:1:1cc8::1` for me. I confirmed that the IP address is reachable from most networks I tried but it is not reachable from
Mythic Beasts (npub1wy5…64vc) or
Andrews & Arnold Ltd (AAISP) (npub1sv0…rq9x)The problem seems to affect both ssh and ping. With both protocols I get an ICMPv6 error message back:
```
ICMP6, destination unreachable, unreachable address 2a05:87c6:1:1cc8::1, length 88
```
The origin of the ICMPv6 error message is 2001:8b0:0:53::109 or 2a00:1098:2::7 depending on which provider I connect from.
Here is an example traceroute output:
```
root@nat64-london:~# traceroute -n -I 2a05:87c6:1:1cc8::1
traceroute to 2a05:87c6:1:1cc8::1 (2a05:87c6:1:1cc8::1), 30 hops max, 80 byte packets
1 2a00:1098:1::2d 0.284 ms 0.231 ms 0.217 ms
2 2a00:1098:2:ffff::9c 0.401 ms 0.387 ms 0.375 ms
3 2a00:1098:2:1::1c:1 0.437 ms 0.417 ms 0.453 ms
4 2a00:1098:2::7 0.323 ms 0.376 ms 0.365 ms
5 2a00:1098:2::7 3055.197 ms !H 3055.184 ms !H 3055.165 ms !H
root@nat64-london:~#
```
The last hop limit exceeded message came from the same IP as the unreachable address. The later error message was delayed by 3 seconds.
In my experience the 3 second delay is most often caused by a neighbor discovery timeout. That indicates that 2a00:1098:2::7 and 2001:8b0:0:53::109 have a route forward towards the destination, but the next hop is not responding to neighbor solicitation messages.
Published at
2024-08-25 10:05:54Event JSON
{
"id": "861c2741776f5c59295d553869c9d3d7642d86a000b8587b76e807349f96ebe0",
"pubkey": "95c284f154245f88dca618fe6b8ee8cfb5a2de26706f2814b3ef2b6d6b0b84c8",
"created_at": 1724580354,
"kind": 1,
"tags": [
[
"p",
"831f088c53bea5a2faa06f0123cc9c1d30b816c1c4b1dbf0100a2cff8f612bb6"
],
[
"p",
"712913b00ac899746988cf9496deb3992caff8f7cc36a78527aaf319ab4f24d0"
],
[
"p",
"da50c965cdff34b1c8bd03920adf447dd35fadbeb8c1b63b53da77e5284e43dc"
],
[
"e",
"fb89bd49960662422b8344475955a739973aae46574cd09ab776cde7840a7ede",
"",
"root",
"da50c965cdff34b1c8bd03920adf447dd35fadbeb8c1b63b53da77e5284e43dc"
],
[
"proxy",
"https://westergaard.social/objects/5ea58e3a-51ed-4312-b976-1d133a1cc390",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://westergaard.social/objects/5ea58e3a-51ed-4312-b976-1d133a1cc390",
"pink.momostr"
],
[
"-"
]
],
"content": "That hostname resolves to `2a05:87c6:1:1cc8::1` for me. I confirmed that the IP address is reachable from most networks I tried but it is not reachable from nostr:npub1wy538vq2ezvhg6vge72fdh4nnyk2l78hesm20pf84te3n260yngqud64vc or nostr:npub1sv0s3rznh6j6974qduqj8nyur5cts9kpcjcahuqspgk0lrmp9wmqnfrq9x\n\nThe problem seems to affect both ssh and ping. With both protocols I get an ICMPv6 error message back:\n```\nICMP6, destination unreachable, unreachable address 2a05:87c6:1:1cc8::1, length 88\n```\n\nThe origin of the ICMPv6 error message is 2001:8b0:0:53::109 or 2a00:1098:2::7 depending on which provider I connect from.\n\nHere is an example traceroute output:\n```\nroot@nat64-london:~# traceroute -n -I 2a05:87c6:1:1cc8::1\ntraceroute to 2a05:87c6:1:1cc8::1 (2a05:87c6:1:1cc8::1), 30 hops max, 80 byte packets\n 1 2a00:1098:1::2d 0.284 ms 0.231 ms 0.217 ms\n 2 2a00:1098:2:ffff::9c 0.401 ms 0.387 ms 0.375 ms\n 3 2a00:1098:2:1::1c:1 0.437 ms 0.417 ms 0.453 ms\n 4 2a00:1098:2::7 0.323 ms 0.376 ms 0.365 ms\n 5 2a00:1098:2::7 3055.197 ms !H 3055.184 ms !H 3055.165 ms !H\nroot@nat64-london:~# \n```\n\nThe last hop limit exceeded message came from the same IP as the unreachable address. The later error message was delayed by 3 seconds.\n\nIn my experience the 3 second delay is most often caused by a neighbor discovery timeout. That indicates that 2a00:1098:2::7 and 2001:8b0:0:53::109 have a route forward towards the destination, but the next hop is not responding to neighbor solicitation messages.",
"sig": "14ec2f4221cce7ec1c250faba34c8f0869db889b53586fb6c83b6a66281533e2e623f631545e6f3fc56f9be6bae6ce02f6f953e9c0c78b0bc6d33991570e32b6"
}