IFCFG-IPVLAN(5)
π 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 toyesto identify this configuration type as IPVLAN. noyes, 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
- Default:
IPVLAN_FLAGS<bridge|private|vepa> β specifies the mode flags. only one flag at a time is allowed. similar toIPVLAN_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
- Default:
π 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 π
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
- opensuse-leap 16.0: wicked 0.6.80-bp160.2.1 Β· GPL-2.0-or-later
- opensuse-leap 16.0: wicked 0.6.80-bp160.2.1 Β· GPL-2.0-or-later
- opensuse-leap 16.0: wicked 0.6.80-bp160.2.1 Β· GPL-2.0-or-later
- opensuse-leap 16.0: wicked 0.6.80-bp160.2.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms