289
edits
Difference between revisions of "Mesh/Firmware"
Jump to navigation
Jump to search
changed formatting
Jwentwistle (talk | contribs) (added details about bandwidth shaping) |
Jwentwistle (talk | contribs) (changed formatting) |
||
| Line 168: | Line 168: | ||
Potential use of [https://en.wikipedia.org/wiki/Quilt_%28software%29 Quilt] to update nodes. | Potential use of [https://en.wikipedia.org/wiki/Quilt_%28software%29 Quilt] to update nodes. | ||
== | == QoS / bandwidth shaping == | ||
To support letting node owners select how much bandwidth they share. Allow users to block forwarded traffic based on type. There's an paper regarding [http://www.scribd.com/doc/155501125/Layer-7-Classificarion-and-Policing-in-the-PfSense layer 7 traffic shaping] too. | |||
'''Complete Distributions''' | '''Complete Distributions''' | ||
| Line 197: | Line 197: | ||
The firmware should tunnel all internet traffic from the mesh through a VPN server, unless this feature is specifically disabled. This should not be a single server, as that would be a single point of failure. | The firmware should tunnel all internet traffic from the mesh through a VPN server, unless this feature is specifically disabled. This should not be a single server, as that would be a single point of failure. | ||
[https://github.com/sudomesh/tunneldigger TunnelDigger] - a lightweight tunneling client/server. | * [https://github.com/sudomesh/tunneldigger TunnelDigger] - a lightweight tunneling client/server. | ||
[https://github.com/heyaaron/openmesher OpenMesher] - another option, but not ideal because of memory constraints on embedded systems. | * [https://github.com/heyaaron/openmesher OpenMesher] - another option, but not ideal because of memory constraints on embedded systems. | ||
Here is our [[Mesh/Network_topology|Network Topology]]. | Here is our [[Mesh/Network_topology|Network Topology]]. | ||