I **really** need to learn #ipv6 better. At the house, I have a Verizon business line (not their residential service). I've got dedicated ipv4 addresses. I also have an ipv6 range that gets mapped by them.
The same line runs my ISP stuff and I'm trying to do a bit of segmentation. At first I thought I'd get a hurricane electric range, because it would be stable. I could count on it. Silly me, I went and got 3 HE ranges assigned to 3 different segments. That's dumb and the router doesn't like it.
I'm winding down the HE tunnels. That doesn't seem to be very effective. But I'm not sure (a) how to configure my #mikrotik to pick up whatever v6 range my ISP is sending, and (b) partition it into a couple predictable ranges. I think they delegate a /64. and then (c) assign those ranges to certain sets of systems. (They're already segregated on IPv4 /24s)
I also don't know how stable the Verizon assignment is. I'm nervous about possibly publishing AAAA records for stuff only to find that VZ delegates a new prefix one day and all that stops working.
I really want to learn, but there's so much randomness introduced by ISPs who don't document how stuff works.
Paco Hope
npub18m…edgg0
2026-08-21 12:38:07 UTC
Author Public Key
npub18mdv65n7xqd0dhu0895tw6xkkxmhereksgqs60087ng855cmeqkqmedgg0Published at
2026-08-21 12:38:07 UTCEvent JSON
{
"id": "4bdb356d90b9b930adc399a8d6ab1b8d5c3647b5a6aeb608b71b3813a5a24adc",
"pubkey": "3edacd527e301af6df8f3968b768d6b1b77c8f3682010d3de7f4d07a531bc82c",
"created_at": 1787315887,
"kind": 1,
"tags": [
[
"t",
"mikrotik"
],
[
"t",
"ipv6"
],
[
"proxy",
"https://infosec.exchange/@paco/117133533987332283",
"web"
],
[
"proxy",
"https://infosec.exchange/users/paco/statuses/117133533987332283",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/paco/statuses/117133533987332283",
"pink.momostr"
],
[
"-"
]
],
"content": "I **really** need to learn #ipv6 better. At the house, I have a Verizon business line (not their residential service). I've got dedicated ipv4 addresses. I also have an ipv6 range that gets mapped by them.\n\nThe same line runs my ISP stuff and I'm trying to do a bit of segmentation. At first I thought I'd get a hurricane electric range, because it would be stable. I could count on it. Silly me, I went and got 3 HE ranges assigned to 3 different segments. That's dumb and the router doesn't like it.\n\nI'm winding down the HE tunnels. That doesn't seem to be very effective. But I'm not sure (a) how to configure my #mikrotik to pick up whatever v6 range my ISP is sending, and (b) partition it into a couple predictable ranges. I think they delegate a /64. and then (c) assign those ranges to certain sets of systems. (They're already segregated on IPv4 /24s)\n\nI also don't know how stable the Verizon assignment is. I'm nervous about possibly publishing AAAA records for stuff only to find that VZ delegates a new prefix one day and all that stops working.\n\nI really want to learn, but there's so much randomness introduced by ISPs who don't document how stuff works.",
"sig": "c8c8b3453f1dc6278bb0980d77b51879cf89c767e13bd947403ee3aa66a0a3d65c4fa0a83afef5b480353e4e3c3b9cbb164a6dfd14bd94ef51414285e495d2ca"
}