Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
series of MATCHes that are ORed.
|
|
|
|
|
|
any flag" is generally what we want.
|
|
this since they aactually follow the full network path even for local IPs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
unknown networks to prevent forensics.
|
|
|
|
|
|
attack potential, and implement network config fast propagate (though we probably will not use this for a bit).
|
|
|
|
|
|
(thanks JG@DCVC!), and clean up some cruft in Network.
|
|
rapid setup. Will need to revisit later.
|
|
item presented to controller by nodes (to facilitate future meshiness).
|
|
|
|
|
|
|
|
multicast on the network as would be expected.
|
|
65535 ports per IP.
|
|
|
|
|
|
|
|
|
|
since they will need them to push auth for multicast stuff, (2) added a bunch of rate limit circuit breakers for anti-DOS, (3) cleanup.
|
|
etc., and fix an issue with sending ECHO to recheck marginal paths.
|
|
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.
|
|
compatiblity issue.
|
|
|
|
lazily when member is learned.
|
|
|
|
|
|
pushes and simplify code.
|
|
|
|
since we could get pushed one that is newer.
|