Search results

  1. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    By the way, I use OpenvSwitch (OVS) in my config so it works a little bit different with assigning VLANs.
  2. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    Is it because vmbr1 has no Gateway so it cannot find it's way back?
  3. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    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.
  4. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    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?
  5. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

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

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

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

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

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

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    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.
  9. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    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.
  10. S

    [SOLVED] [pveupgrade] error processing kernel

    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!
  11. S

    [SOLVED] [pveupgrade] error processing kernel

    # 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`...
  12. S

    [SOLVED] [pveupgrade] error processing kernel

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

    VLAN-Configuration in Cluster PVE 8.0.3

    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...
  14. S

    Upgrade from 7 to 8 kernel issue

    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 <<
  15. S

    Proxmox 8 clients can't get ip from dhcp server

    - 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?
  16. S

    VLAN-Configuration in Cluster PVE 8.0.3

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

    VLAN-Configuration in Cluster PVE 8.0.3

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

    Proxmox 8.0.3 - Realtek USB Ethernet loses connection randomly and will not work till plugged back in and rebooted.

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

    [SOLVED] [pveupgrade] error processing kernel

    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