IFCFG-IPVLAN(5)

πŸ“¦ version 0.6.80, in opensuse-leap 16.0

πŸ’… ifcfg-ipvlan(5) β€” the glow-up edition ✨

okay bestie, so this is a page from the Wicked User Manual, and it's all about ifcfg-ipvlan, like, the IPVLAN interface configuration situation. buckle up πŸŽ€


🌸 NAME 🌸

ifcfg-ipvlan β€” IPVLAN interface configuration. that's it, that's the name, she's iconic πŸ‘‘


✨ SYNOPSIS ✨

/etc/sysconfig/network/ifcfg-*

literally just the config files in that directory, that's the whole vibe check πŸ’–


πŸ¦‹ IPVLAN interface πŸ¦‹

okay so to set up an IPVLAN interface, you need a configuration file with the IPVLAN=yes variable set. like, that's non-negotiable bestie, it's the whole personality πŸ’…

an IPVLAN interface is conceptually similar to MACVLAN β€” think of them as sisters, but very different sisters. here's the comparison, and yes i'm keeping every detail πŸ‘‡

  • MACVLAN operates at Layer 2 and assigns a unique MAC address to each MACVLAN. πŸŽ€
    • Management support on most (L3+) managed switches
    • Common DHCP support
  • IPVLAN operates at Layer 3 and shares the MAC address with the underlying interface. πŸ¦‹
    • Supposed to be used with Advanced Router Configuration when the switches restrict the maximum number of mac addresses (or ACLs) per physical port.
    • Limited SLAAC and DHCPv6 support

for detailed information (and i mean detailed), refer to the kernel documentation: https://docs.kernel.org/networking/ipvlan.html 🧚


πŸ’œ OPTIONS πŸ’œ

  • IPVLAN <yes|no> β€” this option must be set to yes to identify this configuration type as IPVLAN. no yes, no IPVLAN, periodt βœ‹
  • IPVLAN_DEVICE β€” mandatory option to specify the lower (parent) interface for this IPVLAN interface. mandatory, bestie, like the homework you can't skip 😭
  • IPVLAN_MODE <l2|l3|l3s> β€” specifies the operational mode for the IPVLAN interface. for a given lower device, you can select one of these modes and all linked devices will operate in the same mode. no mixing and matching, she's a package deal πŸ’«
    • Default: l3
  • IPVLAN_FLAGS <bridge|private|vepa> β€” specifies the mode flags. only one flag at a time is allowed. similar to IPVLAN_MODE, a given flag will be applied to all linked devices of one lower interface. one flag, one vibe, that's the rule 🚩
    • Default: bridge

🌈 EXAMPLES 🌈

example ifcfg-<name> config file for an IPVLAN interface β€” steal this, it's cute:

STARTMODE=auto
BOOTPROTO=static
IPADDR=10.0.0.100/24

IPVLAN=yes
IPVLAN_DEVICE=eth0
IPVLAN_MODE=l3s
IPVLAN_FLAGS=bridge

Copyright (C) 2024 SUSE LLC. protect the intellectual property, we love to see it πŸ’–


πŸ’€ BUGS πŸ’€

found a bug? please report bugs as described at https://bugs.opensuse.org β€” don't suffer in silence bestie, tell the maintainers 🫢


πŸ”₯ SEE ALSO πŸ”₯

routes (5), ifcfg (5), wicked (8) β€” go read those too, iykyk πŸ“š


πŸ‘‘ AUTHORS πŸ‘‘

Clemens Famulla-Conrad. absolute legend, we stan 🌟


and that's the page!! fr fr, ifcfg-ipvlan really ate and left no crumbs πŸ“

sign-off szn: this was the Wicked User Manual, dated November 2024. see you in the next manpage, bestie πŸ’œβœ¨
πŸ“¦ where this page comes from