Ok I have found out from my provider that their MAC addresses are static and
using the MAC address is how they recommend sorting out this issue.
They mentioned the issue stems from the fact they cannot control which order
Openstack adds the NICs to the VM, which in turn can cause the PCI address to
change, and the kernel will rename devices based on that.
As such, would you think it would be reasonable to manually create this file or
could I modify the existing generator file or add a new one to automatically
add it in?
Regards
Michael Knill
From: Michael Knill <michael.kn...@ipcsolutions.com.au>
Date: Thursday, 28 August 2025 at 3:39 pm
To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] When is
'/etc/udev/rules.d/70-persistent-net.rules' created
Thanks Lonnie
I will confirm if the MAC’s change or not from the provider.
Regards
Michael Knill
From: Lonnie Abelbeck <li...@lonnie.abelbeck.com>
Date: Thursday, 28 August 2025 at 12:08 am
To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] When is
'/etc/udev/rules.d/70-persistent-net.rules' created
Michael,
If the VM host MACs are changing from reboot to reboot, the
70-persistent-net.rules must not be generated, as that would cause problems.
Single NIC would not matter in this case, but multiple NICs are at the mercy of
the VM host consistently maintaining the NIC order.
I presume you are not seeing a problem with an OpenStack VM host, but you are
just thinking ahead.
FYI, here are some sample guest VM instances:
## Proxmox KVM (70-persistent-net.rules generated)
pbx-pve ~ # mac2vendor bc:24:11
Proxmox Server Solutions GmbH
## Linode KVM (no 70-persistent-net.rules)
linode ~ # mac2vendor f2:3c:91
Randomized MAC Address
## Vultr KVM (no 70-persistent-net.rules)
vultr ~ # mac2vendor 56:00:01
Randomized MAC Address
## UTM QEMU (no 70-persistent-net.rules)
pbx-macos ~ # mac2vendor ee:df:27
Randomized MAC Address
Both Proxmox KVM and UTM QEMU can define the MAC address in the configuration,
as such it is static.
Both Linode KVM and Vultr KVM interface MACs do not change from reboot to
reboot.
Lonnie
> On Aug 27, 2025, at 2:09 AM, Michael Knill
> <michael.kn...@ipcsolutions.com.au> wrote:
>
> Thanks Lonnie
>
> So considering my MAC addresses are fa:16:3e:* could I comment out the
> following line from this file and reboot:
>
> # do not use "locally administered" MAC address
> # ENV{MATCHADDR}=="?[2367abef]:*", ENV{MATCHADDR}=""
>
> I would only edit for multi interface VM’s which are currently only our
> softswitch servers.
>
> What do you think? Or I could just build a manual one?
>
> Regards
> Michael Knill
> From: Lonnie Abelbeck <li...@lonnie.abelbeck.com>
> Date: Wednesday, 27 August 2025 at 10:27 am
> To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
> Subject: Re: [Astlinux-users] When is
> '/etc/udev/rules.d/70-persistent-net.rules' created
>
> Hi Michael,
>
> That [1] file is generated by this udev rule:
> --
> /usr/lib/udev/rules.d/75-persistent-net-generator.rules
> --
> Not trivial to follow, but you can see how some interfaces are skipped.
>
> For many VM guests, no [1] file is auto-generated.
>
> None of my KVM Hypervisor Guest VMs have a [1] file. Though in all cases the
> first interface is "eth0".
>
> I have never needed it, but you could add a manual [1] file (with specific
> MAC addresses) if needed.
>
> Lonnie
>
> [1] /etc/udev/rules.d/70-persistent-net.rules
>
>
>
> > On Aug 26, 2025, at 6:54 PM, Michael Knill
> > <michael.kn...@ipcsolutions.com.au> wrote:
> >
> > Hi All
> >
> > Im just wondering when '/etc/udev/rules.d/70-persistent-net.rules’ is
> > created. I have Astlinux in an OpenStack VM and the NIC assignments appear
> > to be pretty random and Im concerned that they could change on a reboot.
> >
> > I looked for this file but I could not find it:
> > 12810-IPCPROD-SSFE1 kd # ls -la /etc/udev/rules.d/
> > total 24
> > drwxrwxr-x 1 root root 120 Jul 5 2023 .
> > drwxrwxr-x 1 root root 80 Jul 5 2023 ..
> > -rw-r--r-- 1 root root 11589 Jul 5 2023 62-nut-usbups.rules
> > -rw-r--r-- 1 root root 753 Jul 5 2023 dahdi.rules
> > -rw-r--r-- 1 root root 185 Jul 5 2023 usbtty.rules
> > -rw-r--r-- 1 root root 531 Jul 5 2023 xpp.rules
> >
> > I thought this file was auto created as I usually have to delete it if I
> > change NIC’s so wondering how it all works?
> >
> > Regards
> > Michael Knill
> > Managing Director
> > D: +61 2 6189 1360
> > P: +61 2 6140 4656
> > E: michael.kn...@ipcsolutions.com.au
> > W: ipcsolutions.com.au
> > <image001.png>Smarter Business Communications
> > _______________________________________________
> > Astlinux-users mailing list
> > Astlinux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> > pay...@krisk.org.
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
