| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
lookup.
|
|
|
|
explicitly check whether paths should be used. Check in with this callback (if present) when learning new paths or sending initial packets.
|
|
|
|
uPnP addresses?!?
|
|
|
|
|
|
|
