Search results
-
T
[SOLVED] Bridge ageing time not configurable (brctl setageing .. / bridge_ageing 0)
Good deal. I currently only have one node where this is needed, so I can get by with the older kernel until the new one is released.- troycarpenter
- Post #10
- Forum: Proxmox VE: Networking and Firewall
-
T
[SOLVED] Bridge ageing time not configurable (brctl setageing .. / bridge_ageing 0)
I just filed bug #983: https://bugzilla.proxmox.com/show_bug.cgi?id=983- troycarpenter
- Post #6
- Forum: Proxmox VE: Networking and Firewall
-
T
[SOLVED] Bridge ageing time not configurable (brctl setageing .. / bridge_ageing 0)
If you have console access to the host during bootup, you can select the 4.2.8-1-pve kernel through the grub menu. I'm not sure how to make that permanent because the kernel you want is hidden is a sub-menu. I wasn't able to change the grub configuration to automatically select the one I...- troycarpenter
- Post #5
- Forum: Proxmox VE: Networking and Firewall
-
T
[SOLVED] Bridge ageing time not configurable (brctl setageing .. / bridge_ageing 0)
This seems to be tied to the kernel. This works: root@ajanta:~# uname -a Linux ajanta 4.2.8-1-pve #1 SMP Sat Mar 19 10:44:29 CET 2016 x86_64 GNU/Linux root@ajanta:~# brctl setageing vmbr0 0 But this does not: root@gatimaan:~# uname -a Linux gatimaan 4.4.6-1-pve #1 SMP Thu Apr 21 11:25:40 CEST...- troycarpenter
- Post #3
- Forum: Proxmox VE: Networking and Firewall
-
T
[SOLVED] Bridge ageing time not configurable (brctl setageing .. / bridge_ageing 0)
I'm seeing this problem as well. root@fury:~# brctl setageing vmbr4 0 set ageing time failed: Numerical result out of range I have also found that 10 seems to be lowest value now: root@fury:~# brctl setageing vmbr4 9 set ageing time failed: Numerical result out of range root@fury:~# brctl...- troycarpenter
- Post #2
- Forum: Proxmox VE: Networking and Firewall