diff --git a/docs/interfaces_and_networks.md b/docs/interfaces_and_networks.md
index aa54312..ba04321 100644
--- a/docs/interfaces_and_networks.md
+++ b/docs/interfaces_and_networks.md
@@ -36,7 +36,7 @@ spec:
 
 It is also possible to connect VMs to secondary networks using [Multus CNI](https://github.com/k8snetworkplumbingwg/multus-cni). This assumes that Multus CNI is installed across your cluster and a corresponding `NetworkAttachmentDefinition` CRD was created.
 
-The following example defines a network which uses the [Open vSwitch CNI plugin](https://github.com/k8snetworkplumbingwg/ovs-cni), which will connect the VM to Open vSwitch's bridge `br1` on the host. Other CNI plugins such as [bridge](https://www.cni.dev/plugins/current/main/bridge/) or [macvlan](https://www.cni.dev/plugins/current/main/macvlan/) might be used as well. For their installation and usage refer to the respective project documentation.
+The following example defines a network which uses the [Open vSwitch CNI plugin](https://github.com/k8snetworkplumbingwg/ovs-cni), which will connect the VM to Open vSwitch's bridge `br1` on the host. Other CNI plugins such as [bridge](https://www.cni.dev/plugins/current/main/bridge/) might be used as well. For their installation and usage refer to the respective project documentation.
 
 First the `NetworkAttachmentDefinition` needs to be created.
 
@@ -70,6 +70,8 @@ spec:
         networkName: ovs-br1
 ```
 
+> **Note**: The [macvlan](https://www.cni.dev/plugins/current/main/macvlan/) CNI plugin cannot work with bridge interface, since the unicast frame to VM will be dropped without `passthru` mode.
+
 ## VM Network Interfaces
 
 VM network interfaces are configured in `spec.instance.interfaces`. They describe properties of virtual interfaces as "seen" inside guest instances. The same network may be connected to a VM in multiple different ways, each with their own connectivity guarantees and characteristics.