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 watchlist is designed to match only on IPv4 flows. This is probably happening because of PHV conflicts (arp/lldp fields ending up in ipv4/udp/tcp fields).
We should update the watchlist table to either:
match on ipv4 validity bit
wrap table apply with gateway condition (if (hdr.ipv4.isValid()) watchlist.apply())
We should check all the other tables in the pipeline. Do we check header validity when matching certain fields?
I wish the compiler would be capable of emitting warnings for such conditions.
The text was updated successfully, but these errors were encountered:
The watchlist is designed to match only on IPv4 flows. This is probably happening because of PHV conflicts (arp/lldp fields ending up in ipv4/udp/tcp fields).
We should update the watchlist table to either:
if (hdr.ipv4.isValid()) watchlist.apply()
)We should check all the other tables in the pipeline. Do we check header validity when matching certain fields?
I wish the compiler would be capable of emitting warnings for such conditions.
The text was updated successfully, but these errors were encountered: