On Sat, Sep 26, 2026 at 10:11:25PM +0000, Lloyd wrote:
> Use the Macbook to create a temporary wi-fi hotspot, then run
> tcpdump or Wireshark on the Mac to verify you are really receiving
> traffic from the Thinkpad. This could rule out DHCP issues.
>
> Futher, you can Option+click the Wi-Fi icon in the menubar to open
> Wireless Diagnostics, some helpful tools there to capture traffic.
>
This is the first thing I've tried of the suggestions
just made, and it actually worked -- I successfully
connected to the Macbook's hotspot, *and received an
IP address* from it.
----
tsathoggua# ifconfig iwm0
iwm0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
lladdr 14:ab:c5:59:a2:c2
index 1 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect (HT-MCS15 mode 11n)
status: active
ieee80211: nwid macbookhotspot chan 11 bssid 46:10:99:81:26:34 95%
wpakey wpaprotos wpa2 wpaakms psk,sha256-psk wpaciphers ccmp wpagroupcipher ccmp
inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255
----
I don't have dns resolution, so I can't ping openbsd.org or anything,
but I can get to any ip address I like, including other machines on my
home network. And I can ssh to the openBSD laptop from the macbook.
So the wifi works, and the dhcp works on some networks, but not others!
Crystal Kolipe wrote:
> Do you know what device 10.0.0.49 is? These arp requests are never answered.
I'm rather confused by that. My app unhelpfully thinks this is a "Generic
Linux Device." It doesn't return pings. I'm not sure what it is. It's not
any of the devices I'm concerning myself with right now.
> You might get more useful information by running dhcpleased in verbose mode:
>
> # rcctl stop dhcpleased
> # dhcpleased -d -vv
To give this I try, I changed my /etc/hostname.iwm0 to put my home
network's wifi name and password back in, and I fired it up and
retried the dhcpleasectl command.
I'm having a difficult time copying and pasting the output from
dhcpleased -- tmux isn't quite doing what I want it to do, and I can't
seem to get it through "tee" either. Skill issue with output
redirection probably. I'll copy it manually here instead.
# 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
dhcp_hdr op: Boot Reply (2)
dhcp_hdr htype: Ethernet (1)
dhcp_hdr hlen: 6
dhcp_hdr hops: 0
dhcp_hdr xid: 0x5296342d
dhcp_hdr secs: 0
dhcp_hdr flags: 0x80
dhcp_hdr ciaddr: 0.0.0.0
dhcp_hdr yiaddr: 0.0.0.0
dhcp_hdr siaddr: 0.0.0.0
dhcp_hdr giaddr: 0.0.0.0
dhcp_hdr chaddr: 14:ab:c6:59:a2:c2 (000000000000000000) (I may have miscounted
the 0's)
DHO_DHCP_MESSAGE_TYPE: DHCPNAK
DHO_DHCP_SERVER_IDENTIFIER: 10.0.0.1
DHO_56, len: 13
DHO_END
DHCPNAK on iwm0 from 4c:d7:4a:4a:35:37/10.0.0.1 to
ff:ff:ff:ff:ff:ff/255.255.255.255
deleting 192.168.2.2 from iwm0 (lease from 0.0.0.0)
^^^ that was the address from the macbook hotspot
state_transition[iwm0] Rebooting -> Init, timo: 1
deconfigure_interface iwm0
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 2
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 4
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 8
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 16
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 32
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 64
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 64
DHCPDISCOVER on iwm0
iface_timeout[1]: Init
state_transition[iwm0] Init -> Init, timo: 64
and so forth -- same situation as in the beginning, no ip
address received from home wifi.
Stuart Henderson wrote:
> Or maybe has run out of leasable addresses.
I'm pretty sure there are addresses available - I belive it has successfully
handed out addresses very recently.
> Are logs available on the router?
Sadly no, it's controlled by an app, with very limited diagnostics available :(
>
> Maybe try a different dhcp client (e.g. dhcpcd)?
I'm not sure what would go into this, I assume I would need to uninstall
dhcpleased or at least disable it, and install dhcpcd via pkg_add, and then
enable it? Would things have to be configured differently in /etc/hostname.iwm0
to make that work?
