Search results

As far as I see, question is simple as banana. First, you must understand, do you need pfSense in this scheme or you do not, as mentioned above by bobmc. Outbound NAT and port forward for your VMs can be performed by ISP modem. So, if you have modem and pfSense, then you have 2 routers. Is it...

If your provider gibes /30 block for you, it gives 4 IPs: 1: network address; 2: provider gateway; 3: one you use in your VM; 4: broadcast address. So, with /30 block you can use only one IP (3) for your VM.

Remember that if you have 32 IPs in different networks, you need to setup 32 gateways. But if you have 32 IPs in one network (/24 for example), you need only one common gateway for these IPs.

You have VLAN and MTU settings on the vmbr2, check these settings on your router/switch and nas. As mentioned above, there is no needed ping from specified interface, system choose interface itself. And do not connect NAS via router, use switch or direct connection.

Well, at least you've got a working solution.

TTL=63, seems that pings goes through router. Try traceroute, not ping.

Is there anything unusual in /var/log/syslog? And please show /etc/network/interfaces from all 3 nodes.

There is nothing wrong to have multiple interfaces, one per VLAN, unless you have hundreds or thousands on VLANs, of course. This gives you easer network setup inside VM. Here I have similar setup with PFSense VM: Interface net0 is LAN interface within PFSense Interface net1 is WAN interface...

Wireguard key points are public key exchange between two peers and address setup, that all.

This behavior is normal. You have one gateway 10.10.100.1 and can ping outside from interface at the same network, vmbr0. Other interfaces has no gateways (and should not in common cases), so network stack do not know where packets from that interfaces needs to be routed. From that interfaces...

Just leave WLAN unconfigured at this time. Maybe you will configure it later for some purposes. Remove auto wlp3s0 from /etc/network/interfaces or comment it out. Also replace iface wlp3s0 inet static with iface wlp3s0 inet manual Next, you have vmbr0 already bridged with you LAN connection. Use...

Well, maybe 5.15 kernel has buggy nic module. I heard Proxmox has 6.2 kernel, can you try it? And try to disable auto-negotiation on switch side, force connection speed to 2,5 Gbps or 1 Gpbs.

Usually you should not use two interfaces at the same network. Disconnect WLAN and and make full working setup using LAN only. As I can understand, the second interface (WLAN) just confusing you.

Now you have 2 interfaces in one network, wlp3s0 and enps25. Is there any special reasons to have that scheme? Common situation is one interface per one network.

Check cables and try to replace cable connected to problem NIC. Also, try to upgrade switch firmware.

Are network cards connected to a 10G switch? Try to disable flow control on SFP+ ports on switch, if it possible.

Some routers has built-in VPN server, PPtP, OpenVPN, Wireguard, etc. If your router supported by OpenWRT, you can install an OpenWRT firmware and set up Wireguard VPN, it simple enough.

Interface IP address and gateway must be in the same network. So, if you gateway is 192.168.2.1, vmbr0 ip address might be 192.168.2.5/24 for example. It seems that your CT has no ipv4 address. Maybe it cannot get it from dhcp?

Vicidial has its own web interface, right?

Maybe it better to use web interface for users instead of connect directly to Proxmox?