Skip to content

TRMNL reports not connected to WiFi when no DHCP #157

@stevekennedyuk

Description

@stevekennedyuk

I use my WiFi access points in bridge mode as I run my own DHCPd server on Linux. The Linux box may occasionally be down so no DHCP addresses will be allocated. If TRMNL happens to connect at this point, it will fail - but the error message will be "can not connect to WIFi", when in fact the WiFi has connected, but there's no DHCP IP address allocated.

There should be a way to set a default IP (even if it's something like 192.168.1.1) and also there should be a separate message i.e. "No IP address/unable to get address from DHCP" and only "can not connect to WiFi" when there's an actual WiFi connection error.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions