You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2020-01-17 17:48:14
- rolfie
- Member
- Registered: 2017-11-25
- Posts: 1,173
NIC replacement issues
Got a M5A99X EVO R2 board running ASCII. The onboard NIC (Realtek) suddenly stopped working. I had an Intel GBit NIC around I did install in the PC and disabled the onboard chip in the BIOS. This is no more detected by lspci.
But now ASCII insists on replacing eth0 with eth1. Had to modify the interfaces settings.
Where do I need to look to stop ASCII/(eudev?) doing this?
Thnaks, rolfie
Online
#2 2020-01-17 18:14:02
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: NIC replacement issues
Remove /etc/udev/rules.d/70-persistent-net.rules
Brianna Ghey — Rest In Power
Offline
#3 2020-01-18 10:42:50
- rolfie
- Member
- Registered: 2017-11-25
- Posts: 1,173
Re: NIC replacement issues
Thanks, the contents pointed to the Realtek NIC. Renamed the file and everything is back to eth0.
I have the feeling that FF is resolving adresses very slowly now. Is there an easy way to generate a new rule for the Intel NIC?
Thanks, rolfie
Online
#4 2020-01-18 10:58:10
- Head_on_a_Stick
- Member
- From: London
- Registered: 2019-03-24
- Posts: 3,125
- Website
Re: NIC replacement issues
I have the feeling that FF is resolving adresses very slowly now.
You're probably imagining it (or it's purely coincidental). Renaming the interface shouldn't affect address resolution.
Installing and configuring unbound will provide a caching nameserver that should (slightly) speed up resolution for repeated attempts.
EDIT: remove the file rather than rename it.
Last edited by Head_on_a_Stick (2020-01-18 10:59:24)
Brianna Ghey — Rest In Power
Offline
Pages: 1
