Search results

According to my information (net) this is not the case. linux has a timeout of 300s as aging timeout, but the garbage collection that really removes the entries can be delayed for another 30s or even more. So all docs say you may end up between 5-10 minutes at worst. And that's about my...

Well that's hard to tell now. I already had to set all the corresponding bridges by hand to 300. Nevertheless I checked the other bridges in the boxes (there are 5). And they all show the same "30000").So I guess the major issue is the different arp timeouts of the guest producing the fake tcp...

Hello, well, you are right with the arp explanation. In the meantime I found a workaround that does work. I made a cronjob on a guest on host 2 that sends arping -fc1 to every guest that falsely reaches the guest on host3. This leads to the corresponding macs being re-added to the bridges on...

Hello all, hm, I had to find out that this above "workaround" does not work. After some hour runtime the thing is exactly the same with the new "auto" macs. The setup consists of 3 proxmox hosts with a trunk port connected over 2 switches. Host 1 has the guest, host 2 shows the mac in the...

Hello all, regarding this problem I found something that may be helpful to others or for tracking down the problem. It seems that some (all?) of the duplicated packets have a destination mac that is preconfigured in the corresponding guest network setup. In my case they start with "52:54" or...

Hello all, I have a pretty standard setup for several linux guests on Proxmox. Lately I found out by monitoring the guest interfaces with snmp that there is traffic I cannot explain. So I tried to find the cause for it and found out that every guest connected to the same bridge and subnet gets...

Sure, here: https://pve.proxmox.com/wiki/VNC_Client_Access and last sentence reads: "Note: Using this method it not possible to set a VNC password. " (which means vnc access config via config file)

I just had to read in the wiki that when configuring vnc for a guest it is not possible to use a password. This is really unusable for customer access. How do you think one should enable customers to access their corresponding guests?

Can you please elaborate what that means. "containers" like "LXC containers" ? We have none in the setup. We are talking about the vm list on the left of the web gui... (as an example)

So there are no coders in your staff? Alphabetical sorting of a given list is "not so easy to implement" ?!? (sorry, couldn't resist)

Stay serious, please. You are already the second staff member that read this thread. And none of the two found it worth the time making a feature request for it. If that is an easy process, it should likely take just as long as answering in the thread - for you. For me on the other hand - since...

Well, easy-going to tell that. But if you already happen to follow quite a lot of the important projects there is not much spare time left. And honestly I would not start at this topic, but rather with - why does a proxmox cluster node change its ssh keys on occasion (happened 3 times during the...

Lets simply end with the fact that proxmox does not have the feature (compared to libvirt/virt-manager) although it would be dead simple to implement. In our case there is no wind*ws involved.

That's really not our use case. We use read-only drives often as backups where you can examine an older setup, and you must not be able to write anything there, even if it is thrown away afterwards. Else you cannot judge if the status is as it was when this snapshot was done.

One would prefer an solution inside proxmox GUI of course. Fiddling with the file base isn't really that transparent in this case. I was pretty astonished though that libvirt/virt-manager supports this out-of-the-box (and it was often used in my environment) whereas here it isn't even something...

Believe someone with years experience with glusterfs: it is dead slow because the authors/company refuses to implement it as kernel drivers.

That's wrong. It _does_ work in every direction. A packet from vmbr5 to vmbr4 is tagged because the bridge port of vmbr5 is named vmbr4.8. So on an outgoing packet the 8 vlan id will be tagged on. The same goes one step deeper. As vmbr4 has enp5s0f0.1007 as bridge port all packets outgoing there...

Hello, I try to protect a (second) drive of some vm. With qemu/virt-manager it was easy to flag a drive read-only. But I cannot find a corresponding option in proxmox. How can I do that? The drive is an nfs-mounted raw file, btw. -- Regards Stephan

Ok, I understand your idea. But since the tagging is needed outside the proxmox cluster this is no option. But I found a solution that you already mentioned elsewhere. There is only one additional bridge needed: auto vmbr4 iface vmbr4 inet manual bridge-ports enp5s0f0.1007...

Got an idea. Maybe everything is a lot more transparent if I describe a potential setup for this whole story. Lets assume you have 5 boxes with one lan port each. Lets assume you have 2 switches. Lets assume you have a proxmox cluster. Now connect the 5 boxes to switch 1 and tag each switch...