On Sun, Sep 27, 2026, at 2:59 AM, Crystal Kolipe wrote: > > You probably want something like: > > # dhcpleased -dvv 2>&1 | tee /tmp/logfile > > ... as dhcpleased is writing to stderr and tee only captures stdout.
Ah, thanks, that was it, it didn't occur to me it might be going to stderr, I thought it was some kind of buffering issue. >> >> # dhcpleased -d -vv >> state_transition[iwm0] Down -> Rebooting, timo: 1 >> DHCPREQUEST on iwm0 >> parse_dhcp, from: 4c:37:4a:4a:35:e7, to: ff:ff:ff:ff:ff:ff >> parse_dhcp: 10.0.0.1:67 -> 255.255.255.255:68 > > As Florian also points out, this is a reply being received from the router. > > So although the other tests initially suggested that you might have had an > issue with 2.5 Ghz vs 5 Ghz operation, (I.E. no Tx on 5 Ghz *, which would > point to the iwm driver code), now we see that at least the DHCPNAK packet was > received from the router by your iwm device, so it's not a simple, 'rx isn't > working on 5 Ghz' issue. > > (*) although there must have been at least some Tx to connect to the AP in the > first place, so I was a bit dubious about that. > > Having said that, for completeness I guess it could still plausibly be > something very specific, such as a specific packet size or content that was > triggering a bug in the driver code and preventing the request going out, but > I would put that possibility as a distant last. > > Next step would be to try what Stuart suggested and test a different dhcp > client: Thanks, trying this. I'm looking at the man page for dhcpcd and cobbled together this command which looks like it should do the thing? However it does not. # dhcpcd iwm0 -r 10.0.0.176 (I picked that address randomly, it's higher than any current assigned address) dhcpcd-10.3.1 starting iwm0: is a Virtual Interface Master, skipping iwm0: interface not found dhcpcd exited > > Also, are you running the most recent firmware on the router? I have not found any way in the extremely "black box" app I use to control the router, to check if it's updated, unfortunately
