The current fad is to use random MAC addresses. I want anything that is "infrastructure" to have unique and stable MAC addresses, so that DHCP
can give them stable IP addresses. My Pi4 runs Fedora (which is very
stable on it except for the GUI), but it seems to always come up with randomized MAC addresses. Does it not HAVE a hardware MAC address?
And if it has one, where do I tell Fedora to use it?
Oh. its network manager that does it
On Fri, 13 Sep 2024 16:49:58 +0100, The Natural Philosopher wrote:
Oh. its network manager that does it
I disable NetworkManager on machines I consider “servers” or “infrastructure”. Then I manually configure the network interfaces.
On 9/13/2024 6:37 PM, Lawrence D'Oliveiro wrote:
On Fri, 13 Sep 2024 16:49:58 +0100, The Natural Philosopher wrote:
Oh. its network manager that does it
I disable NetworkManager on machines I consider “servers” or
“infrastructure”. Then I manually configure the network interfaces.
So how do I manually configure the ethernet port to use the hardware MAC address?
On Sat, 14 Sep 2024 08:37:58 -0700, Lars Poulsen wrote:
On 9/13/2024 6:37 PM, Lawrence D'Oliveiro wrote:
On Fri, 13 Sep 2024 16:49:58 +0100, The Natural Philosopher wrote:
Oh. its network manager that does it
I disable NetworkManager on machines I consider “servers” or
“infrastructure”. Then I manually configure the network interfaces.
So how do I manually configure the ethernet port to use the hardware MAC
address?
Every NIC has a built-in address, which it should default to.
Or, a quick look at the docs <https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
On 9/14/2024 3:31 PM, Lawrence D'Oliveiro wrote:
On Sat, 14 Sep 2024 08:37:58 -0700, Lars Poulsen wrote:
On 9/13/2024 6:37 PM, Lawrence D'Oliveiro wrote:
On Fri, 13 Sep 2024 16:49:58 +0100, The Natural Philosopher wrote:So how do I manually configure the ethernet port to use the hardware MAC >>> address?
Oh. its network manager that does it
I disable NetworkManager on machines I consider “servers” or
“infrastructure”. Then I manually configure the network interfaces. >>>
Every NIC has a built-in address, which it should default to.
Or, a quick look at the docs
<https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
Not quite responsive:
1) I do not want to invent a MAC address, I want to tell it to use the manufacturer's supposedly unique default address AFTER the OS/driver/network-manager/whatever has already wiped it out during the
boot process. Your command example assumes that I know what it is.
2)As you can see in the subject line, I am running Fedora, not
rasp(b)ian. Even if Fedora's GUI does not work on the RP4, I would
rather run headless than have to learn Debian system management after a decade of living in RedHat world.
Or, a quick look at the docs <https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
... I am running Fedora, not rasp(b)ian.
On Sat, 14 Sep 2024 22:31:58 -0000 (UTC), I wrote:
Or, a quick look at the docs
<https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
Actually, I think it might be
ip link set «device» macaddr ...
On Sun, 15 Sep 2024 22:08:07 -0000 (UTC), I wrote:
On Sat, 14 Sep 2024 22:31:58 -0000 (UTC), I wrote:
Or, a quick look at the docs
<https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
Actually, I think it might be
ip link set «device» macaddr ...
No, it is in fact the first form. Note that the link must be down before
you can change its MAC address.
Also if you set this to a non-default value, “ip link show” will show that
default value as the “permaddr”. So you can easily set it back to that.
On 9/14/2024 3:31 PM, Lawrence D'Oliveiro wrote:
On Sat, 14 Sep 2024 08:37:58 -0700, Lars Poulsen wrote:
On 9/13/2024 6:37 PM, Lawrence D'Oliveiro wrote:
On Fri, 13 Sep 2024 16:49:58 +0100, The Natural Philosopher wrote:So how do I manually configure the ethernet port to use the hardware MAC >>> address?
Oh. its network manager that does it
I disable NetworkManager on machines I consider “servers” or
“infrastructure”. Then I manually configure the network interfaces. >>>
Every NIC has a built-in address, which it should default to.
Or, a quick look at the docs
<https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
Not quite responsive:
1) I do not want to invent a MAC address, I want to tell it to use the manufacturer's supposedly unique default address AFTER the OS/driver/network-manager/whatever has already wiped it out during the
boot process. Your command example assumes that I know what it is.
2)As you can see in the subject line, I am running Fedora, not
rasp(b)ian. Even if Fedora's GUI does not work on the RP4, I would
rather run headless than have to learn Debian system management after a decade of living in RedHat world.
Running headless, using ssh to login, I cannot use an interactiveYes you can.
command to do this.
somewhere under /etc?Yes.
And the difference between raspian (a Debian derivative) and Fedora
(which uses systemd) *does* make a difference.
Are you just trolling?
The current fad is to use random MAC addresses. I want anything that is "infrastructure" to have unique and stable MAC addresses, so that DHCP
can give them stable IP addresses. My Pi4 runs Fedora (which is very
stable on it except for the GUI), but it seems to always come up with randomized MAC addresses. Does it not HAVE a hardware MAC address?
And if it has one, where do I tell Fedora to use it?
On 9/15/2024 4:53 PM, Lawrence D'Oliveiro wrote:
On Sun, 15 Sep 2024 22:08:07 -0000 (UTC), I wrote:
On Sat, 14 Sep 2024 22:31:58 -0000 (UTC), I wrote:
Or, a quick look at the docs
<https://manpages.debian.org/8/ip-link.8.en.html> gives
ip link set «device» address «addr»
Actually, I think it might be
ip link set «device» macaddr ...
No, it is in fact the first form. Note that the link must be down before
you can change its MAC address.
Also if you set this to a non-default value, “ip link show” will show
that
default value as the “permaddr”. So you can easily set it back to that.
Running headless, using ssh to login, I cannot use an interactive
command to do this. Does this information live in a configuration file somewhere under /etc?
And the difference between raspian (a Debian derivative) and Fedora
(which uses systemd) *does* make a difference.
On 9/15/2024 9:36 PM, The Natural Philosopher wrote:
Unfortunately you are probably the only one here that is using RedHat
on a Pi.
You may well be right about that.
AFAIK, ethernet defaults to 'one permanent MAC address' - its only
wifi that tends to switch around for security in public wifi spaces.
Have you actually checked to see if you are getting ethernet
randomisation?
ifconfig -a will display it
Thank you for an actually useful suggestion. I had forgotten to check
that and just assumed that was the cause of a change in IP address.
Unfortunately you are probably the only one here that is using RedHat on
a Pi.
AFAIK, ethernet defaults to 'one permanent MAC address' - its only wifi
that tends to switch around for security in public wifi spaces.
Have you actually checked to see if you are getting ethernet randomisation? ifconfig -a will display it
On 16/09/2024 23:30, Lars Poulsen wrote:
On 9/15/2024 9:36 PM, The Natural Philosopher wrote:Hang on a minute.... IP address or MAC address?
Unfortunately you are probably the only one here that is using RedHat
on a Pi.
You may well be right about that.
AFAIK, ethernet defaults to 'one permanent MAC address' - its only
wifi that tends to switch around for security in public wifi spaces.
Have you actually checked to see if you are getting ethernet
randomisation?
ifconfig -a will display it
Thank you for an actually useful suggestion. I had forgotten to check
that and just assumed that was the cause of a change in IP address.
IP address may change any time you connect to the DHCP server (if you
are using DHCP).
ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
*inet 192.168.0.101* netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::9a2:3187:4600:cfc1 prefixlen 64 scopeid 0x20<link>
*ether d8:3a:dd:85:22:b1* txqueuelen 1000 (Ethernet)
RX packets 335547 bytes 39007037 (37.2 MiB)
RX errors 0 dropped 158 overruns 0 frame 0
TX packets 348598 bytes 256465720 (244.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
This is a statically configured *IP address* on a Pi 4B
I assume the Ethernet *MAC* address is always the same.
Looking up the MAC address online:
Result:
MAC Address Prefix Manufacturer
D83ADD Raspberry Pi Trading Ltd
My DHCP server on that network has a list of known hosts (known by their
MAX address) and what their IP address should be. Hence my annoyance
when employees with iPhones have randomized MAC addresses.
My DHCP server on that network has a list of known hosts (known by their
MAX address) and what their IP address should be. Hence my annoyance
when employees with iPhones have randomized MAC addresses.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 175:06:56 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,724 |