My router advertises its MTU over ICMPv6 router advertisements. It's
somewhat large (9216), and exceeds the hardware capabilities of my
OpenBSD system's rge interface (9194). This results in a bunch of
noisy log messages of:
> slaacd[...]: failed to set MTU: Invalid argument
And the obvious outcome where slaacd doesn't actually adjust the MTU
to something larger.
I thought I'd be helpful and make a patch where slaacd clamps to the
maximum hardware capability before attempting to set the MTU. However,
I got blocked by pledge: There currently is no pledge that gives
access to SIOCGIFHARDMTU.
So, some questions arise:
1. Does it make sense to add SIOCGIFHARDMTU (and maybe SIOCGIFMTU too)
to pledge("route")?
2. Should slaacd clamp at all or or have some additional settings for
MTU control?
-Stefan
