My Community Dashboard

  • There is a macvlan reference here. It looks like by design, it could be on the same subnet as the parent interface so care must be taken over the addressing and I think you need to reserve the IP addresses it can assign using the --ip-range switch so it does not clash with DHCP or other manual IP addresses. It also looks like the macvlan interface cannot communicate with the parent interface at all. You may be able to get round this by creating a virtual interface and attaching the macvlan interface to the virtual interface.