[Bug]: Static IP configuration doesn't work #2543
Labels
bug
Something isn't working
Comments
|
Are you converting the ip address to an integer? |
|
No, I'm setting the IP address via Android App and it enforces x.x.x.x In the debug panel of the app, it correctly shows the IP configuration in decimal values. |
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Fixes meshtastic#2543
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Fixes meshtastic#2543
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Also, the RAK4631 uses little endian, which is why the IP addresses need to be converted before setting them. Fixes meshtastic#2543
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Also, the RAK4631 uses little endian, which is why the IP addresses need to be converted before setting them. Fixes meshtastic#2543
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Also, the RAK4631 uses little endian, which is why the IP addresses need to be converted before setting them. Fixes meshtastic#2543
micheljung
added a commit
to zso-pfhr/firmware
that referenced
this issue
Jun 6, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Also, the RAK4631 uses little endian, which is why the IP addresses need to be converted before setting them. Fixes meshtastic#2543
thebentern
pushed a commit
that referenced
this issue
Jun 7, 2023
With static ethernet config, `status` stayed `0` which let the function return without setting `ethEvent`. Therefore, `reconnectETH` was never called and network services were never started. Also, the RAK4631 uses little endian, which is why the IP addresses need to be converted before setting them. Fixes #2543
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Category
Other
Hardware
Rak4631
Firmware Version
2.1.11
Description
Connect a RAK with an ethernet module and DHCP enabled, it will successfully get an IP address (e. g. 192.168.1.223) and can be pinged.
Switch to the static IP configuration, set the exact same IP address (192.168.1.223) and appropriate subnet mask (255.255.255.0) and you can no longer ping the device.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: