View previous topic :: View next topic |
Author |
Message |
FastTurtle Guru

Joined: 03 Sep 2002 Posts: 516 Location: Flakey Shake & Bake Caliornia, USA
|
Posted: Sat Apr 12, 2025 1:41 pm Post subject: missing eth0 in init.d Solved |
|
|
Following the handbook and at the netowkr stage - page lists using dhcp for most as I fo but /etc/init.d has no eth0 or eth1 entries to ln net.lo to. Seems tat a step was missed in the handbook where we used to ensure you netowkr would work/
Any reminders as to how to fix?
Thanks to Neddy for the reminder but had to change to what ifconfig reported
eno2 as the interface _________________ AsRock Rack Rome8-2t
AMD Epyc 7282 CPU
256GB of ECC memory
Team Group 1TB Sata M2 for boot
Last edited by FastTurtle on Sat Apr 12, 2025 4:34 pm; edited 1 time in total |
|
Back to top |
|
 |
grknight Retired Dev

Joined: 20 Feb 2015 Posts: 2103
|
Posted: Sat Apr 12, 2025 2:26 pm Post subject: |
|
|
You mean like Handbook - netifrc - Configuring network where it creates the link from net.lo to net.eth0 before adding it?
You would replace eth0 with the real interface name on a system and/or repeat for additional interfaces.
When using netifrc, do not use other networking scripts in the runlevels (rc-update). Do not add dhcpcd. Do not add NetworkManager. This goes for most networking tools where you are having netifrc administer the interface. Two tools will just conflict and cause issues. |
|
Back to top |
|
 |
FastTurtle Guru

Joined: 03 Sep 2002 Posts: 516 Location: Flakey Shake & Bake Caliornia, USA
|
Posted: Sat Apr 12, 2025 3:28 pm Post subject: |
|
|
Just above tat they indicate install dhcdcd, which I did. In following the handbook, I also installed netifrc but the issue is with linking net.lo to eth0 as I don't have any eth? entries at all.
We used to have to do something by copying an eth entrie to init.d for wired connections so if that's still useable, it means someone boobied badly as they dropped a step. _________________ AsRock Rack Rome8-2t
AMD Epyc 7282 CPU
256GB of ECC memory
Team Group 1TB Sata M2 for boot |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55162 Location: 56N 3W
|
Posted: Sat Apr 12, 2025 4:12 pm Post subject: |
|
|
FastTurtle,
net.lo runs as whatever it is called as.
Code: | cd /etc/init.d
ln -s net.lo net.eth0 |
gives you /etc/init.d/net.eth0, so that it can be added to the default runlevel
Copying net.lo was always wrong as the copies would never be updated. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
grknight Retired Dev

Joined: 20 Feb 2015 Posts: 2103
|
Posted: Sat Apr 12, 2025 4:15 pm Post subject: |
|
|
Please only choose one method. The different sections are different options for networking.
Please also read things completely not just copy commands. Then, you would have seen: Code: | Note
This assumes that the network interface will be called eth0. This is, however, very system dependent.
It is recommended to assume that the interface is named the same as the interface name when booted
from the installation media if the installation media is sufficiently recent. More information can be found in the Network interface naming section. |
|
|
Back to top |
|
 |
FastTurtle Guru

Joined: 03 Sep 2002 Posts: 516 Location: Flakey Shake & Bake Caliornia, USA
|
Posted: Sat Apr 12, 2025 4:21 pm Post subject: |
|
|
Neddy: the problem is, when I use that command, it fails with no eth0 found.
checking iifconfig and it shows eno2, so I'll give that a try
What has me baffelled is absolutely no entries other then tun in /dev/net and nothing at allfor tno/eth0
thanks Neddy for the reminder. Had to use eno2 as the interface and it should now work when I reboot _________________ AsRock Rack Rome8-2t
AMD Epyc 7282 CPU
256GB of ECC memory
Team Group 1TB Sata M2 for boot |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55162 Location: 56N 3W
|
Posted: Sat Apr 12, 2025 4:35 pm Post subject: |
|
|
FastTurtle,
should work but it needs to be net.eth0, not just eth0.
eth0 is a kernel assigned name. You probably have persistent device renaming, so the interface will be renamed
You need net.<new_name>
Useto see all your real physical interfaces, regardless of them being up or not. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
|