3 ms·

For those wondering what's the difference between macvlan and ipvlan, the main ipvlan paper [0] summarizes its raison d'être: > This is especially problematic

For those wondering what's the difference between macvlan and ipvlan, the main ipvlan paper [0] summarizes its raison d'être: > This is especially problematic where the connected next-hop e.g. switch is expecting frames from a specific mac from a specific port. e.g.: if the host is attached to a managed switch with a strict security policy, macvlan would not work. [0] https://www.netdevconf.org/0.1/sessions/28.html https://www.netdevconf.org/0.1/sessions/28.html

puzzle 9y ago
If you need distinct MAC addresses, though, for e.g. DHCP, usually not the case with containers, then you have to use macvlan.
KaiserPro 9y ago
This is what I'm trying to understand. Macvlan appears to be a much better solution as it allows 1-1 mapping and piggybacking onto all the automatic/set&forget mechanisms that AWS provides. Obviously it needs a switch at the otherside that can handle a huge and quick changing arp table. Also if you have mac address limiting typical on edge switches, its a non flyer