News for hackers. Stuff that matters.
Re:IPvlan overlay-free Kubernetes Networking in AWS by muxator on Monday December 04, 2017 @07:52PM (#15848937)
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

Re:IPvlan overlay-free Kubernetes Networking in AWS by KaiserPro on Tuesday December 05, 2017 @05:43AM (#15850999)
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

Re:IPvlan overlay-free Kubernetes Networking in AWS by puzzle on Tuesday December 05, 2017 @12:43AM (#15850000)
If you need distinct MAC addresses, though, for e.g. DHCP, usually not the case with containers, then you have to use macvlan.