892
edits
Difference between revisions of "Mesh/Firmware"
Jump to navigation
Jump to search
→ToDo
(→ToDo) |
|||
| Line 7: | Line 7: | ||
* Get watchdog working (Rhodey) | * Get watchdog working (Rhodey) | ||
* Get fake captive portal running (MaxB, Louis, Juul) | * Get fake captive portal running (MaxB, Louis, Juul) | ||
* Deal with situations where internet is not shared or not present. | |||
* 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. | ||
* | * 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." | |||
* Figure out a solution for MAC address anonymizing. | * Figure out a solution for MAC address anonymizing. | ||
* Set up OpenVPN on exit node. | * Set up OpenVPN on exit node. | ||
| Line 18: | Line 20: | ||
* Support TDMA on Linux (Adri is working on FreeBSD support, maybe we can port). | * Support TDMA on Linux (Adri is working on FreeBSD support, maybe we can port). | ||
* Test if batman Internet gateway selection is working correctly | * 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 | ** 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 = | = Firmware generation features = | ||