Difference between revisions of "Mesh/Firmware"

Mesh/Firmware (view source)

Revision as of 19:02, 24 April 2014

135 bytes added , 19:02, 24 April 2014

→‎ToDo

Juul

Bureaucrats, Administrators

890

edits

@@ Line 3: / Line 3: @@
 = ToDo =
-This is a list of things we want to solve for future firmware versions:
+Stuff we _need_ before beta launch:
-* Make it possible to contribute to html/css without installing a dev environment (e.g. for luci)
+* Get watchdog working on ar71xx (?)
-* Get watchdog working (Rhodey)
+* Make analog hardware watchdog for old chipset and solder to devices.
-* Get fake captive portal running (MaxB, Louis)
+* Run a node with serial monitoring to see if we can learn why it crashes.
 * Detect ethernet being plugged/unplugged and send DHCP requests accordingly.
-* Deal with situations where internet is not shared or not present.
+* Deal with situations where internet is not shared or not present. (juul)
-* Deal with situations where the node's eth0 is plugged into a 10.0.0.0/8 network.
+* Deal with situations where the node's eth0 is plugged into a 10.0.0.0/8 network (juul)
 * Implement remote password reset (via h.sudomesh.org)
 * Implement error reporting in web admin interface
-** Script that checks for issues and reports back, e.g. "Ethernet is connected and DHCP server is present but DHCP server does not want to give me (the node) an IP. DHCP server probably has MAC address filtering enabled."
+* Implement a remote logging/monitoring solution (how far along is nodewatcher 2?)
+** Maybe with a script that checks for issues and reports back, e.g. "Ethernet is connected and DHCP server is present but DHCP server does not want to give me (the node) an IP. DHCP server probably has MAC address filtering enabled."
+* Select a wifi channel, both 2.4 ghz and 5 ghz.
+* Test if batman Internet gateway selection is working correctly (juul)
+** Currently DHCP hands out exit node IP as gateway, which means that the bandwidth specified in the batman gw_mode will be taken into account for DHCP server selection but not for gateway selection. Gateway selection will just happen based on normal batman-adv routing.
+** DHCP servers should maybe hand out node IP as gateway, but since both are on same subnet this will cause ICMP redirect messages to be generated.
+Issues for later versions:
+* Figure out how to legally use lower 5 ghz frequencies
 * 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.
 * Find better solution for batman/tunneldigger related MTU issues (Juul).
 ** Currently setting client MTU with DHCP (does not work on e.g. Win 7) and using TCP MSS clamping on exit node (obviously only works for TCP).
-* 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
+* Make it possible to contribute to html/css without installing a dev environment (e.g. for luci)
-** Currently DHCP hands out exit node IP as gateway, which means that the bandwidth specified in the batman gw_mode will be taken into account for DHCP server selection but not for gateway selection. Gateway selection will just happen based on normal batman-adv routing.
-** DHCP servers 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 =