You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that FAUCET will push a VLAN header on a packet, then pop it.
In the meantime, we need to match on the packet's VLAN header after the push but before the pop.
It appears it will not match the packet when the header has been pushed.
Bug report
Vlan pop out functions at the Edge port break the matching or forwarding action.
Here is the lagopus show flow output even with the counter at zero.
Packets with VLAN tag strip out at the edge should not break the data plane.
Actual behavior
Trying to ping two hosts connected to Lagopus does not work using native VLAN at the Edge and VLAN tagging in the Lagopus bridge.
If we configure the hosts with trunks and lagopus does not have to strip out the VLAN tag it works.
Issue Type
Summary
The problem is that FAUCET will push a VLAN header on a packet, then pop it.
In the meantime, we need to match on the packet's VLAN header after the push but before the pop.
It appears it will not match the packet when the header has been pushed.
Bug report
Vlan pop out functions at the Edge port break the matching or forwarding action.
Here is the lagopus show flow output even with the counter at zero.
Expected behavior
Packets with VLAN tag strip out at the edge should not break the data plane.
Actual behavior
Trying to ping two hosts connected to Lagopus does not work using native VLAN at the Edge and VLAN tagging in the Lagopus bridge.
If we configure the hosts with trunks and lagopus does not have to strip out the VLAN tag it works.
Environment
Steps to reproduce
Relevant logs
All details can be found in the linked file below :
FAUCET LAGOPUS confs .txt
Links / reference
The text was updated successfully, but these errors were encountered: