This is an old revision of the document!
FreiFunk Bugs
Here you can find all the known bugs on the FreiFunk project and how to solve them.
Firmware
stable
Firmware version | Bug | Solution |
---|---|---|
2.0.3 | knows only old GW1 | update to new Version |
2.0.5 | knows only old GW1 | update to new Version |
2.1.0 | does not know new GW3 | update to new Version |
2.1.0 | auto-update bug, nodes stuck in boot loop on firmware update | POWER OFF/POWER ON node. Update to new Version. If update is not possible, re-flashing the node needs to be done. |
2.1.1 | does not know new GW3 | update to new Version |
2.1.1 | auto-update bug, nodes stuck in boot loop on firmware update | POWER OFF/POWER ON node. Update to new Version. If update is not possible, re-flashing the node needs to be done. |
experimental
Keep in mind,that installing an experimental firmware on a router may brick the device. It should only be installed to test new firmware and new hardware.
Firmware version | Bug | work-around |
---|---|---|
2.2.0~exp20181221 | NO LAN IPV4 | / |
2.2.0~exp20181221 | No config mode webgui after firmware update | re-flashing the node |
2.2.0~exp20190328 | NO LAN IPV4 | / |
2.2.0~exp20190328 | No config mode webgui after firmware update | re-flashing the node |
2.2.0~exp20190717 | NO LAN IPV4, may come from network | / |
2.2.0~exp20190909 | NO LAN IPV4, may come from network. contact info is not mandatory | / |
network
Bug | reason | solution | work-around |
---|---|---|---|
IP distribution on nodes, some times no IPV4 some time IPV4 and IPV6, no differnence if node is connected to GW2 or GW3 | / | solved | reboot the node |
Failover not working from GW2 to GW3 |