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
During development and testing I came about a situation where neighbor solicitation flows would cause softflowd to go crazy. Scenario: something in the network causes NS packets every 5-30 seconds. EACH of these flows will be picked up by softflowd as TWO flows (neighbor solicitation and neighbor advertisement). Then these flows will be exported. And for some reason, softflowd exports them in a single UDP packet each. Result: softflowd also captures each of these UDP packets as one flow, causing exponential packet generation.
This causes the collector to amout a massive stream of incoming packets, eventually even going OOM.
The text was updated successfully, but these errors were encountered:
During development and testing I came about a situation where neighbor solicitation flows would cause softflowd to go crazy. Scenario: something in the network causes NS packets every 5-30 seconds. EACH of these flows will be picked up by softflowd as TWO flows (neighbor solicitation and neighbor advertisement). Then these flows will be exported. And for some reason, softflowd exports them in a single UDP packet each. Result: softflowd also captures each of these UDP packets as one flow, causing exponential packet generation.
This causes the collector to amout a massive stream of incoming packets, eventually even going OOM.
The text was updated successfully, but these errors were encountered: