Search results

So I scrapped out an old server so i dont play around with a live system. Dropped proxmox and on one lan i have 192.168.10.10 as an ip to connect to our main network. And for the second one i have 192.168.42.3 and for the VM i have .42.5. Which interface should i bridge?

Hi Adayge, I can ping the DMZ interface(192.168.42.1) from the proxmox(ip addr 192.168.10.34) server itself but i cant ping anything from the VM(192.168.42.5) edit: for people to get a better idea what the current setup is im attaching a quick networking diagram

Hey guys, Im trying to implement a VM with SecureLink which should be residing in the DMZ zone. The proxmox server has both nic bonded and connected to our main network 192.168.10.x which is connected to port 4 of our firewall/gateway. On port 5 i have the DMZ/network 192.168.42.1, nothing is...

Quick update: Ive been running 4.15.18-14-pve #1 SMP PVE 4.15.18-39 kernel for the past 10 days on all 3 of our nodes and have not noticed any of the problems mentioned before.

I'm not sure if this is a problem similar to this one https://forum.proxmox.com/threads/vm-network-freeze.37161/ but it seems like it. I would suggest trying older kernel( I'm currently using kernel - 4.15.18-9-pve) with no issue on 5.4.3. With the latest kernel, I'm getting similar problems...

I wish your solution would've worked. I have problems with both, win and Linux vm's, but the interruptions are totally weird. And from the looks of it seems like those vms just their knowledge of the network and they need some time to rediscover everything but also drops the connectivity. The...

Quick update and reality check! I don't know if this is still the same issue, but it definitely looks like it so I'm gonna post it here. After having a very smooth sail for a while i got one of our server updated with 5.4 and running 4.15.18-12-pve #1 SMP PVE 4.15.18-35, and after that im...

After running kernel 4.15.18-7-pve for a couple of weeks we HAVENT encounter any of the problems mentioned before by or any of the other users. The nod is running fine and it is housing mix of LXC and KVMs.

One of our problematic servers got moved to new hardware(not related to this problem) so I'm running fresh proxmox install with Linux 4.15.18-7-pve kernel and am testing it to see if the problem still persist. Ill update this post in a day or two.

Just tested it, and the problem still persists with pve-kernel-4.15.18-1.

I just rebooted the server, hold shit down and from the advanced menu choose 4.15.17-1

The nod has mixed architecture of VM's, a windows vm, a bunch of Ubuntus, Red Hats, and CentOS. I've noticed that I'm running 4.15.17-1 kernel on my other nod so I tried to downgrade the kernel to 4.15.17-1 and I'm watching it now, it looks better still no drop. I'll post an update after some...

Well, I did share more info like PVE and kernel versions and even a little bit of investigation, but I've never got an answer. Having a ping running from the VM's it is not really a solution to this problem. I thought that staff members will at least try to help out, anyhow ill persist with my...

Hi there, Im not sure if the problem is the same or it needs to be put in a separate post, but here we go. We have a 3 node cluster, and we didint have any problems before upgrading to 5.2. The problems we are experiencing are occurring only on one of the nodes and the problem seems to be...