----------------------------------------------------------------------------------
@MSGID: <op.2bdgr6yta3w0dxdave@hodgins.homeip.net>
a4ace212
@REPLY: 1@dont-email.me> c56cae01
@REPLYADDR David W. Hodgins
<dwhodgins@nomail.afraid.org>
@REPLYTO 2:5075/128 David W. Hodgins
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<op.2bdgr6yta3w0dxdave@hodgins.homeip.net>
@RFC-References: 1@dont-email.me>
@TZUTC: -0400
@PID: Opera Mail/12.16 (Linux)
@TID: FIDOGATE-5.12-ge4e8b94
On Sat, 16 Sep 2023 05:19:48 -0400, The Natural Philosopher
<
tnp@invalid.invalid> wrote:
Just including the parts relevant to my suggestion ...
> But if the Pi Zero is disconnected and then reconnected, it fails to
> pick up DHCP.
> This is the syslog for a *successful* connection after reboot
>
> Sep 16 09:57:42 juliet NetworkManager[739]: [1694854662.5981]
> dhcp4 (usb0): option dhcp_lease_time => `43200`
> But this is what happens when the device is unplugged and re plugged in..
> Sep 16 09:41:53 juliet NetworkManager[737]: [1694853713.5013]
> device (usb0): interface index 4 renamed iface from `usb0` to
> `enxf62dad34f39e`
There isn`t enough shown from the good connection to show whether it`s occurring
after the interface is renamed or before it. I`m just wondering if it`s not
being recognized due to that, in combination with settings in the dhcp server.
Try adding the kernel boot parameter net.ifnames=0 to stop the interface being
renamed.
If that fails, run wireshark on the host so you can compare what is being sent
and received to/from the dhcp server.
Regards, Dave Hodgins
--- Opera Mail/12.16 (Linux)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441