Hi Jon, Your reply led me to check my machines. They were ok.Only DHCP clients. I then checked the router’s client list. It turned out that the guest network assigns the 192.168.101 addresses. Not documented! So I changed the hostname.urtwn0 from the guest network to the “real” network. Now everything works. Thanks for your insight!
/niels Sent from [Proton Mail](https://proton.me/mail/home) for iOS On Wed, Jan 29, 2025 at 10:22, Jon Higgs <[j...@altos.au](mailto:On Wed, Jan 29, 2025 at 10:22, Jon Higgs <<a href=)> wrote: > On 29/01/25 09:05, Niels Müller Larsen wrote: >> I have a Thinkcentre, a Thinkpad laptop and an HP Probook laptop. My router >> gives IP addresses in the 192.168.1.xxx segment. >> Works fine on the ethernet and the builtin wifi adapters. But when I add a >> USB D-Link adapter, the Thinkcentre behaves as expected, it gets an >> 192.168.1.xyz address, but if I stick it into the Thinkpad or the Probook it >> gets 192.168.101.xyz. >> All of them are OpenBSD 7.6 and I have a single join, and inet autoconf in >> the hostname.urtwn0 files. >> I have searched and not found any explanation. >> >> Anyone here seen anything like that? > > Hi Niels, > > Sounds like you have two DHCP servers on the segment. The clients are > taking the offer from the server they have a pre-existing lease with. > When you move the USB adapter to another host, there is no preference > because it has no existing leases for that interface. It it takes the > first offer it gets. > > I hope that helps. > > -- > Jon
