Search results

Please describe more detailed what client and telephony software you use and how exactly your users connected to it.

I have pfSense running smoothly as VM on Proxmox. It has several network on several virtual NICs. VLANs on switches and on Proxmox I can describe this solution more detailed, if you interested.

I'm not shure in routed configuration at this setup. There is an external router and host & VM has internal addresses. Also I've noticed mtu 9000, it means jumbo frames and must enabled in whole network chain including network adapters, bridges, switches and routers. If not, maybe set it to...

Check for duplicate IP addresses first.

It may corrupt corosync synchronization, quorum lost, etc.

This is not Proxmox issue. This is how iptables works. To write rules in the right way, you need basic knowledge of iptables and kernel packet filter logic.

iptables rules work ONLY on full match -- so, that rule works and pass traffic only when TCP packet have source port 8006 AND destination port 8006.

In my opinion, good way is to wrap ISP connection into separate VLAN using managed switch. For example, connect ISP cable to switch port #1 while Proxmox connected to port #2. Then setup VLAN10, name it "ISP VLAN": Port #1 will be untagged port. Remove it from default VLAN. Port #2 will be...

Try to remove S.Port 8006, leave D.Port only in last rule. Usually connections are made from random source ports,

What CPU usage and iowait you have on host and VM when delays occured?

Yes, it is possible. Read about Proxmox HA Cluster.

Create accepting incoming rule for SSH.

I use Windows 2008R2 AD DNS for internal use and two bind9 on my public IPs for domain zone.

This required to setup an own DNS server, at least caching, right?

Setup DNS on your host. Go to your host Web interface -> System -> DNS Specify one or more DNS servers there. If your VM cannot resolve domains, setup DNS on VM, this depends on what OS you run on it. common for linux if edit /etc/resolv.conf: nameserver 1.1.1.1 nameserver 8.8.8.8 But it may...

eno1 must be physically connected to an ISP or upstream router.

As an addition. First. If you do not pass eno1 network to VMs, then you do not need eno1 bridged. So you assign public ip to eno1 directly, this looks right. Second. If you have pubilc ip on your network interface, take care of security, at least setup firewall on Proxmox host. But do it...

Keep us updated and good luck!

Is your vmbr1 do not have slave interface? Please do not follow guides blind. Try to understand. Your ISP is gateway for your Proxmox host. Your Proxmox host is gateway for your VMs on Proxmox host. So, your Proxmox host acts as a router. And try to comment out 'auto eno1' in...

What specified in the 'gateway' parameter? It should be gateway ip, given by ISP.