18.04.04 Server needs new eth0 driver for networking, help installing

Similar to the problems detailed in this thread,

I have a new-build file server with a Gigabyte Aorus AX Z490 motherboard.

I cannot get this machine to reliably raise network interfaces with eth0 and automatically gain connectivity on every reboot – at least without being physically present to do a hard reboot and inserting the ethernet cable into the back after the boot sequence has finished.

Could I have some handholding through this? I’ve never installed a linux driver manually before, and apparently the needed driver is not yet included in the 18.04 Server kernel by default. Oddly enough however, it was included when I first loaded 18.04 Desktop version on this machine to run trial tests. There were no connectivity problems under 18.04 Desktop (at least I think it was 18.04 Desktop, and not 20.04 Desktop).

In the posting linked at the top, that user listed out these steps:

I was able to solve this thanks to your workaround.

I had a different motherboard, so I downloaded the Windows LAN Driver
from Asus’s website at

I then downloaded the NVM Update Utility at
https://downloadcenter.intel.com/download/24769 since it has a Linux

The name of the file should be similar to FXVL_15F3_ASUS.bin, but the
ending will be different depending on the various Z490 motherboard
manufacturers. This can be found on the driver website for the
specific motherboard you are using.

After unzipping this file, I was left with two zip files,

I225V_Intel_Gigabit_Ethernet_Driver_V1.0.1.4_WIN10_64-bit.zip. I found
the FXVL_15F3_ASUS.bin in I225V_End_User_FW_UPDATE.zip and copy-pasted
this file over into the /700Series/Linux_x64/ directory for the NVM
Update Utility.

Next, we need to find the config file for the i225 driver. After
unzipping and searching the Asus LAN Driver files, I found the proper
config settings at config_i225.txt in I225V_End_User_FW_UPDATE.zip.
Again, the location of the config_i225.txt might vary depending on the
motherboard manufacturer’s LAN driver.

Lastly, I navigated to nvmupdate.cfg in /700Series/Linux_x64/, and
added this to the end of the file:

VENDOR: 8086
IMAGE DOWNGRADE: TRUE END DEVICE Once this is added, type sudo ./nvmupdate64e. After following the on-screen instructions, Ethernet
should connect immediately. Hope this helps anyone experiencing this

Somewhere in this process, I go completely off the rails and get lost. When I try sudo ./nvmupdate64e nothing happens, so whatever I’m doing wrong comes up prior to that point.

My lspci is as follows:

$ lspci
00:00.0 Host bridge: Intel Corporation Device 9b53 (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 9bc5 (rev 05)
00:12.0 Signal processing controller: Intel Corporation Device 06f9
00:14.0 USB controller: Intel Corporation Device 06ed
00:14.2 RAM memory: Intel Corporation Device 06ef
00:14.3 Network controller: Intel Corporation Device 06f0
00:16.0 Communication controller: Intel Corporation Device 06e0
00:17.0 RAID bus controller: Intel Corporation SATA Controller (RAID mode)
00:1b.0 PCI bridge: Intel Corporation Device 06c0 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Device 06ac (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device 06b8 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 06b0 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 06b4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0685
00:1f.3 Audio device: Intel Corporation Device 06c8
00:1f.4 SMBus: Intel Corporation Device 06a3
00:1f.5 Serial bus controller (0c80): Intel Corporation Device 06a4
01:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. Device 2263 (rev 03)
04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 02)

I need the 15f3 Intel ethernet driver for linux, and I have it (per that other thread’s postings) but I am too much in the n00b to novice (at best!) understanding with linux drivers to get any further. Anyone able to guide me along?

networking – Unable to connect to wireless networks

I recently moved to a different hostel at my university, and my router’s wireless network, which worked fine in the previous hostel, suddenly started behaving weird. My devices (tried with my phone and laptop, and those of my friends too) can detect the wireless network, but fail to connect it. On the android phones, the status simply changes to “Saved” from “Connecting”, while on Windows it says “Can’t connect to this network”.

I’ve tried changing the settings, rebooting the router, and even resetting it, but the issue persists. Sometimes the devices successfully connect to the network, but within 5 minutes or so the issue returns. I have two routers, and both are experiencing the same issue (both worked back in the previous hostel), and a friend is also experiencing this issue with his router (in the same hostel). Even without the router being connected to the WAN, the devices cannot connect to the broadcasted wireless network. The router works fine if the PC has a wired connection to it though.

Has anyone else experienced a similar problem? Is there any way this can be solved?

Information that might be relevant: internet traffic in the university is directed through a proxy which controls access to sites; there are three wireless networks hosted by the university around the campus for wireless access, both in the 2.4GHz and 5GHz bandwidths. From my limited knowledge, I suspect that the university networks might be interfering with the router’s wireless networks in the new hostel.

networking – Correct way to provide a direct network link between 2 devices as well as connecting both to a switch

What is the correct way to configure the PC and Server, so that the loop doesn’t cause networking issues? Meaning, traffic to/from other devices can only go via the switch as normal and neither device is seen as a bridge or route to the other?

Just connect the two using a cable and configure both ports to have IP addresses. Ideally this link should use a completely separate subnet from your main LAN.

Bridging will not occur unless you deliberately set up a bridge. Neither Windows nor FreeBSD (nor any other OS) enable it automatically.

Routing will not occur unless you deliberately set up packet forwarding. Neither Windows nor FreeBSD enable it automatically.

(Additionally, IPv4 uses explicitly configured routing tables, so even if the PC or the server did have routing enabled, routing still wouldn’t occur because other hosts would have no way of knowing that they can use them as gateways. IPv6 would need a little more care to ensure that the machines do not send out Router Advertisements, but that’s also disabled-by-default on both Windows and FreeBSD.)

Of course, if you don’t want the PC to use the server as a gateway, then do not fill in the “Default gateway” field when configuring IP addresses on your 10Gbit NIC…

If in future I upgrade the switch to a fully managed switch that can handle access controls, such as Netgear ProSAFE, or I start to use VLANs on it, does the “correct answer” change?


networking – Error connecting Windows 10 PCs to a MAC on a LAN

The Setup:

1x Mac Mini (MM), running OS X El Capitan Version 10.11.6(not Mac server)

5x Windows 10 (W10) PCs

1x LAN wifi

1x LAN ethernet

The Challenge:

Connect all 5 PCs to the MM over the wired LAN or Wifi and map folders on the MM as additional Drives (Eg, P, Q, R etc) on the W10 PCs, as so as to share files stored on the MM. BTW: The MM is not used as a workstation, more as a “server” or pseudo-server.

The Method:

From the PCs Command prompt on the W10 PCs run “net use T: “1nn.nnn.1.14ffffff” /persistent:yes. (real values hidden for security)

The Initial Outcome:

2 of the 5 PCs connected and drive letters assigned – no problems,

3 of the PCs could not connect, error message 71, “No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.”

Attempted Solution:

On the W10 PCs; increased the number of currentlogons in the registry from 10 to 100, but this made no difference. I think i should be doing something like this on the MM…

Second Outcome:

No effect.


How do I increase the number of (network?) connections that the MM can accept? I believe this would solve the issue, but if I’m barking up the wrong tree, I would gladly be pointed to another one.

Thanks in Advance

networking – Can’t connect to SSH on private IP through VPN gateway

Morning, everyone,

I’ve been having a strange problem for a few hours. I was SSH connected on my Azure virtual machine and my SSH connection suddenly froze (without disconnecting). I closed my shell and restarted my SSH session without success. I checked the NSGs with neighboring machines I connect well to, the NSGs are almost identical. I tried to reboot the machine, redeploy the machine, reset the SSH configuration, reset the user account, without success too. I can easily connect to other machines on the same subnet. I can connect on public IP. I feel like there’s a problem between the VPN gateway and the private IP… Any ideas?

Thank you

Note : I have the following entry in the health status :

At samedi 4 juillet 2020 à 3:15:32 PM UTC+4, the Azure monitoring system received the following information regarding your Virtual machine:
Your virtual machine is unavailable. We’re working to automatically recover your virtual machine and to determine the source of the problem. No additional action is required from you at this time.
Recommended Steps
Check back here for status updates
Redeploy this virtual machine to a different host server

networking – Using 2nd router as extension of my main router, LAN works but WLAN doesn’t and after “x” time it just refuses to work at all

I recently followed a guide how to use an old router to extend my network at home. Everything was smooth, made sure the range I have set the DHCP Server won’t conflict with anything (Main Router, from my ISP.) I’ve used –

Moving on to the old router. I’ve disabled it’s DHCP so it wouldn’t conflict with the server, set the old router’s IP Address as I’ve setup the wireless options as well, made sure it has a different SSID, even changed the channel selection so it wouldn’t collide with anything. The LAN interface works, at the moment I’m connected to it as I’m typing this question. The only problem I’ve had is whenever an I try to connect to it wirelessly via an Android or iPhone it has limited connectivity. I am connected to the network, but I do not have an internet, the LAN ports work however. The 2nd/old router acts like a switch it seems. Any advice how to set this up properly?

networking – CentOS 8 network on boot

I’m running CentOS 8, every time I reboot the network does not start until I log in to the system.

I’ve checked the NetworkManager and the autoconnect is set to yes.

connection.autoconnect:                 yes

In network-scripts/ifcfg-ens192 the followings settings are


Is there a way for the network to start on boot instead having to log in?

networking – Corruption using linux traffic control (tc command)

I am kinda new to doing traffic control using Linux tc commands. So i am doing some hands-on on introducing network delay, packet loss and corruption etc across two hosts in the same network. The below commands were used to corrupt all traffic from port 20786 in Host A to port 202 in Host machine B.

sudo tc qdisc add dev eth0 root handle 1: prio priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
sudo tc qdisc add dev eth0 parent 1:2 handle 20: netem corrupt 30%
sudo tc filter add dev eth0 parent 1:0 protocol ip u32 match ip sport 20786 0xffff flowid 1:2
sudo tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dport 202 0xffff flowid 1:2

How do i make sure the packets will be corrupted? I am asking this because won’t there be TCP error control which make sure that the packets don’t get corrupted?

networking – My raspberry pi web server cant be accessed from outside my Network

I set up a raspberry pi 4 web server in my home network.
I got apache and php running on it and the website can be accessed from within the network but always fails when outside of my network.
I can access the webserver with my private, public and my web domain but only as long as the requesting host is inside my own home network.

I have port forwarding activated on my router (port 80 and port 443) but it seems like the raspberry doesnt even listen to these ports since whenever i check Port 80 (https://www.yougetsignal.com/tools/open-ports/) it says that the port is closed (shouldnt it be opened since there is a web server running there?).

I obviously can provide any information relevant to solving this problem, but right now i am unsure about whatmore i can say…
I am lost

Any Idea on what could be wrong is greatly appreciated!

networking – libvirt on fedora, qemu/kvm guest, guest can ssh to host, but failed to samba or ftp to host

I am running libvirt/qemu-kvm on Fedora32, guest OS is win10 with spice-guest-tool in use.

I use ‘nat’ mode virtual networking.

root@fedora ~)# virsh net-dumpxml default
<network connections='1'>
  <forward mode='nat'>
      <port start='1024' end='65535'/>
  <bridge name='virbr0' stp='on' delay='0'/>
  <mac address='52:54:00:e1:1e:c3'/>
  <ip address='' netmask=''>
      <range start='' end=''/>

While guest is running, ‘brctl show‘ seems fine.

(root@fedora ~)# brctl show
bridge name bridge id       STP enabled interfaces
virbr0      8000.525400e11ec3   yes     virbr0-nic

On host I can ping guest by its ip (

On guest, I can access internet, also can ssh to my host,
but failed to access samba and ftp on my host.

For example, I type ‘net view‘ on guest,
host ‘tcpdump -i vnet0‘ shows:

15:47:39.041395 IP > fedora.bear.microsoft-ds: Flags (S), seq 160880283, win 64240, options (mss 1460,nop,wscale 8,nop,nop,sackOK), length 0
15:47:39.041526 IP fedora.bear > ICMP fedora.bear tcp port microsoft-ds unreachable, length 60

And ‘net view’ eventually reports ‘System error 53: network path not found‘.
I also checked ‘iptables -L -v‘ (too verbose to paste here), no one got ‘REJECT’ed.

In case of ‘ftp’, it is similar to ‘samba’.

15:54:13.232366 IP > fedora.bear.ftp: Flags (S), seq 669575524, win 8192, options (mss 1460,nop,wscale 0,nop,nop,sackOK), length 0
15:54:13.232468 IP fedora.bear > ICMP fedora.bear tcp port ftp unreachable, length 60

It seems that host can not send package back to guest.

Am I missing something? What could be the cause?