| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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).
|
|
since this breaks IPv6 on OSX and probably IPv4 too if you were to encounter a 6-only situation.
|
|
|
|
|
|
|
|
|
|
multicast on the network as would be expected.
|
|
on Mac. This version adds the bifurcated routes always but also adds a device-specific non-bifurcated route. Will have to see if this still interferes with OSX route settings, since by definition device specific routes should not conflict with general routes.
|
|
65535 ports per IP.
|
|
|
|
|
|
|
|
nice but it is non-critical and rules are the priority. Current implementation bangs heads with OSX route assignment on WiFi join, etc.
|
|
|
|
|
