| Age | Commit message (Collapse) | Author |
|---|
|
series of MATCHes that are ORed.
|
|
|
|
any flag" is generally what we want.
|
|
|
|
|
|
|
|
(thanks JG@DCVC!), and clean up some cruft in Network.
|
|
|
|
multicast on the network as would be expected.
|
|
do not handle OK packets we did not expect. This hardens up a few potential edge cases around security, since such messages might be used to e.g. pollute a cache and DOS under certain conditions.
|
|
normally use expired paths. Expired paths might still be tried if nothing else is reachable.
|
|
|
|
happen if an unsupported or unknown MATCH is encountered in a rules table.
|
|
|
|
|
|
meta-data.
|
|
|
|
Network.cpp.
|
|
|
|
|
|
|
|
json-parser to eliminate a dependency.
|
|
|
|
|
|
elegant way.
|
|
protocol cleanup.
|
|
reused.
|
|
capabilities, and some cleanup across other places.
|
|
|
|
|
|
|
|
|
|
|
|
will be powerful.
|
|
|
|
|
|
|
|
|
|
|
|
network controller easier to refactor.
|
|
|
|
|
|
|
|
|
|
representation, especially rules.
|
|
lookup point.
|
|
more rules with better space efficiency.
|
|
|
|
|
|
|
