> On Apr 20, 2024, at 1:01 AM, Thomas D. Dean <tomd...@wavecable.com> wrote: > > On 4/19/24 18:35, Michael van Elst wrote: >> tomd...@wavecable.com ("Thomas D. Dean") writes: >>> How do I setup wpa_supplicant? >> That depends on what you want to do. >> Here are some examples: >> https://wiki.netbsd.org/tutorials/how_to_use_wpa_supplicant/ > > I saw that. > dhcp is working over the wired connection. > > I thought I had everything configured for wifi. It just does not work. > > I have a cable modem <-> wifi/wired router. I have several machines > connected. Linux and windoze, now. One RPi with NetBSD 10. Used to have some > FreeBSD machines, but, they have been replaced. > > # etc/rc.d/wpa_supplicant reload > Selected interface 'bwfm0' > 21:58:35.931: OK > > # wpa_cli status > Selected interface 'bwfm0' > 21:58:44.815: bssid=60:38:e0:db:a9:7a > freq=0 > ssid=tddhome > id=0 > mode=station > pairwise_cipher=TKIP > group_cipher=TKIP > key_mgmt=WPA-PSK > wpa_state=GROUP_HANDSHAKE > ip_address=169.254.135.120 > address=e4:5f:01:da:eb:46 > > # ifconfig bwfm0 > bwfm0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > ssid "" nwkey 65536:"","","","" > powersave off > address: e4:5f:01:da:eb:46 > media: IEEE802.11 autoselect (DS1 mode 11g) > status: no network > inet6 fe80::d7c0:41b9:46a5:a5ff%bwfm0/64 flags 0x8<DETACHED> scopeid 0x3 > inet 169.254.135.120/16 broadcast 169.254.255.255 flags 0x4<DETACHED> > > > > I don't understand where the inet 169.254.135.120 comes from. The router pool > is 192.168.1.xxx.
That's an APIPA address from block 169.254.0.0/16. dhcpcd gives the interface an address from that block when it can't properly obtain one via DHCP, unless instructed not to. > > Tom Dean