Wired connection not working fedora 41 (dualboot linux/win10)

Ask Fedora
, , ,
1

hello all,

I have a dualboot desktop PC with fedora41/win10. I use 90% of the time linux. I recently have bought myself a (QNAP) NAS, to help me store files between the 2 OS’s and other devices. This NAS is directly connected to my desktop PC (“ad-hoc”).

I have set up the NAS on windows (Qfinder software is required for first setup, bad linux support). This went well and i can easily and reliably connect my network folder when in windows.

I can’t however connect to my NAS when i boot into linux. I have only now found out that my wired ethernet port on my PC doesnt work in linux because i dont use it.
I connect myself to the internet via WIFI. I dont have a wired connection where my PC is.

using the nmcli command:

enp3s0: disconnected
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), C4:65:16:14:1F:C6, hw, mtu 1500

however, using the ip link command:

2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether c4:65:16:14:1f:c6 brd ff:ff:ff:ff:ff:ff

I dont really understand what is going on.

Thank you kindly,
Edward

2

You have to blacklist the r8169, so that you can use the :

r8168 one.

1 Like
3

So far the r8168 driver has been installed succesfully, following the linked tutorial ( sunwire/dkms-r8168 Copr ) without the secure boot steps.

however it seems that the next link ( SLES 12 SP4 | Administration Guide | Managing Kernel Modules ) gives a 404.

do i need to make/edit a .conf file to blacklist the r8169 and assign(?) the r8168?

using sudo lspci -v it seems that r8168 is already in use.

edit: i tried blacklisting r8169 (i think it worked?) however i still cant use the ethernet port… if a want to access the web ui of the NAS it wont load.

edit 2: i have found a “temporarily work around”: I set up an unused network range extender. i connected it to the home wifi and used the only physical port to connect the NAS, then i connected my PC to the new wifi network… well… it works
thanks for your help anyway :slight_smile:

4

If someone knows a way of fixing the wired network port please help me.

5

Please make a inxi -Fzxx and post the output there. So we can see what driver is active.

Please post also a nmcli c to see how it looks on the network manager side.

2 Likes
6

inxi -Fcxx :

Network:
  Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
    vendor: Hewlett-Packard driver: rtw_8822be v: N/A pcie: speed: 2.5 GT/s
    lanes: 1 port: 4000 bus-ID: 02:00.0 chip-ID: 10ec:b822
  IF: wlp2s0 state: up mac: aa:ce:3a:87:99:92
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8168 v: 8.054.00-NAPI pcie: speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: c4:65:16:14:1f:c6

nmcli c :

NAME                    UUID                                  TYPE      DEVICE 
home-wifi-EXT           52c6bd27-d035-4469-b66a-1e73b8ac2024  wifi      wlp2s0 
lo                      90a4129a-f395-4e57-95cf-6dc3ec40e7c6  loopback  lo     
extended-8              a6557616-e7a0-4a51-93c7-92cc68e298e7  wifi      --     
home-wifi               8c75f3d5-e9af-4c44-9657-49650787822c  wifi      --
8

that has done the trick, my network port now works!
Thank you @vgaetera and @ilikelinux !!

however i now receive the message “connection ‘ethernet’ deactivated” and “IP configuration was unavailable”. That is most likely because my NAS is directly connected to it. maybe i can reconnect the NAS? or give both a reboot?

1 Like
10

I retried connecting a few times but it didn’t help.

11

The NAS you most likely connect to the router direct. So you can connect it from your network with other devices. This way you can use the NAS also when your computer is switched off with mobile devices etc.

1 Like
12

that is indeed the proper way of using a NAS, sadly, it is not possible for me to connect the NAS to the router, the main purpose of the NAS is to be an extended storage for my dual-boot PC anyway, and maybe some laptops i have lying around…

13
  • Connect the NAS to Windows.
  • Find out the IP address of the NAS.
  • Check Windows network settings:
ipconfig /all & route print
14

IP of NAS is 192.168.1.47

ipconfig /all & route print gives:

result removed for now, it is unclear to me if it is safe to share it in public…

15

That’s a link-local connection which you can replicate like this:

nmcli connection delete ethernet
nmcli connection add type ethernet ipv4.method link-local
nmcli connection up ethernet

If the problem persists, allow the LLMNR client:

sudo firewall-cmd --permanent --add-service=llmnr-client
sudo firewall-cmd --reload

In addition, make sure to enable link-local on the NAS and verify that the source and destination IPs are in the same subnet 169.254.0.0/16.

If this is not possible, you have the following options:

  • Use IPv6 link-local assuming the NAS supports IPv6.
  • Switch to a static or shared IPv4 connection.

That IP belongs to the Wi-Fi network and makes your traffic routed exclusively over Wi-Fi.
In this case, Ethernet is not used, unless the NAS has some other IP.

See also:

1 Like
16

Thank you for coming back to me.

This has done the trick:

I now have access to the network folder and the web UI of the NAS. It all works now!

Again, Thanks to everyone involved! :slight_smile:

2 Likes