you will either need to install tailscale client on your kali vm and make the vm part of your tailscale network or you will need to setup some form of NAT/Port Forwarding/Routing on your PVE node
It's probably a routing problem, your incoming connection is on 192.168.2.x but the Proxmox server is on a different subnet (192.168.1.x)
if you run ip route on your wireguard server what does it show?
which subnet is the Windows PC on?
Firstly, I would not use iptables and pfsense together, it's making more complication than you need IMO
Normally, pfsense has the public IP address and then you can setup NAT rules on that to direct incoming traffic as you desire. The complication here is that you only have one physical nic on...
I think your main issue is that you have the server nic (enp3s0) bridged to vmbr0 - this is not correct. The hetner docs have this
auto vmbr0
iface vmbr0 inet static
address <main IPv4 address>/32
bridge-ports none
bridge-stp off
bridge-fd 0
This setup relies on...
There is a very good example of this kind of setup on the netgate site, although it's talking about pfSense rather than opnSense, the general principals are the same.
pfsense on proxmox guide
Setup proxmox and give it an IP in the range you have chosen for your home lan - e.g 172.19.1.101 and...
I'm trying to run ESXi 7.0.3 under proxmox v8.0.4 on an AMD Ryzen host
ESXi installs OK but I can't get a VM to start. I think the PVE Host is configured ok as I am able to run a VM on a nested PVE instance.
ESXi VM config
balloon: 0
boot: order=sata0;ide2;net0
cores: 6
cpu: host
ide2...
I think you're missing the option to enable forwarding on the host, your network config file should include
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
these configs also normally include the following commands
post-up iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1
post-down...
only vmbr0 needs a specific IP address, you can still create a bridge for your extra network interfaces if you like, just don't assign any ip addresses to them. You could still create a VM, attach it to vmbr2 and give the VM an IP of 192.168.31.42, that would work. Alternatively, you could bond...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.