enp1s0 changed to eno0

[engineermdr]

My home experienced a power outage this morning. I have a dedicated small Atom computer I use as a firewall/router. It powered back up when the power was restored, but no internet for the internal network.

Problem 1: I discovered the internal network port enp1s0 is now named eno0. When did that happen? Why did that happen? My kernel is 5.10.93 compiled Jan 31, 2022, and I'm almost certain I've rebooted since installing it, so I doubt it's the kernel. I did have to transition away from eudev, was that it?

So, I fix /etc/conf.d/net and use the new name and I get the net device up, but still not able to contact anything on the internal network.

Problem 2: Since this a firewall, iptables was configured for the old device name. Another fix there.

An hour later, I finally have networking again (we won't talk about one of the other computers that won't even post now ). So now I want to avoid this ever again. I think I have 3 options:

1. Prevent the renaming and revert to eth1 and eth0. However, I'm worried they might switch places someday.
2. Force the renaming somehow myself, if that's possible and I believe it is
3. Toss udev and use static /dev - nothing ever changes on this machine and it would be quite reasonable to set up and forget

Thoughts? #2 seems like the safest with the least effort, but if the process to force the naming changes, then I'm screwed again. I'd like to use #1 if my concerned aren't warranted. And #3 would be the most permanent and take me back to the early days of linux, but likely the most work.

[Hu]

[engineermdr]

Yes, the uninterruptible power supply is an excellent suggestion. Thanks, I will look into that.

I should probably also get into the habit of rebooting immediately after updates on this important machine so I'm not so surprised when reboots do happen - they are always at the worst time.