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
Today we just learn by doing ARP, and we dont have mac aging or prevention against mac address flooding etc.. Also we dont learn mac from the source packet (if the source is in the connected subnet). ARP/mac learning needs significant amount of enhancements
At least for the purpose of Encap node learning the mac from Decap, it should be possible to combine both Encap and Decap nodes to one single node. Need to think about this carefully if we want to scale mac address learning
Also the Encap nodes on all threads dont need to learn macs and keep it in hashtables etc.., only the encap on the thread owning the interface needs to learn the mac
The text was updated successfully, but these errors were encountered:
Today we just learn by doing ARP, and we dont have mac aging or prevention against mac address flooding etc.. Also we dont learn mac from the source packet (if the source is in the connected subnet). ARP/mac learning needs significant amount of enhancements
At least for the purpose of Encap node learning the mac from Decap, it should be possible to combine both Encap and Decap nodes to one single node. Need to think about this carefully if we want to scale mac address learning
Also the Encap nodes on all threads dont need to learn macs and keep it in hashtables etc.., only the encap on the thread owning the interface needs to learn the mac
The text was updated successfully, but these errors were encountered: