Search results

Right. I still think Untagged 2000 is wrong. Your other screenshot says : Network default and no Traffic Restriction. Try that please in the 'problem' switch. Try to configure the switch with a working port, and from there on you can restrict more and block/allow more.

Can this switch do trunking at all? I did a Google search and people complained about not being able to create an trunk port. Is this the first trunk port you are configuring, or is there already an existing trunk port in that switch?

And if you UNcheck the Traffic Restriction button, can you then select ALL ?

"By default Networks/VLANs set to all will trunk VLANs" set port 19 to ALL

What happens when you set it to "none" instead of Untagged (2000) ?

What other settings are there in that drop down menu (Untagged (2000)) For me this Untagged setting makes no sense if it has to be a trunk port. But I do not own or use Ubiquiti gear.

With "uplink" I think you mean "trunk port" ? A trunk port is Tagged, so it can carry multiple vlans. Your trunk port 19 is configured as Untagged.

THANK YOU SOOOO MUCH!!! That was indeed the solution, double quote marks. No clue how those single quotes got there... And this had been running for months. Anyway, I'm very happy now!

# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`Proxmox Virtual Environment`...

/etc/default/grub exists, but I use systemd-boot (/etc/kernel/cmdline).

Thanks for the reply. I know and have experienced for myself that an openvswitch update can indeed break connectivity. Then someone had the bright idea of adding "ifup -a" at the end of the pveupgrade command. (or something similar, that the last command is to bring up the interface. Not sure if...

I have the same error, only with different kernel version, and running PVE 7: Errors were encountered while processing: pve-kernel-5.15.107-2-pve Also see my post: https://forum.proxmox.com/threads/pveupgrade-error-processing-kernel.129494/ >> SOLVED <<

- please share your PVE host "/etc/network/interfaces" - (from PVE host) what is the output of : # ip ad - can the PVE host reach (ping) the dhcp server?

I would very much like to hear them.....(seriously).

Or install and use OpenvSwitch (OVS). Makes life a bit easier.

Check in BIOS if there are options for USB sleep mode, energy mode, standby mode etc. Turn those settings off.

Now I can't install any packages on my PVE host, all ends with : Processing was halted because there were too many errors. I wanted to try this : https://github.com/jordanhillis/pvekclean

Why reserve 3 nics for OPNsense? Or are you planning to use an interface for DMZ?

Well.....for starters you could do from your PVE host shell : # pveupdate # pveupgrade # reboot

Hi, I just ran into this error when doing a "pveupdate" and "pveupgrade" on my PVE host. I'm running kernel 6.2 for a few weeks now, before that I had kernel 5.15. No problems no errors, until now. What is the solution, I tried apt autoremove, apt full-upgrade, apt dist-upgrade. Still these...