I wish to have a macvlan interface with an IP on the same subnet as its parent interface, but I am experiencing difficulties in getting traffic from the internet to flow back in to applications (namely ping) bound to the macvlan.I think it's an ARP issue.eth0 is on 192.168.1.214/24I would like another interface, static0 to get 192.168.1.5.I create and bring up a macvlan interface with eth0 as parent:ip link add static0 link eth0 type macvlan mode bridgeip link set static0 upI configure static0's ip to be on the same subnet as eth0:ip addr add 192.168.1.5/24 dev static0eth0's has hwaddr aa:aa:aa:aa:aa:aastatic0 gets bb:bb:bb:bb:bb:bbAt this point, my routing looks as follows:$ ip routedefault via 192.168.1.254 dev eth0  proto static  metric 100 169.254.0.0/16 dev eth0  scope link  metric 1000192.168.1.0/24 dev static0  proto kernel  scope link  src 192.168.1.5 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.214  metric 100 It's a bit redundant, but it all goes out the same physical link anyways.I do ping from the host, binding to my new interface, but the application does not receive the replies:# ping -I static0 google.comPING google.com (216.58.216.174) from 192.168.1.5 static0: 56(84) bytes of data.(no output)In a separate terminal, I tcpdump icmp traffic on static0, and see both the echo requests and replies, but they don't make their way to the application:# tcpdump -i static0 -vten icmpbb:bb:bb:bb:bb:bb > 00:00:0c:07:ac:00, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 36290, offset 0, flags [DF], proto ICMP (1), length 84)    192.168.1.5 > 216.58.216.174: ICMP echo request, id 31813, seq 541, length 6400:1e:f6:46:2c:00 > bb:bb:bb:bb:bb:bb, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 55, id 0, offset 0, flags [none], proto ICMP (1), length 84)    216.58.216.174 > 192.168.1.5: ICMP echo reply, id 31813, seq 541, length 64Another thing I tried was to assign 192.168.1.5/32 to static0 instead of /24, which simplifies the routing table, and produces the same tcpdump trace, but doesn't help otherwise.
Is placing a macvlan interface on the same subnet as the parent interface supported?
networking;macvlan