đ
Original date posted:2012-06-26
đ Original message:> Additionally, such addresses are exchanged and relayed via the P2P network.
> To do so, we reused the fd87:d87e:eb43::/48 IPv6 range. Each address in this
> 80-bit range is mapped to an onion address, and treated as belonging to a
> separate network. This network range is the same as used by the OnionCat
> application (though we do not use OnionCat in any way), and is part of the
> RFC4193 Unique Local IPv6 range, which is normally not globally routable.
>
> Other clients that wish to implement similar functionality, can use this
> test case: 5wyqrzbvrdsumnok.onion == FD87:D87E:EB43:edb1:8e4:3588:e546:35ca.
> The conversion is simply decoding the base32 onion address, and storing the
> resulting 80 bits of data as low-order bits of an IPv6 address, prefixed by
> fd87:d87e:eb43:. As this range is not routable, there should be no
> compatibility problems: any unaware IPv6-capable code will immediately fail
> when trying to connect.
You are going to want to include the block of the Phatom project as well:
https://code.google.com/p/phantom/
fd00:2522:3493::/48
And the one for 'garlicat' for I2P, which might be more complex due
to I2P's addressing:
fd60:db4d:ddb5::/48
Note that while these blocks are not expected to be routable, that
people may in fact have interfaces, routing tables and packet filters
on their machines configured with up to all three of those networks
for the purposes therein.
grarpamp [ARCHIVE] /
npub1rjâŚvs23t
2023-06-07 10:19:21
in reply to nevent1qâŚ26wp
Author Public Key
npub1rjzq78n467z9ugxvfq6cyxdk8n3rtn8h92yjnrtene4a52g847rsgvs23tSeen on
wss://relay.noswhere.comPublished at
2023-06-07 10:19:21Event JSON
{
"id": "ff3cc51df8afd227af3133e1a28395e16d95de11cc64fe3ecf0611b3584a6fa6",
"pubkey": "1c840f1e75d7845e20cc48358219b63ce235ccf72a89298d799e6bda2907af87",
"created_at": 1686133161,
"kind": 1,
"tags": [
[
"e",
"8673be66f7fc6071bb567ee4601ef1d16e1703ad776437d0d1dc54fe0c26aea1",
"",
"root"
],
[
"e",
"da4e56e63adee131dd2a6bd7cbbdb1d3a730c566f8d951d6424c6336441fb9bb",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "đ
Original date posted:2012-06-26\nđ Original message:\u003e Additionally, such addresses are exchanged and relayed via the P2P network.\n\u003e To do so, we reused the fd87:d87e:eb43::/48 IPv6 range. Each address in this\n\u003e 80-bit range is mapped to an onion address, and treated as belonging to a\n\u003e separate network. This network range is the same as used by the OnionCat\n\u003e application (though we do not use OnionCat in any way), and is part of the\n\u003e RFC4193 Unique Local IPv6 range, which is normally not globally routable.\n\u003e\n\u003e Other clients that wish to implement similar functionality, can use this\n\u003e test case: 5wyqrzbvrdsumnok.onion == FD87:D87E:EB43:edb1:8e4:3588:e546:35ca.\n\u003e The conversion is simply decoding the base32 onion address, and storing the\n\u003e resulting 80 bits of data as low-order bits of an IPv6 address, prefixed by\n\u003e fd87:d87e:eb43:. As this range is not routable, there should be no\n\u003e compatibility problems: any unaware IPv6-capable code will immediately fail\n\u003e when trying to connect.\n\nYou are going to want to include the block of the Phatom project as well:\nhttps://code.google.com/p/phantom/\nfd00:2522:3493::/48\n\nAnd the one for 'garlicat' for I2P, which might be more complex due\nto I2P's addressing:\nfd60:db4d:ddb5::/48\n\nNote that while these blocks are not expected to be routable, that\npeople may in fact have interfaces, routing tables and packet filters\non their machines configured with up to all three of those networks\nfor the purposes therein.",
"sig": "09e70469fd47e850906dd302605f99667b1dd77b8dc9f8ef50edcc42ad85a49cb06d4e63884bf01907f9c1c485e1133e0ff89b93e0aeae3eb66b6a1e454239b6"
}