Search results

Would a restart not clear the arp tables anyway? I restarted everything multiple times, and it seemed to make no difference.

I share your sentiment and think PVE should be made "cloud native" as you call it. A great additional, which I have only recently started playing with, is SDN integration into the GUI. To have formal kubernetes support would be really great! As far as auto-creation of clusters is concerned...

As with the other issue I could not resolve once I cleaned up the old bridges (how can that be??) and restarted the node, everything came up daisies. For the life of me, I cannot explain it, and I hope I don't have to plough through weeks like this again! o_O:cool:

This is weird. I removed the bridge VLAN11 from the SDN and recreate it, then assigned the bridge to the applicable devices and it works. 100% the same as what I had before. This was driving me mad and now it has just numbed me... At least it's working now. Some more feedback: I think this...

I have a few vlans set up manually as can be seen from my config here: I have now established that VLAN 35 is actually working 100%, one I set up manually as being eth2.35 but not VLAN aware. Now for the SDN config... I'll compare the generated config with the manual one.

After a debug session with NVidia on the Mellanox switch, we have found that the switch is not the culprit and it actually registering the proxmox nic mac addresses and passing the traffic. So it's back to the config of proxmox is seems.

I have four nodes with LAN addresses 192.168.131.1, .2, .3 and .4 . These are all configured identically except for the difference of the last octet of an ip address. So NodeA has .1, B has .2, C has .4 and so on. NodeB for example: vmbr0 is the LAN and it's is also the LAN on a pfSense...

They can only ping each other when they're on the same node. I corrected myself after posting that in the first message, so apologies if that was not clear. I have since found that there are messages on the switch that say the VLAN is being filtered, so I've taken it up with their tech support.

If that was the case, then I would be able to ping at least the host node's address from the windows guest, but I can't. I have now configured an Ubuntu LXC, so test that. The address is 192.168.142.91. If I have the LXC running on the node where the pfSense guest is running, then I can ping...

Thanks for that clarification! So I should really just set up a non-VLAN aware Vnet and work with that for now. So maybe I should rephrase my problem then: If I have set up a Vnet and Zone, it creates a bridge tagged with the VLAN. Then, when I add that bridge to a KVM guest machine, the...

CORRECTION: On checking this again, here is what I actually get: I can ping the first pfSense VLAN 11 address from any node. (192.168.142.252) I cannot ping the backup pfSense VLAN 11 address from any node, nor from the first pfSense (192.168.142.253) I can ping the CARP virtual IP from any...

I'm experimenting with the SDN service and have not been able to figure this one out: If I create a Vnet (in my case 11) and tick "VLAN aware", then I cannot define a subnet. If, on the other hand, I untick "VLAN aware", I can define a subnet. What is the point of this and how does one...

The beauty of using free/libre software is that one can use it for what one wants. We have a cluster of older repurposed machines that are used as a development and testing environment, be backup to these and it does a great job of it. Surprisingly, the response times are not bad at all. In...

Just from experience I would think that you should drop one layer of proxmox (I cannot see why you need to run proxmox in a VM inside proxmox when proxmox provides nice features like pools & SDN to keep things separated) and run your you VM with the containers on a proxmox instance that is not...

I just thought about it a little more (and read up somewhat) and understand that the linked clone is based on a snapshot of the template. So once a snapshot is made, all changes go to the clone. If the template is changed, the clone still refers to the snapshot and does not include the...

I'm surprised to learn that a linked clone cannot be updated by updating the template the clone is linked to. Why is this? Is there a technical reason that one of the dev's here could explain. If it where possible to update a template and let the linked clone act modification it would be a...

I don't see much feedback on your issue, @henning, and I'm wondering if you managed to figure this out?

We ended up recreating the VM and it runs perfectly now. What went wrong we will probably never know.

No joy! It still doesn't succeed in writing to the disk properly.

Of course! I changed that to scsi0 and then fixed fstab in FreeBSD to use the changed name and now it seems to be fine.