3 ms·

>This documents how I added IPv6 to my home network, which runs OpenBSD, using OpenBSD's ifconfig, slaacd, dhcp6leased, rad, and unbound. This should serve as a

>This documents how I added IPv6 to my home network, which runs OpenBSD, using OpenBSD's ifconfig, slaacd, dhcp6leased, rad, and unbound. This should serve as a guide to other people in the same situation, but be aware you need to be running at least OpenBSD 7.6, as that is the version that added support for dhcp6leased and updated rad to handle DHCPv6 PD (prefix delegation). For older OpenBSD versions, you'll have to use ports, and there are multiple guides for that, use your friendly neighborhood search engine." The author forgot Step 1. Ensure your ISP provides IPV6 services. Otherwise, good documentation for the record.

alrs 2y ago
Who cares if the ISP supports ipv6? Figuring out a world without DHCP and subnetting on a LAN is the hard part.
IntelMiner 2y ago
Shout out to my old ISP CenturyLink who participated in world IPv6 day in 2011 ...Then decided that NAT64 was "good enough" for people who wanted IPv6 instead of just doing fucking dual-stack
- yjftsjthsd-h 2y ago
  NAT64 is a way for v6-only hosts to reach v4 hosts. I don't understand how that would apply here?
  - jesprenj 2y ago
    I guess one could choose between v4 or v6 but not both at the same time (dual stack). My mobile ISP also does it this way -- you either use IPv4 only on mobile data or IPv6 only with NAT64 and DNS64 to reach v4 hosts.
    - zeroflow 2y ago
      It's frustrating trying to work with ISPs. While there surely are business services available, as a normal customer, you're out of luck. I count myself lucky, since I can at least get a public (dynamic) IPv4 address. The other option is DSLite with a single /64 via DHCP6. Well, I can't use that. So yeah, while it would be a fun journey trying out IPv6 - it's not feasable for me. And most likely, that holds true for others aswell. There are options available - like the HE tunnelbroker - but those come with their own set of drawbacks.
LargoLasskhyfv 2y ago
Step 1 does not apply because of https://tunnelbroker.net/ https://tunnelbroker.net/ & https://dns.he.net/ https://dns.he.net/ amongst several other options.

alrs 2y ago

Who cares if the ISP supports ipv6? Figuring out a world without DHCP and subnetting on a LAN is the hard part.

IntelMiner 2y ago

Shout out to my old ISP CenturyLink who participated in world IPv6 day in 2011 ...Then decided that NAT64 was "good enough" for people who wanted IPv6 instead of just doing fucking dual-stack

yjftsjthsd-h 2y ago
NAT64 is a way for v6-only hosts to reach v4 hosts. I don't understand how that would apply here?
- jesprenj 2y ago
  I guess one could choose between v4 or v6 but not both at the same time (dual stack). My mobile ISP also does it this way -- you either use IPv4 only on mobile data or IPv6 only with NAT64 and DNS64 to reach v4 hosts.
  - zeroflow 2y ago
    It's frustrating trying to work with ISPs. While there surely are business services available, as a normal customer, you're out of luck. I count myself lucky, since I can at least get a public (dynamic) IPv4 address. The other option is DSLite with a single /64 via DHCP6. Well, I can't use that. So yeah, while it would be a fun journey trying out IPv6 - it's not feasable for me. And most likely, that holds true for others aswell. There are options available - like the HE tunnelbroker - but those come with their own set of drawbacks.

LargoLasskhyfv 2y ago

Step 1 does not apply because of https://tunnelbroker.net/ https://tunnelbroker.net/ & https://dns.he.net/ https://dns.he.net/ amongst several other options.