Skip to content

Persistent DHCP identifier fix#39

Merged
edigaryev merged 1 commit intomainfrom
persistent-dhcp-identifier-fix
Oct 8, 2024
Merged

Persistent DHCP identifier fix#39
edigaryev merged 1 commit intomainfrom
persistent-dhcp-identifier-fix

Conversation

@edigaryev
Copy link
Copy Markdown
Collaborator

Since we disable all data sources above to speed-up the booting process, we need to somehow provide our DHCP identifier fix from "network-config".

Otherwise the fix will only be visible on the initial VM boot, which I was testing #38 on.

@edigaryev edigaryev merged commit a2ea637 into main Oct 8, 2024
@edigaryev edigaryev deleted the persistent-dhcp-identifier-fix branch October 8, 2024 15:02
nirs added a commit to nirs/lima that referenced this pull request Jan 18, 2025
On macOS the DHCP server use the DUID+IAID for both hw_address and
identifier, which makes it harder to discover the machine mac address by
looking up leases in /var/db/dhcpd_leases. It seems that this issue
started in macOS 15.

    % cat /var/db/dhcpd_leases
    {
            name=lima-test
            ip_address=192.168.105.4
            hw_address=ff,5c:bb:eb:5e:0:2:0:0:ab:11:72:3e:92:23:14:1d:a7:ba
            identifier=ff,5c:bb:eb:5e:0:2:0:0:ab:11:72:3e:92:23:14:1d:a7:ba
            lease=0x678b8aee
    }

With this change the record is created using the mac address:

    % cat /var/db/dhcpd_leases
    {
            name=lima-test
            ip_address=192.168.105.4
            hw_address=1,52:55:55:ba:82:85
            identifier=1,52:55:55:ba:82:85
            lease=0x678b90c6
    }

The fix is based on:
cirruslabs/linux-image-templates#39.

Minikube have the similar (networkd specific) fix:
kubernetes/minikube#3572

Signed-off-by: Nir Soffer <nirsof@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants