OK, I tried splitting the bands into their own NWIds, and trying connecting to the 2.5GHz and 5GHz bands individually, and the results were similar to what I've seen so far (I end up with a network with "status: active" but no IP address.
I also tried removing "inet autoconf" from the /etc/hostname.iwm0 file, and replacing it with: inet 10.0.0.179 255.255.255.0 NONE I just arbitrarily picked 179 because it's higher than the most recently handed out address I know of, 174. This makes "ifconfig" think I have that address, but I when I try to "ping" the router or a linux box on my network, which I happen to know the IP of, I get "sendmsg: Host is down". However, if I use tcpdump, I still see a lot of chatter from random devices on my network (including the linux box I was unable to successfully ping or ssh to). On Sun, Sep 27, 2026, at 1:08 PM, Lloyd wrote: > It could help to force it to connect to 2.4 GHz. > > Your access point may be running in ax mode. > > I'm not convinced this is purely a DHCP issue. > > Your device may be associating to the AP but not sending traffic. > > Another way to rule out DHCP issues is assign a static IP. > > Regards > Lloyd > > Ed Heil wrote: > >> I know that my home wifi combines the 2.5 and 5G channels under >> a single nwid. It has the option of separating them but >> there's a note in the app saying it's recommended to keep them >> together. Maybe I should separate them and see if my openbsd >> box can connect to the 2.5G one once it's separated?
