> On Oct 6, 2019, at 2:59 PM, Sebastian Benoit <be...@openbsd.org> wrote:
>
> Ted Unangst(t...@tedunangst.com) on 2019.10.06 14:33:17 -0400:
>> I'm not sure where the bug is exactly (seems probable it could be an apple
>> problem), but for the record...
>>
>> When my laptop roams from my home wifi to my phone hotspot, it retains the
>> same IP it had on the home network, which doesn't work with the phone
>> network.
>> Running dhclient manually results in it supposedly getting the same IP:
>> iwm0: bound to 10.3.3.63 from 172.20.10.1
>>
>> The only way to get a working IP is to delete the dhclient.leases file, then
>> run it again. At last:
>> iwm0: bound to 172.20.10.6 from 172.20.10.1
>>
>> I'm not sure what can be done. Does ios echo back our suggestion incorrectly?
>> Does it return some result that dhclient misinterprets? No idea. We could
>> detect this condition perhaps? Anyway, there's a workaround for affected
>> people.
>
> I think ifconfig output in the home wifi and the hotspot wifi would be
> helpful for debugging, and the pcap file from
>
> tcpdump -s 1500 -w /tmp/wifi.pcap -i <if> port bootps or port bootpc
>
> while you move from one network to the other, and then run dhclient by hand.
>
> /B.
>
And the leases file when it is misbehaving.
Running with -L on both networks (saving the different versions!) to record
what dhclient thinks it is getting and configuring would also help diagnosis.
And the dhclient.conf file just to add suspenders to the belt and road
initiative.
Unfortunately I've got no idea how to gather useful info on the ios side.
.... Ken
