13 Apr
2020
13 Apr
'20
9:18 a.m.
Hello,
I am wanting to upgrade my server from Debian 9 to Debian 10. I have done this on other
systems without problems but have a question about the Bitfolk VM and network interface
name.
For Debian 10 upgrades the legacy name definition file is not supported [1] :
/etc/udev/rules.d/70-persistent-net.rules
I define eth0 here using MAC i.e.
SUBSYSTEM=="net", DRIVERS=="?*",
ATTR{address}=="00:16:3e:1b:b2:db", NAME="eth0"
I have no files in /etc/systemd/network/.
Per [1], using udevadm to find the udev name :
# udevadm test-builtin net_id /sys/class/net/eth0 2>/dev/null
ID_NET_NAME_MAC=enx00163e1bb2db
ID_OUI_FROM_DATABASE=Xensource, Inc.
it is wanting to use "enx00163e1bb2db".
So, to get started I was going to :
1) Disable the 70-persistent-net.rules file
2) Change all occurrences of "eth0" to "enx00163e1bb2db" using :
grep -r eth0 /etc
3) Reboot
Is this correct? Or is their a better way that the Debian 9 to 10 upgrade can cope with
(maybe with a nicer interface name)?
Once I am happy all works using this interface name, I can think about the Debian 10
upgrade itself.
Many Thanks,
[1] https://www.debian.org/releases/stable/amd64/release-notes/ch-information.e…
--
Alastair Sherringham
http://www.sherringham.net
13 Apr
13 Apr
9:36 a.m.
Hi Alastair,
On Mon, Apr 13, 2020 at 10:18:32AM +0100, Alastair Sherringham wrote:
I am wanting to upgrade my server from Debian 9 to
Debian 10. I
have done this on other systems without problems but have a
question about the Bitfolk VM and network interface name.
Since the MAC addresses and interface names are fixed in the config
on BitFolk's side, interface names are stable inside the VMs and
eth0 will always be eth0.
I've installed Debian 10 in BitFolk VMs many times and upgraded to
it many times and it's never changed away from eth0.
Here's something I wrote to another customer who asked:
Based on a Xen guest's device directory in sysfs being something
like:
/sys/devices/vif-0/net/eth0/
…then on second look it seems that here:
https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id…
…it just doesn't fall into any of the existing categories except
for MAC-based, which as you say is disabled by default.
Specifically, it is not considered PCI because it's on a bus
called "vif-0" or whatever, not "pci".
I suppose it is possible that in future Xen could change
something here, or udev could add an extra test.
If you are worried about this then I think you could do one of
several things, such as:
- Use the net.ifnames=0 kernel command line option to
disable any future renaming.
- Enable the MAC-based device naming; your MAC address will not
change for the life of the account.
- Add a udev rule to rename based on MAC address to something
you choose.
So I don't think you need to do anything at all.
On bare metal or a KVM guest it would probably be a different story.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
10:53 a.m.
Thanks Andy.
OK, I'll just have a go at the upgrade as-is and see how it goes. If anything breaks
and I can't fix it, I'll ask for advice. I hope to try this soon but not today.
Cheers,
Alastair
On Mon, 13 Apr 2020, at 10:36 AM, Andy Smith wrote:
Hi Alastair,
On Mon, Apr 13, 2020 at 10:18:32AM +0100, Alastair Sherringham wrote:
--
Alastair Sherringham
http://www.sherringham.net
I am wanting to upgrade my server from Debian 9
to Debian 10. I
have done this on other systems without problems but have a
question about the Bitfolk VM and network interface name.
Since the MAC addresses and interface names are fixed in the config
on BitFolk's side, interface names are stable inside the VMs and
eth0 will always be eth0.
I've installed Debian 10 in BitFolk VMs many times and upgraded to
it many times and it's never changed away from eth0.
Here's something I wrote to another customer who asked:
Based on a Xen guest's device directory in sysfs being something
like:
/sys/devices/vif-0/net/eth0/
…then on second look it seems that here:
https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id…
…it just doesn't fall into any of the existing categories except
for MAC-based, which as you say is disabled by default.
Specifically, it is not considered PCI because it's on a bus
called "vif-0" or whatever, not "pci".
I suppose it is possible that in future Xen could change
something here, or udev could add an extra test.
If you are worried about this then I think you could do one of
several things, such as:
- Use the net.ifnames=0 kernel command line option to
disable any future renaming.
- Enable the MAC-based device naming; your MAC address will not
change for the life of the account.
- Add a udev rule to rename based on MAC address to something
you choose.
So I don't think you need to do anything at all.
On bare metal or a KVM guest it would probably be a different story.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
*Attachments:*
* signature.asc
30 Apr
30 Apr
11:57 a.m.
I upgraded my server to Debian 10 Buster yesterday and all went smoothly. The ethernet
device stayed as "eth0" and didn't really need to worry about anything. So,
thanks for helping out.
Cheers, Alastair
On Mon, 13 Apr 2020, at 11:53 AM, Alastair Sherringham wrote:
Thanks Andy.
OK, I'll just have a go at the upgrade as-is and see how it goes. If anything breaks
and I can't fix it, I'll ask for advice. I hope to try this soon but not today.
Cheers,
Alastair
On Mon, 13 Apr 2020, at 10:36 AM, Andy Smith wrote:
--
Alastair Sherringham
http://www.sherringham.net
Hi Alastair,
On Mon, Apr 13, 2020 at 10:18:32AM +0100, Alastair Sherringham wrote:
--
Alastair Sherringham
http://www.sherringham.net
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
I am wanting to upgrade my server from Debian 9
to Debian 10. I
have done this on other systems without problems but have a
question about the Bitfolk VM and network interface name.
Since the MAC addresses and interface names are fixed in the config
on BitFolk's side, interface names are stable inside the VMs and
eth0 will always be eth0.
I've installed Debian 10 in BitFolk VMs many times and upgraded to
it many times and it's never changed away from eth0.
Here's something I wrote to another customer who asked:
Based on a Xen guest's device directory in sysfs being something
like:
/sys/devices/vif-0/net/eth0/
…then on second look it seems that here:
https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id…
…it just doesn't fall into any of the existing categories except
for MAC-based, which as you say is disabled by default.
Specifically, it is not considered PCI because it's on a bus
called "vif-0" or whatever, not "pci".
I suppose it is possible that in future Xen could change
something here, or udev could add an extra test.
If you are worried about this then I think you could do one of
several things, such as:
- Use the net.ifnames=0 kernel command line option to
disable any future renaming.
- Enable the MAC-based device naming; your MAC address will not
change for the life of the account.
- Add a udev rule to rename based on MAC address to something
you choose.
So I don't think you need to do anything at all.
On bare metal or a KVM guest it would probably be a different story.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
*Attachments:*
* signature.asc
1799
days inactive
1816
days old
3 comments
2 participants
participants (2)
-
Alastair Sherringham -
Andy Smith