Page MenuHomeFreeBSD

netinet6: allow binding to anycast addresses
ClosedPublic

Authored by ivy on Apr 19 2025, 4:42 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 2, 7:43 PM
Unknown Object (File)
Sep 8 2025, 3:31 AM
Unknown Object (File)
Sep 5 2025, 5:33 AM
Unknown Object (File)
Sep 3 2025, 4:09 PM
Unknown Object (File)
Aug 31 2025, 11:46 PM
Unknown Object (File)
Aug 28 2025, 12:10 AM
Unknown Object (File)
Aug 24 2025, 6:17 AM
Unknown Object (File)
Aug 23 2025, 5:43 PM

Details

Summary

the restriction on sending packets from anycast source addresses was
removed in RFC4291, so there's no reason to forbid binding to such
addresses. this allows anycast services (e.g., DNS) to actually use
anycast addresses, which was previously impossible.

RFC4291 also removes the restriction that only routers may configure
anycast addresses; this was never enforced in code but was documented in
ifconfig.8. update ifconfig.8 to document both changes.

PR: 285545

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ivy requested review of this revision.Apr 19 2025, 4:42 AM
des requested changes to this revision.Apr 19 2025, 10:12 AM
des added inline comments.
sbin/ifconfig/ifconfig.8
31

it's nbd if you don't but try to remember to bump before pushing

452

We should probably add RFC 4291 (and RFC 3484 which is mentioned elsewhere in the page) to the “SEE ALSO” section. See tcp(4) or protocols(5) for examples of how to format the references.

456

overly verbose, “explicitly binds [a socket] to the address” is enough

This revision now requires changes to proceed.Apr 19 2025, 10:12 AM

fixes for ifconfig.8 review comments:

  • be less verbose
  • add RFCs to see also
  • bump Dd
ivy marked 3 inline comments as done.Apr 20 2025, 6:36 PM
This revision is now accepted and ready to land.Apr 21 2025, 5:34 PM
This revision was automatically updated to reflect the committed changes.