Comment 16 for bug 1914740

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2021-02-25 10:28 EDT-------
(In reply to comment #25)
> For netplan yaml of:
>
> network:
> version: 2
> ethernets:
> enc8f00:
> dhcp4: yes
>
> It would be interesting to see if L3 dhcp starts to work if one does:
>
> $ sudo mkdir -p /etc/systemd/network/10-netplan-enc8f00.network.d
> $ cat <<EOF | sudo tee -a
> /etc/systemd/network/10-netplan-enc8f00.network.d/30-request-broadcast.conf
> [DHCPv4]
> RequestBroadcast=yes
> EOF
>
> $ sudo networkctl reconfigure enc8f00
>
> (or chzdev -d 0.0.8f00; chzdev -e 0.0.8f00 or reboot, whatever is easier to
> make networkd force renew).

Thank you xnox. I confirm that this works with chzdev -d/-e and with reboot.
@Asha, this is a better solution for you.

------- Comment From <email address hidden> 2021-02-25 10:36 EDT-------
(In reply to comment #26)
> My preference would be to fix networkd, if that fails netplan, and isc-dhcp
> only if there is syntax to online the device in the right l2/l3 state via
> kernel cmdline and that one needs to complete install over it.
>
> For example, does automatic chzdev device enablement provides
> autoconfiguration for hipersockets in l3? in that case it would be neat for
> ip=dhcp to just do the right thing.
>
Yes, 'chzdev -e' defaults to Layer3 unless you explicitely specify 'chzdev -e layer2=1'. Note that chzdev creates a udev rule to make this setting persistent.

> Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3 interfaces
> be good enough in networkd?
Yes, that sounds good.