892
edits
Difference between revisions of "Mesh/Firmware"
no edit summary
(Updating Firmware QoS / bandwidth shaping status) |
|||
| Line 1: | Line 1: | ||
Documentation for the sudo mesh firmware. | Documentation for the sudo mesh firmware. | ||
= ToDo = | |||
This is a list of things we want to solve for future firmware versions: | |||
* Get watchdog working (Rhodey) | |||
* Get fake captive portal running (MaxB, Louis, Juul) | |||
* Deal with situations where the node's eth0 is plugged into a 10.0.0.0/8 network. | |||
* Deal with situations where internet is not shared or not present. | |||
* Figure out a solution for MAC address anonymizing. | |||
* Set up OpenVPN on exit node. | |||
* Implement statistics for web admin interface. | |||
* Manual (or automatic?) speed and output power selection via web interface. | |||
* Support ar71xx chipsets (this is mostly a node-configurator issue) | |||
* Select a wifi channel. | |||
* Get hardware watchdog support working for Meraki Outdoor units (ask mischief on irc). | |||
* Support TDMA on Linux (Adri is working on FreeBSD support, maybe we can port). | |||
* Test if batman Internet gateway selection is working correctly | |||
** Currently DHCP hands out exit node IP as gateway, which means that the bandwidth specified in the batman gw_mode will not be taken into account. | |||
** It should maybe hand out node IP as gateway, but since both are on same subnet, this will cause ICMP redirect messages to be generated. | |||
= Firmware generation features = | = Firmware generation features = | ||