I researched this topic as much as I could before charging in. Unfortunately what information I could find was rather dated. Several threads date back to 2012, and even the most recent threads in 2016 and 2015 make reference to files and folders that simply do not exist on my system. I quickly realized that topics discussed in these threads might not work, but I did pick up one repeated comment I thought might be relevant. This was the fact that amahi is slaved to the eth0 interface. I was hoping that if I could get the new NIC to show up as eth0 and all would be good. Recent experience with another computer showed that when I added a PCIe NIC, it reported as eth0 while the onboard was eth1. I hoped for the same with my amahi machine, and decided to experiment.
First I installed the new PCIe NIC, connected it to the switch, and disabled the onboard NIC in BIOS. I was hoping that with only one NIC, the "first" NIC would be eth0. Unfortunately after rebooting I had no network access. I checked my router (providing DHCP), and the amahi IP address was not showing as connected, nor was there a DHCP lease for the card (I know the machine was booting okay because I connected a monitor, and could see the HDA login prompt.) Quickly the hope that the new NIC would be eth0 and all would be good was quickly dashed. I then re-enabled the onboard NIC, plugged it into the switch, and booted with both NICs installed. At this point the network config was stock, except for having the 2nd NIC in the machine, but unplugged, but I still could not connect remotely. Hopes of an easy swap gone, I removed the 2nd NIC, and restarted in my stock config, and started to dig a little deeper.
I checked the network config using
Code: Select all
ifconfig -a
Any ideas appreciated.