Proxmox Install Issues

[AryasDad]

I am running into a frustrating issue that I cannot seem to resolve and would appreciate any help or nudges in direction of tutorials that may help me resolve.

First a little background:
I have been running PFSense for several years on bare metal.  I have 1 gig fiber through AT&T and have never seemed to get close to my supposed 1GB limit.  I seem to be hovering around 300 or so.  I figured it was the hardware I was running on.  So I recently bought a new 6 port, i7 device from aliexpress.

I also have a separate Ubuntu server running on an Intel Nuc.  Through my investigation of new firewall hardware,  I cam across Proxmox.  So I decided it would be nice to roll my firewall and my Ubuntu as VM's.  I also came across OPNSense due to all the shenanigans related to pfsense changes.  Looked into it and thought it would be a good time to transition.

I have been trying for several days to get up and running a test.  Now I still have my pfsense box running on the front end and created a separate van to get the proxmox/opnsense/ubuntu system up and running before I swap it out.  I don't know if this is what is causing my issues, but am thinking not based on the issues I am encountering.

Hardware specs
CPU: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
RAM: DDR4 32GB Kit (2 x 16GB) 2666MHz PC4-21300 CL19
HD:  mSATA SSD 256GB
Ethernet: 6 intel 1g ports
Proxmox version: 6.4-4
OPNSense version: 21.1

I have proxmox up and running.  I have tried to install OPNsense several times.  I always seem to get stuck after the second reboot.  I do the install, set up my interfaces, etc. reboots after install and do final setup.  Everything runs smooth.  It is after another reboot where things go hay-wire.

After initial install and first reboot, I have no issues checking for updates, or anything else.  After that next reboot, I can no longer access updates.  I can ping, but updates do not work.

For example, I can run the following commands from cli with no issues prior to the first reboot:
opnsense-update -M
pkg update -f

I can also run the update check from the web gui and no issues.

I have tried on subsequent installs not to update the system to latest 21.1.7, thinking that was the issue, and still it happens.

After the second reboot, web gui updates spins and spins and sometimes I get a timeout and sometimes I get no updates available.  I have tried several different mirrors, and all seem to have the same issue.

If I run the "pkg update -f" from cli, it takes up to 30-45 minutes to download packagesite.txz.  Prior to the second reboot, it downloads in a snap.

I downloaded PFSense and set it up as a VM to see if it has the same issues.  So far, I do not see the same behavior, but it doesn't have the same update methods as opnsesne, so not really sure what to check.  I even have rebooted it several times and even did a fetch of https://pkg.opnsense.org/FreeBSD:12:amd64/21.1/latest/packagesite.txz and no access or speed issues were encountered.

I have searched and I see a lot about ipv6 when it comes to seeing no packages or orphaned packages (something I also see after the second reboot).  I am not really running ipv6 and have no real need to up my understanding of it as my needs do not require it.  My pfsense box with AT&T doesn't have it setup.  And it doesn't appear to be affecting the pfsesne VM in this regard.

But, I don't think this is really my issue, as it works great after 1 reboot.  It is the second reboot, every time that causes the apparent shutdown.

So what changes after a second reboot to cause my system to effectively stop working?  I would really like to resolve this as I like OPNSense organization much better and not liking the direction pfsense is going with the whole proprietary bent.

[AryasDad]

Following up and issues seem to have self resolved.  I let the box sit pending any insight to my issues.  When I returned to it, connection speed seemed to be back to normal.  Though I would have to reboot the unit after every few package installs, as it would appear to stall on subsequent installs.

I have also replaced the ethernet cables this morning to see if it was "hardware" issues. 

But, all in all, seem to be back to testing out.