3 ms·

On my routers, this is the first release I have not needed to run 3rd party software for core functionality. dhcp6leased is now included to handle IPv6-PD, and

by matrix2003 2y ago

On my routers, this is the first release I have not needed to run 3rd party software for core functionality. dhcp6leased is now included to handle IPv6-PD, and if your ISP supports SLAAC, slaacd is included as well for your WAN interface. I still have my fingers crossed for DHCPv6 normal address delegation, but it's a great step!

kstrauser 2y ago
For the sake of discussing it here: why would you need a SLAAC daemon? Edit: My question wasn't so much why you'd want SLAAC as why you'd need a daemon for it. From https://www.openbsd.org/papers/florian_slaacd_bsdcan2018.pdf https://www.openbsd.org/papers/florian_slaacd_bsdcan2018.pdf: > Remove sending of router solicitations and processing of router advertisements from the kernel. Oh, got it. That totally makes sense in an OpenBSD way.
- ectospheno 2y ago
  It can be one. Perhaps you don’t want it.
  - kstrauser 2y ago
    Never said otherwise. I wasn't aware of a need for such a thing before just now and wondered why that would be a nice thing to have. I could go off and RTFM, but then we wouldn't get to talk about it.
    - matrix2003 2y ago
      SLAAC is basically an IPv6 alternative to how DHCP works. With IPv6, you can either use DHCPv6 (ISPs deliver Prefix Delegations and Normal Addresses this way) or SLAAC (How one typically gets an IPv6 address on a LAN or route from a Link-Local address on an ISP). Hopefully that's clear as mud ;) I would encourage you to go check out IPv6 if that was the intent of your original question. It actually makes more sense after you dive in, and can be pretty neat. ULAs (Unique Local Address) are one often-overlooked part of which I'm an advocate.
      - kstrauser 2y ago
        I just replied to myself with an edit to the higher level comment. Sure, I use IPv6 with SLAAC. I'd never needed a separate daemon to handle it, though. I hadn't imagined that OpenBSD would pull that out into its own program, but I'm not at all surprised now that I've heard about it.
        matrix2003 2y ago
        ah - gotcha! Yep. OpenBSD is big on the least-privilege principle, Which IMO is why it's pulled out into a separate daemon that only has the permissions and visibility to do what it needs.
        kstrauser 2y ago
        Yeah, that seems like a very OpenBSD thing to do, and I mean that positively. It just initially struck me, like, "yay, I no longer have to install a ping daemon!" "A what daemon?"
    - ectospheno 2y ago
      I should have included more text I guess. I was providing two answers to why it was one: 1. It can be one so it probably should be. 2. This lets you not run it.
- matrix2003 2y ago
  At least for my ISP, SLAAC installs a default route and uses link-local addresses to route traffic (I actually didn't know this would work until I tried with OpenBSD 7.6). This allows the PD LAN subnet to be routed out to the internet. YMMV! edit: I may be slightly misunderstanding, and it might not be needed. Regardless, my router can now ping internet addresses while running slaacd.

kstrauser 2y ago

For the sake of discussing it here: why would you need a SLAAC daemon? Edit: My question wasn't so much why you'd want SLAAC as why you'd need a daemon for it. From https://www.openbsd.org/papers/florian_slaacd_bsdcan2018.pdf https://www.openbsd.org/papers/florian_slaacd_bsdcan2018.pdf: > Remove sending of router solicitations and processing of router advertisements from the kernel. Oh, got it. That totally makes sense in an OpenBSD way.

ectospheno 2y ago
It can be one. Perhaps you don’t want it.
- kstrauser 2y ago
  Never said otherwise. I wasn't aware of a need for such a thing before just now and wondered why that would be a nice thing to have. I could go off and RTFM, but then we wouldn't get to talk about it.
  - matrix2003 2y ago
    SLAAC is basically an IPv6 alternative to how DHCP works. With IPv6, you can either use DHCPv6 (ISPs deliver Prefix Delegations and Normal Addresses this way) or SLAAC (How one typically gets an IPv6 address on a LAN or route from a Link-Local address on an ISP). Hopefully that's clear as mud ;) I would encourage you to go check out IPv6 if that was the intent of your original question. It actually makes more sense after you dive in, and can be pretty neat. ULAs (Unique Local Address) are one often-overlooked part of which I'm an advocate.
    - kstrauser 2y ago
      I just replied to myself with an edit to the higher level comment. Sure, I use IPv6 with SLAAC. I'd never needed a separate daemon to handle it, though. I hadn't imagined that OpenBSD would pull that out into its own program, but I'm not at all surprised now that I've heard about it.
      - matrix2003 2y ago
        ah - gotcha! Yep. OpenBSD is big on the least-privilege principle, Which IMO is why it's pulled out into a separate daemon that only has the permissions and visibility to do what it needs.
        kstrauser 2y ago
        Yeah, that seems like a very OpenBSD thing to do, and I mean that positively. It just initially struck me, like, "yay, I no longer have to install a ping daemon!" "A what daemon?"
  - ectospheno 2y ago
    I should have included more text I guess. I was providing two answers to why it was one: 1. It can be one so it probably should be. 2. This lets you not run it.
matrix2003 2y ago
At least for my ISP, SLAAC installs a default route and uses link-local addresses to route traffic (I actually didn't know this would work until I tried with OpenBSD 7.6). This allows the PD LAN subnet to be routed out to the internet. YMMV! edit: I may be slightly misunderstanding, and it might not be needed. Regardless, my router can now ping internet addresses while running slaacd.