@pfsin excellent, happy it worked.

@Gertjan THANK YOU sir for answering

@scourtney2000 make sure you can ping Solarwinds server sourcing from your loop1

@stivi I have found this:
https://doc.dpdk.org/guides-21.05/rel_notes/release_21_05.html
"Added a command line option to configure forced speed for an Ethernet port: dpdk-testpmd -- --eth-link-speed N."
Is this possible in tnsr?

@mloiterman I was never able to get the AQC107 card working in my box, as it doesn't seem supported by the DPDK version used in the current TNSR release. I ended up running ESXi on the router, and using VMXNET3 adapters for all NICS (other card for LANs is an X710-T4L) and that worked for me without a speed hit.

This allowed the AQC107 card to use it's 5Gbps speeds, which I needed for AT&T Fiber.

I wan to report back to that point, I got a greater mSATA
with 256 GB space and were installing all partitions once more again, and now all is fine for me, with no hassle or
problems running out of space.

frank@lankeeper:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL NAME FSTYPE SIZE MOUNTPOINT LABEL loop0 squashfs 63.3M /snap/core20/1822 loop1 squashfs 111.9M /snap/lxd/24322 loop2 squashfs 49.8M /snap/snapd/18357 loop3 squashfs 116.8M /snap/core/14946 loop4 squashfs 9.6M /snap/canonical-livepatch/209 sda 238.5G ├─sda1 1M ├─sda2 btrfs 5G /boot ├─sda3 ext4 20G / ├─sda4 ext4 20G /home ├─sda5 ext4 20G /srv ├─sda6 ext4 20G /usr ├─sda7 ext4 20G /var ├─sda8 ext4 20G /var/lib ├─sda9 ext4 20G /usr/local ├─sda10 ext4 20G /srv/www ├─sda11 ext4 20G /srv/ftp ├─sda12 ext4 20G /srv/rsync ├─sda13 ext4 15G /tmp ├─sda14 swap 4G [SWAP] └─sda15 ext4 14.5G /var/tmp

Looks like there is a problem with the kernel - "downgrading" to 5.15.0-60-generic fixed the problem.

@russellc Related to logs, you can ssh the system installation environment. It will make it easier.

I worked around this issue by installing the old version (22.06) and running an update to 22.10.

Unfortunately, the Netgate support didn't help much.

@derelict Derf, yep I mentioned the kernel version. The TNSR version is 21.07.0-1.

Anyway, sudo clixon_cli worked to get the commands operational (and that's using my custom user, not tnsr)

[Now I see the part of the docs that caused this issue, since I created a custom user during install:
Default TNSR Permissions where only root and tnsr users are allowed into the CLI.

For others' reference, here's how to fix that (once in the CLI via sudo):

configure t nacm group admin member USERNAME exit configuration copy running startup exit

More info on NACM config here in the docs

After that, just entering clixon_cli without sudo will work just fine...

I came across this post https://forum.netgate.com/topic/157917/tnsr-with-esxi-vmxnet3-unable-to-load-interfaces/3?_=1630333615883 and reinstalled the VM in BIOS mode. After this I can see the interface.

I will mark the post as solved.

Thanks,

@jegr That should have been corrected early yesterday. You should get 21.07 if you do it again.

@derelict if the OP means pfSense then perhaps we should move that to pfSense forums

That was it.

I too was able to resolve my issue. I apologize for hijacking this thread thinking it was similar underlying issue.

The difference between working and not working was when using virt-install, I need to use --cdrom for specifying the install ISO. Using --location ends up not working. While the installation completes, network interfaces do not. Virt-manager worked because it was using cdrom and not location.

Works:

sudo virt-install --cdrom tnsr.iso

Does not work:

sudo virt-install --location tnsr.iso