12:58 p.m.
Just upgraded to FC31. It's a multihomed machine used as a router. One
interface "external" goes to the cable modem. The other interface
"internal" goes to a switch.
cat /etc/sysconfig/network-scripts/ifcfg-external | grep -v \#
TYPE=Ethernet
BOOTPROTO=dhcp
DEVICE=external
ONBOOT=yes
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
USERCTL=no
HWADDR=50:7B:9D:0B:8A:AB
NAME=external
UUID=02b123a7-baea-20e2-051e-8a9ec27cc44a
cat /etc/sysconfig/network-scripts/ifcfg-internal | grep -v \#
DEVICE=internal
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.10.11.251
PREFIX=24
DEFROUTE=no
IPV4_FAILURE_FATAL=no
IPV6INIT=no
PEERDNS=no
USERCTL=no
UUID=ef5b0746-2604-b21f-c03e-00556aef68fc
HWADDR=00:0e:c6:dc:01:aa
But neither interface is found on boot:
enp0s20u3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:0e:c6:dc:01:aa txqueuelen 1000 (Ethernet)
RX packets 2573 bytes 172174 (168.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet)
RX packets 2581 bytes 180221 (175.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 765 bytes 81440 (79.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 765 bytes 81440 (79.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
even though the MAC adresses match. As do the UUID's:
nmcli connection show | grep ernal
external 02b123a7-baea-20e2-051e-8a9ec27cc44a ethernet --
System internal ef5b0746-2604-b21f-c03e-00556aef68fc ethernet --
enp0s20u3 is a USB interface that should be internal. If I unplug and
replug, naming works.
On boot:
kernel: asix 2-3:1.0 eth0: register 'asix' at usb-0000:00:14.0-3, ASIX
AX88772 USB 2.0 Ethernet, 00:0e:c6:dc:01:aa
kernel: usbcore: registered new interface driver asix
kernel: asix 2-3:1.0 enp0s20u3: renamed from eth0
then I unplug and plug:
kernel: asix 2-3:1.0 internal: renamed from enp0s20u3
kernel: asix 2-3:1.0 internal: link up, 100Mbps, full-duplex, lpa 0x45E1
That does not happen if I plug and unplug external, an ethernet cable.
BUT, what's really odd. I'm booting the Fc31 kernel:
kernel-5.3.11-300.fc31.x86_64
if I boot the same kernel, but FC30:
kernel-5.3.11-200.fc30.x86_64
IT WORKS !!
Any help appreciated.
sean
1:33 p.m.
New subject: Anyone using Anydesk or could test it ?
Hallo
is anyone using Anydesk or could test it ?
https://anydesk.com/en/downloads/linux
since the F31-updates during the last week I'm unable to work with
anydesk anymore.
Problem:
During the start of an connection a completely blank dialog box pops up.
Usually it's an dialog to allow the connection attempt on the remote box.
Connection between F31 => Windows works.
Connection between F31 <= Windows does not !
Connections between F31 <=> F31 do not !
It is sufficing to try a F31 connection to the *same* machine to see to
empty dialog box.
Does anyone know to debug this ?
Against which component should I fill a bug report ?
--
sixpack13
3:05 p.m.
New subject: Anyone using Anydesk or could test it ?
bad reply from me, please ignore !
7:09 a.m.
On 2019-11-26 19:58, Sean Darcy wrote:
On boot:
kernel: asix 2-3:1.0 eth0: register 'asix' at usb-0000:00:14.0-3, ASIX
AX88772 USB 2.0 Ethernet, 00:0e:c6:dc:01:aa
kernel: usbcore: registered new interface driver asix
kernel: asix 2-3:1.0 enp0s20u3: renamed from eth0
then I unplug and plug:
kernel: asix 2-3:1.0 internal: renamed from enp0s20u3
kernel: asix 2-3:1.0 internal: link up, 100Mbps, full-duplex, lpa 0x45E1
That does not happen if I plug and unplug external, an ethernet cable.
BUT, what's really odd. I'm booting the Fc31 kernel:
kernel-5.3.11-300.fc31.x86_64
if I boot the same kernel, but FC30:
kernel-5.3.11-200.fc30.x86_64
IT WORKS !!
Any help appreciated.
I've seen the same issue some time ago (but on Centos
7).
The basic problem is that interface renaming must happen correctly
in the initramfs, where you have to be sure the network configuration is fine;
that explains why a successive unplug/replug works.
In my case there was no NetworkManager involved, just the old "service network
start"
things, with configs in /etc/sysconfig/network-scripts/ifcfg*
No idea what can have happened between those two kernels, apart
from indeed having different intiramfs content.
You should try extracting the two initramfs and doing a comparison.
Something like:
[root@router boot]# cat z_decompress.sh
#!/bin/bash
set -e
initramfs=$1
/usr/lib/dracut/skipcpio $initramfs >z_decomp_$initramfs.cpio.gz
rm -Rf z_dir_$initramfs
mkdir z_dir_$initramfs
cd z_dir_$initramfs
gunzip <../z_decomp_$initramfs.cpio.gz | cpio -i
Best regards.
--
Roberto Ragusa mail at robertoragusa.it
9:42 a.m.
On 11/27/19 8:09 AM, Roberto Ragusa wrote:
On 2019-11-26 19:58, Sean Darcy wrote:
> On boot:
> kernel: asix 2-3:1.0 eth0: register 'asix' at usb-0000:00:14.0-3, ASIX
> AX88772 USB 2.0 Ethernet, 00:0e:c6:dc:01:aa
> kernel: usbcore: registered new interface driver asix
> kernel: asix 2-3:1.0 enp0s20u3: renamed from eth0
>
> then I unplug and plug:
> kernel: asix 2-3:1.0 internal: renamed from enp0s20u3
> kernel: asix 2-3:1.0 internal: link up, 100Mbps, full-duplex, lpa 0x45E1
>
> That does not happen if I plug and unplug external, an ethernet cable.
>
> BUT, what's really odd. I'm booting the Fc31 kernel:
>
> kernel-5.3.11-300.fc31.x86_64
>
> if I boot the same kernel, but FC30:
>
> kernel-5.3.11-200.fc30.x86_64
>
> IT WORKS !!
>
> Any help appreciated.
I've seen the same issue some time ago (but on Centos 7).
The basic problem is that interface renaming must happen correctly
in the initramfs, where you have to be sure the network configuration is
fine;
that explains why a successive unplug/replug works.
In my case there was no NetworkManager involved, just the old "service
network start"
things, with configs in /etc/sysconfig/network-scripts/ifcfg*
No idea what can have happened between those two kernels, apart
from indeed having different intiramfs content.
You should try extracting the two initramfs and doing a comparison.
Something like:
[root@router boot]# cat z_decompress.sh
#!/bin/bash
set -e
initramfs=$1
/usr/lib/dracut/skipcpio $initramfs >z_decomp_$initramfs.cpio.gz
rm -Rf z_dir_$initramfs
mkdir z_dir_$initramfs
cd z_dir_$initramfs
gunzip <../z_decomp_$initramfs.cpio.gz | cpio -i
Best regards.
Thanks, but that's beyond my kernel skill set.
Here's what I tried, all without success:
1. put 2 .link files is /etc/systemd/network
ls /etc/systemd/network
10-external.link 10-internal.link
cat /etc/systemd/network/*
[Match]
MACAddress=50:7b:9d:0b:8a:ab
[Link]
Name=external
[Match]
MACAddress=00:0e:c6:dc:01:aa
[Link]
Name=internal
2. put 70-persistent-net.rule in /etc/udev/rules.d
cat /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="50:7b:9d:0b:8a:ab",
NAME="external"
SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="00:0e:c6:dc:01:aa",
NAME="internal"
rebooted
One odd result of running udevadm test on the "external" interface:
enp1s0: Failed to rename network interface 2 from 'enp1s0' to
'external': Device or resource busy
There must be some trick here that I'm missing. What's the problem with
the FC31 kernel ?
sean
11:39 a.m.
I don't run FC31 but on all my other Fedora systems, I add net.ifnames=0 to the
kernel
command line /etc/default/grub:
GRUB_CMDLINE_LINUX="rd.md.uuid=41012be5:1df005d4:cfee0bd3:e112219a *net.ifnames=0*
rd.shell rd.timeout=65 consoleblank=600
rcu_nocbs=0-15"
Then regenerate the grub menu:
# legacy BIOS
grub2-mkconfig -o /boot/grub2/grub.cfg
I don' have but one EFI server:
# EFI BIOS
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Bill
On 11/27/2019 10:42 AM, sean darcy wrote:
On 11/27/19 8:09 AM, Roberto Ragusa wrote:
> On 2019-11-26 19:58, Sean Darcy wrote:
>
>> On boot:
>> kernel: asix 2-3:1.0 eth0: register 'asix' at usb-0000:00:14.0-3, ASIX
>> AX88772 USB 2.0 Ethernet, 00:0e:c6:dc:01:aa
>> kernel: usbcore: registered new interface driver asix
>> kernel: asix 2-3:1.0 enp0s20u3: renamed from eth0
>>
>> then I unplug and plug:
>> kernel: asix 2-3:1.0 internal: renamed from enp0s20u3
>> kernel: asix 2-3:1.0 internal: link up, 100Mbps, full-duplex, lpa 0x45E1
>>
>> That does not happen if I plug and unplug external, an ethernet cable.
>>
>> BUT, what's really odd. I'm booting the Fc31 kernel:
>>
>> kernel-5.3.11-300.fc31.x86_64
>>
>> if I boot the same kernel, but FC30:
>>
>> kernel-5.3.11-200.fc30.x86_64
>>
>> IT WORKS !!
>>
>> Any help appreciated.
> I've seen the same issue some time ago (but on Centos 7).
> The basic problem is that interface renaming must happen correctly
> in the initramfs, where you have to be sure the network configuration is fine;
> that explains why a successive unplug/replug works.
> In my case there was no NetworkManager involved, just the old "service network
start"
> things, with configs in /etc/sysconfig/network-scripts/ifcfg*
> No idea what can have happened between those two kernels, apart
> from indeed having different intiramfs content.
> You should try extracting the two initramfs and doing a comparison.
> Something like:
>
> [root@router boot]# cat z_decompress.sh
> #!/bin/bash
>
> set -e
>
> initramfs=$1
> /usr/lib/dracut/skipcpio $initramfs >z_decomp_$initramfs.cpio.gz
> rm -Rf z_dir_$initramfs
> mkdir z_dir_$initramfs
> cd z_dir_$initramfs
> gunzip <../z_decomp_$initramfs.cpio.gz | cpio -i
>
> Best regards.
>
Thanks, but that's beyond my kernel skill set.
Here's what I tried, all without success:
1. put 2 .link files is /etc/systemd/network
ls /etc/systemd/network
10-external.link 10-internal.link
cat /etc/systemd/network/*
[Match]
MACAddress=50:7b:9d:0b:8a:ab
[Link]
Name=external
[Match]
MACAddress=00:0e:c6:dc:01:aa
[Link]
Name=internal
2. put 70-persistent-net.rule in /etc/udev/rules.d
cat /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="50:7b:9d:0b:8a:ab", NAME="external"
SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="00:0e:c6:dc:01:aa", NAME="internal"
rebooted
One odd result of running udevadm test on the "external" interface:
enp1s0: Failed to rename network interface 2 from 'enp1s0' to 'external':
Device or resource busy
There must be some trick here that I'm missing. What's the problem with the FC31
kernel ?
sean
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
2:56 p.m.
On 11/27/19 12:39 PM, Bill Shirley wrote:
I don't run FC31 but on all my other Fedora systems, I add
net.ifnames=0
to the kernel
command line /etc/default/grub:
GRUB_CMDLINE_LINUX="rd.md.uuid=41012be5:1df005d4:cfee0bd3:e112219a
*net.ifnames=0* rd.shell rd.timeout=65 consoleblank=600 rcu_nocbs=0-15"
Then regenerate the grub menu:
# legacy BIOS
grub2-mkconfig -o /boot/grub2/grub.cfg
I don' have but one EFI server:
# EFI BIOS
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Bill
On 11/27/2019 10:42 AM, sean darcy wrote:
> On 11/27/19 8:09 AM, Roberto Ragusa wrote:
>> On 2019-11-26 19:58, Sean Darcy wrote:
>>
>>> On boot:
>>> kernel: asix 2-3:1.0 eth0: register 'asix' at usb-0000:00:14.0-3,
ASIX
>>> AX88772 USB 2.0 Ethernet, 00:0e:c6:dc:01:aa
>>> kernel: usbcore: registered new interface driver asix
>>> kernel: asix 2-3:1.0 enp0s20u3: renamed from eth0
>>>
>>> then I unplug and plug:
>>> kernel: asix 2-3:1.0 internal: renamed from enp0s20u3
>>> kernel: asix 2-3:1.0 internal: link up, 100Mbps, full-duplex, lpa
>>> 0x45E1
>>>
>>> That does not happen if I plug and unplug external, an ethernet cable.
>>>
>>> BUT, what's really odd. I'm booting the Fc31 kernel:
>>>
>>> kernel-5.3.11-300.fc31.x86_64
>>>
>>> if I boot the same kernel, but FC30:
>>>
>>> kernel-5.3.11-200.fc30.x86_64
>>>
>>> IT WORKS !!
>>>
>>> Any help appreciated.
>> I've seen the same issue some time ago (but on Centos 7).
>> The basic problem is that interface renaming must happen correctly
>> in the initramfs, where you have to be sure the network configuration
>> is fine;
>> that explains why a successive unplug/replug works.
>> In my case there was no NetworkManager involved, just the old
>> "service network start"
>> things, with configs in /etc/sysconfig/network-scripts/ifcfg*
>> No idea what can have happened between those two kernels, apart
>> from indeed having different intiramfs content.
>> You should try extracting the two initramfs and doing a comparison.
>> Something like:
>>
>> [root@router boot]# cat z_decompress.sh
>> #!/bin/bash
>>
>> set -e
>>
>> initramfs=$1
>> /usr/lib/dracut/skipcpio $initramfs >z_decomp_$initramfs.cpio.gz
>> rm -Rf z_dir_$initramfs
>> mkdir z_dir_$initramfs
>> cd z_dir_$initramfs
>> gunzip <../z_decomp_$initramfs.cpio.gz | cpio -i
>>
>> Best regards.
>>
>
> Thanks, but that's beyond my kernel skill set.
>
> Here's what I tried, all without success:
>
>
> 1. put 2 .link files is /etc/systemd/network
>
> ls /etc/systemd/network
> 10-external.link 10-internal.link
> cat /etc/systemd/network/*
> [Match]
> MACAddress=50:7b:9d:0b:8a:ab
>
> [Link]
> Name=external
> [Match]
> MACAddress=00:0e:c6:dc:01:aa
>
> [Link]
> Name=internal
>
>
> 2. put 70-persistent-net.rule in /etc/udev/rules.d
>
> cat /etc/udev/rules.d/70-persistent-net.rules
> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="50:7b:9d:0b:8a:ab",
> NAME="external"
> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="00:0e:c6:dc:01:aa",
> NAME="internal"
>
> rebooted
>
> One odd result of running udevadm test on the "external" interface:
>
> enp1s0: Failed to rename network interface 2 from 'enp1s0' to
> 'external': Device or resource busy
>
> There must be some trick here that I'm missing. What's the problem
> with the FC31 kernel ?
>
> sean
I tried net.ifnames=0. That resulted in interface names eth0 and eth1.
And did not honor the persistent name request.
udevadm finds the 10-external.link file :
SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link
/sys/class/net/eth0
Successfully loaded SELinux database in 1.572ms, size on heap is 331K.
Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
=== trie on-disk ===
tool version: 243
file size: 9955651 bytes
header size 80 bytes
strings 2118107 bytes
nodes 7837464 bytes
Load module index
Found container virtualization none.
Network interface NamePolicy= disabled on kernel command line, ignoring.
timestamp of '/etc/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/10-internal.link
Parsed configuration file /etc/systemd/network/10-external.link
Created link configuration context.
ID_NET_DRIVER=r8169
eth0: Config file /etc/systemd/network/10-external.link is applied
ethtool: autonegotiation is unset or enabled, the speed and duplex are
not writable.
eth0: Failed to query name_assign_type: Invalid argument
eth0: Policies didn't yield a name, using specified Name=external.
ID_NET_LINK_FILE=/etc/systemd/network/10-external.link
ID_NET_NAME=external
Unload module index
Unloaded link configuration context.
but still the interface name is not changed!
sean
4:36 p.m.
My 70-persistent-net.rules looks like this:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:22:36:97:f9", ATTR{type}=="1",
KERNEL=="eth*", NAME="lan4"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:29:37:0e:78", ATTR{type}=="1",
KERNEL=="eth*", NAME="wifi"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:20:59:10", ATTR{type}=="1",
KERNEL=="eth*", NAME="ccast"
Don't know if that is the secret sauce to make yours rename.
Bill
>> cat /etc/udev/rules.d/70-persistent-net.rules
>> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="50:7b:9d:0b:8a:ab", NAME="external"
>> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="00:0e:c6:dc:01:aa", NAME="internal"
>>
>> rebooted
>>
>> One odd result of running udevadm test on the "external" interface:
>>
>> enp1s0: Failed to rename network interface 2 from 'enp1s0' to
'external': Device or resource busy
>>
>> There must be some trick here that I'm missing. What's the problem with
the FC31 kernel ?
>>
>> sean
I tried net.ifnames=0. That resulted in interface names eth0 and eth1. And did not honor
the persistent name request.
udevadm finds the 10-external.link file :
SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/eth0
Successfully loaded SELinux database in 1.572ms, size on heap is 331K.
Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
=== trie on-disk ===
tool version: 243
file size: 9955651 bytes
header size 80 bytes
strings 2118107 bytes
nodes 7837464 bytes
Load module index
Found container virtualization none.
Network interface NamePolicy= disabled on kernel command line, ignoring.
timestamp of '/etc/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/10-internal.link
Parsed configuration file /etc/systemd/network/10-external.link
Created link configuration context.
ID_NET_DRIVER=r8169
eth0: Config file /etc/systemd/network/10-external.link is applied
ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
eth0: Failed to query name_assign_type: Invalid argument
eth0: Policies didn't yield a name, using specified Name=external.
ID_NET_LINK_FILE=/etc/systemd/network/10-external.link
ID_NET_NAME=external
Unload module index
Unloaded link configuration context.
but still the interface name is not changed!
sean
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
10:02 a.m.
On 11/27/19 5:36 PM, Bill Shirley wrote:
My 70-persistent-net.rules looks like this:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:22:36:97:f9", ATTR{type}=="1",
KERNEL=="eth*",
NAME="lan4"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:29:37:0e:78", ATTR{type}=="1",
KERNEL=="eth*",
NAME="wifi"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:20:59:10", ATTR{type}=="1",
KERNEL=="eth*",
NAME="ccast"
Don't know if that is the secret sauce to make yours rename.
Bill
>>> cat /etc/udev/rules.d/70-persistent-net.rules
>>> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="50:7b:9d:0b:8a:ab",
>>> NAME="external"
>>> SUBSYSTEM=="net", ACTION=="add",
ATTR{address}=="00:0e:c6:dc:01:aa",
>>> NAME="internal"
>>>
>>> rebooted
>>>
>>> One odd result of running udevadm test on the "external"
interface:
>>>
>>> enp1s0: Failed to rename network interface 2 from 'enp1s0' to
>>> 'external': Device or resource busy
>>>
>>> There must be some trick here that I'm missing. What's the problem
>>> with the FC31 kernel ?
>>>
>>> sean
>
> I tried net.ifnames=0. That resulted in interface names eth0 and eth1.
> And did not honor the persistent name request.
>
> udevadm finds the 10-external.link file :
>
> SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link
> /sys/class/net/eth0
> Successfully loaded SELinux database in 1.572ms, size on heap is 331K.
> Trying to open "/etc/systemd/hwdb/hwdb.bin"...
> Trying to open "/etc/udev/hwdb.bin"...
> === trie on-disk ===
> tool version: 243
> file size: 9955651 bytes
> header size 80 bytes
> strings 2118107 bytes
> nodes 7837464 bytes
> Load module index
> Found container virtualization none.
> Network interface NamePolicy= disabled on kernel command line, ignoring.
> timestamp of '/etc/systemd/network' changed
> Parsed configuration file /usr/lib/systemd/network/99-default.link
> Parsed configuration file /etc/systemd/network/10-internal.link
> Parsed configuration file /etc/systemd/network/10-external.link
> Created link configuration context.
> ID_NET_DRIVER=r8169
> eth0: Config file /etc/systemd/network/10-external.link is applied
> ethtool: autonegotiation is unset or enabled, the speed and duplex are
> not writable.
> eth0: Failed to query name_assign_type: Invalid argument
> eth0: Policies didn't yield a name, using specified Name=external.
> ID_NET_LINK_FILE=/etc/systemd/network/10-external.link
> ID_NET_NAME=external
> Unload module index
> Unloaded link configuration context.
>
> but still the interface name is not changed!
>
> sean
https://bugzilla.redhat.com/show_bug.cgi?id=1777893
7:03 p.m.
On Thu, Nov 28, 2019 at 11:02:03AM -0500, sean darcy wrote:
I hit this too trying to use the ifcfg- files, per the email with subject
"network bridge does not get an IP address".
I see no failure in the dmesg file you attached to that bug :-(
I get these failures (lan1 and lan2 are the new names):
Dec 26 15:38:50 umbrella systemd-udevd[767]: enp6s1: Failed to rename network interface 2
from 'enp6s1' to 'lan2': Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[767]: enp6s1: Failed to process device, ignoring:
Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[758]: ethtool: autonegotiation is unset or enabled,
the speed and duplex are not writable.
Dec 26 15:38:50 umbrella systemd-udevd[758]: enp4s0: Failed to rename network interface 3
from 'enp4s0' to 'lan1': Device or resource busy
Dec 26 15:38:50 umbrella systemd-udevd[758]: enp4s0: Failed to process device, ignoring:
Device or resource busy
-- Patrick
1618
days inactive
1649
days old
9 comments
6 participants
participants (6)
-
Bill Shirley -
Patrick Mansfield -
Roberto Ragusa -
sean darcy -
Sean Darcy
-
sixpack13