Security: Track the number of open inbound and outbound connections separately #2904
Labels
A-network
Area: Network protocol updates or fixes
C-security
Category: Security issues
I-remote-node-overload
Zebra can overload other nodes on the network
Milestone
Motivation
To limit the number of inbound and outbound connections in Zebra, we need to track them separately.
Suggested Design
Split the changes from #2903 into inbound and outbound.
See #1850, #1851, and #2902 for details of which functions make inbound and outbound connections.
Edge Cases
How can we make sure the inbound and outbound signals don't block each other?
How can we make sure we don't get the inbound and outbound signals mixed up?
The text was updated successfully, but these errors were encountered: