anchor.diff:        {
           "type": "cnv-bridge", <4>
           "bridge": "<bridge-interface>", <5>
  -        "vlan": 1 <6>
  +        "macspoofchk": true, <6>
  +        "vlan": 1 <7>
         },
         {
  -        "type": "cnv-tuning" <7>
  +        "type": "cnv-tuning" <8>
         }
       ]
     }'
  
positive.code: $ oc get network-attachment-definition <a-bridge-network> <1>
  ----
  <1> Where `<a-bridge-network>` is the name specified in the network attachment definition config.
  
  
negative.code: <3> The name for the configuration. It is recommended to match the configuration name to the `name` value of the network attachment definition.
  <4> The actual name of the Container Network Interface (CNI) plug-in that provides the network for this network attachment definition. Do not change this field unless you want to use a different CNI.
  <5> The name of the Linux bridge configured on the node.
  <6> Optional: Flag to enable MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod.
  <7> Optional: The VLAN tag.
  <8> The CNI plug-in that allows the MAC pool manager to assign a unique MAC address to the connection.
  
  . Create the network attachment definition:
  +
  [source,terminal]
  ----
  