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
Comments
For those wondering what's the difference between macvlan and ipvlan, the main ipvlan paper [0] summarizes its raison d'être:
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
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
If you need distinct MAC addresses, though, for e.g. DHCP, usually not the case with containers, then you have to use macvlan.