Possibly but might be worth holding off for a while.
While I agree the driver shouldn't be starting the DHCP client I can see why that's done. A solution needs to backwards compatible. I can't see it would be easy to refactor to have the driver conditionally start automatically or not, but that might just be me. Asking for DHCP and switching to Fixed doesn't really seem all that problematic in most cases, might be considered an aesthetic or idealogical issue. A bug fix request in that direction may therefore not go down well.
An alternative which might gain more traction is to keep what we have, and simply have an option to turn DHCP off. If it's not running when the connect happens I can't see that it would ask for DHCP so issue solved. Something like -
While I agree the driver shouldn't be starting the DHCP client I can see why that's done. A solution needs to backwards compatible. I can't see it would be easy to refactor to have the driver conditionally start automatically or not, but that might just be me. Asking for DHCP and switching to Fixed doesn't really seem all that problematic in most cases, might be considered an aesthetic or idealogical issue. A bug fix request in that direction may therefore not go down well.
An alternative which might gain more traction is to keep what we have, and simply have an option to turn DHCP off. If it's not running when the connect happens I can't see that it would ask for DHCP so issue solved. Something like -
But I'd want to have that working or at least tried first.wlan = network.WLAN(network.STA_IF)
wlan.ifconfig("nodhcp")
wlan.connect(secrets.SSID, secrets.PASSWORD)
wlan.ifconfig(("192.168.0.199", "255.255.255.0", "192.168.0.1", "192.168.0.1"))
Statistics: Posted by hippy — Fri Jan 26, 2024 12:08 am