batadv_interface_change_mtu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… batadv_interface_change_mtu(9) β€” like, the kernel API manual, bestie

okay so real talk, this is a page from the Kernel API Manual and it's about batadv_interface_change_mtu β€” the function that handles changing the MTU of a mesh interface πŸ¦‹ no cap, that's the whole vibe.


✨ NAME ✨

batadv_interface_change_mtu β€” change the MTU of a mesh interface πŸŽ€


🌸 SYNOPSIS 🌸

int batadv_interface_change_mtu (struct net_device *dev , int new_mtu );

πŸ’– ARGUMENTS πŸ’–

  • dev β€” the mesh interface you're modifying 🫢 like, this is the thing getting its MTU changed
  • new_mtu β€” the brand new MTU value you're asking for ✨ literally the number you want

πŸ‘‘ DESCRIPTION πŸ‘‘

So what it actually does: it validates that new_mtu fits inside the range that the configured hard interfaces actually support πŸ”₯ then it remembers it as the user-configured MTU πŸ’Ύ periodt.

That's it β€” vibe check the number, then stash it. Simple. Iconic.


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • -EINVAL if new_mtu is out of range πŸ’€ (out of range = rejected, no cap)

🌈 SEE ALSO 🌈

Kernel file ./net/batman-adv/mesh-interface.c plus this whole squad of friends:


and that's the whole page, bestie πŸ§šπŸ’œ shoutout to ./net/batman-adv for keeping it real β€” dropped October 2026, filed under batadv_interface_change_mtu(9) πŸ“ go read it again iykyk πŸ’…

πŸ“¦ where this page comes from