On Tuesday, 28 May 2024 19:02:09 BST Dale wrote:
> Grant Edwards wrote:
> > On 2024-05-28, Dale wrote:
> >> Grant Edwards wrote:
> >>> On 2024-05-21, Dale wrote:
> > Here's my udev rules file that defines my network interface names
> > for the machine I'm on at the moment:
> >
>
Grant Edwards wrote:
> On 2024-05-28, Dale wrote:
>> Grant Edwards wrote:
>>> On 2024-05-21, Dale wrote:
>>>
> Here's my udev rules file that defines my network interface names
> for the machine I'm on at the moment:
>
>
On 2024-05-28, Dale wrote:
> Grant Edwards wrote:
>> On 2024-05-21, Dale wrote:
>>
Here's my udev rules file that defines my network interface names
for the machine I'm on at the moment:
--/etc/udev/rules.d/70-my-persistent-net.rules---
Grant Edwards wrote:
> On 2024-05-21, Dale wrote:
>
>>> Here's my udev rules file that defines my network interface names
>>> for the machine I'm on at the moment:
>>>
>>> --/etc/udev/rules.d/70-my-persistent-net.rules---
>>> SUBSYSTEM=="net", ACTION=="add",
On 2024-05-21, Dale wrote:
>> Here's my udev rules file that defines my network interface names
>> for the machine I'm on at the moment:
>>
>> --/etc/udev/rules.d/70-my-persistent-net.rules---
>> SUBSYSTEM=="net", ACTION=="add",
Grant Edwards wrote:
> On 2024-05-21, Dale wrote:
>
>
>>> If you want consisent network device names (even when you change
>>> hardware), you need to either
>>>
>>> 1. create udev rules that assign device names based on MAC addresses.
>>>
>>> 2. use a network configuration subsystem that
On 2024-05-21, Dale wrote:
>> If you want consisent network device names (even when you change
>> hardware), you need to either
>>
>> 1. create udev rules that assign device names based on MAC addresses.
>>
>> 2. use a network configuration subsystem that assigns device names
>> and
Grant Edwards wrote:
> On 2024-05-21, Dale wrote:
>
>> So they both show up. When I try to start the network, it says:
>>
>> ERROR: Interface enp3s0 does not exist.
> Are you sure the network interface name hasn't changed? What does
> "ifconfig -a" or "ip addr" show?
>
> After booting up, what
On 2024-05-21, Dale wrote:
> So they both show up. When I try to start the network, it says:
>
> ERROR: Interface enp3s0 does not exist.
Are you sure the network interface name hasn't changed? What does
"ifconfig -a" or "ip addr" show?
After booting up, what does "dmesg | grep enp" show?
>
On Tue, 21 May 2024 06:51:51 -0400, Rich Freeman wrote:
> I usually stick e*
> in my networkd config for the device name on single-NIC hosts. If you
> have multiple NICs then I maybe there is a better way to go about it -
> maybe there is a network manager that can use more data from the NIC
>
Dale:
...
> ERROR: Interface enp3s0 does not exist.
> Ensure that you have loaded the correct kernel module for your hardware.
...
Do:
cat /proc/net/dev
Regards,
/Karl Hammar
On Tue, May 21, 2024 at 6:38 AM Dale wrote:
>
> So, I created a new link to slot 4. The network came up. So,
> basically, it changed names as you suggested. I thought the purpose of
> the enp* names was that they are consistent. Adding or removing cards
> wouldn't change the names of cards,
Grant Edwards wrote:
> On 2024-05-20, Dale wrote:
>
> A 3.0 card is supposed to work fine in a 2.0 slot.
>
>> You, or anyone, have any idea why that card would kill my network?
>> I suspect the card itself is fine. It did see the drive. I just
>> need the internet to work since it may be used
On 2024-05-20, Dale wrote:
A 3.0 card is supposed to work fine in a 2.0 slot.
> You, or anyone, have any idea why that card would kill my network?
> I suspect the card itself is fine. It did see the drive. I just
> need the internet to work since it may be used in a NAS rig.
Is it causing
14 matches
Mail list logo
