No they were there the dmesg command brought them to the surface and the rest was just adding them to the yaml file for netplan, run netplan try and once happy netplan apply and THEN I could see them in all of the usual tools.
The other thing I have found out about the stupid subiquiti installer is if there is no network attached to the card or port it will drop it and you will not see it, I had to attach live net- works to the ports I wanted registered, oh it would find them in the install then drop them. Also if you had a port that did not go to a live network (I tried to use my camera network which is an isolated island) again it would find then drop or worse it would find then make the camera network the public port!!! I would have to go in and change the metric on the ports to get the right one going out. I am going to start looking at some other server solution as it seems that Ubuntu is brain dead... I do not know why they have to make setting up the network part such a mess. Seems that one should not have to go to such lengths to install a stinking nic card. The interesting thing is the desktop will do all of that stuff automagically, I stuffed the fibre card in a desktop machine and it found it as soon as it booted up, showed two fibre ports same rev level (20.04.x) just desktop vice server... Lspci showed the presence of the card but it did not give the port names which were enp30f0 and enp30f1.... Such is life.... But there are more fun things to do then have to clean up something that should in my view be a wee bit more obvious. This is not the first time I have run into this but it sure is getting old. On Wed, Jul 7, 2021 at 6:20 PM Russell Senior <[email protected]> wrote: > I have never installed Ubuntu Server, but I find that surprising. By > default these days, interfaces will have "predictable" names, which I > think is kind of a misnomer, but afaik should show up in the output of > things like "ip a" or "ifconfig -a". It might be that your NIC needs > firmware to operate, and that's what prevents it showing up. What NIC > is it? What does lspci say? > > On Wed, Jul 7, 2021 at 3:08 PM Chuck Hast <[email protected]> wrote: > > > > I had to add a nic card to an Ubuntu server. Appears that once the > > server has been setup it will not recognize a new card. You have to > > go in and find the port names, but in my case ifconfig, ip... etc only > > showed me the functioning cards nothing else, I was finally able to > > find them using dmesg | grep -i network, to see them. After that > > I then had to go in and modify the netplan yaml file and run netplan > > try to see if they were seen, indeed they were. > > > > Seems there should be a way to run the installer that did all of that > > magic initially to short circuit the time it takes to do all of that > just to > > find out what the new port(s) are. In this case it was a fibre card that > > replaced the copper paths to/from the Zoneminder server. Subiquiti > > appears to be what does this, so why is there not a way to at least > > run the network part to discover a card and get on with getting it > > online avoiding having to putz with netplan and all of that. Anyone > > have any ideas or is that just the way it is? > > > > I tried all of the usual discovery tools to try to find those two ports > but > > not one of them displayed them, only the dmesg command above > > worked. > > > > -- > > > > Chuck Hast -- KP4DJT -- > > I can do all things through Christ which strengtheneth me. > > Ph 4:13 KJV > > Todo lo puedo en Cristo que me fortalece. > > Fil 4:13 RVR1960 > -- Chuck Hast -- KP4DJT -- I can do all things through Christ which strengtheneth me. Ph 4:13 KJV Todo lo puedo en Cristo que me fortalece. Fil 4:13 RVR1960
