local proxy server needs to be on a different subnet for nat to work.

@sweety Is there a typo here? This feels like a trick question These are not really in the same category. Please google what is NAT. Please google what is OpenVPN.

@skysurf76 Official response from Ubisoft on their forums...."Hey there, thanks for getting in touch! I'm sorry that you are running into this issue. Due to technological limitations two players are only able to play from the same network if one of them invites the other. Please keep in mind that you will have to complete port forwarding to the system that is the host, although I imagine you've already done so. Here's an FAQ with the ports, just in case. Alternatively you both can play if you get invited to groups by people outside of the local network. " Their explanation doesn't make any sense. They took their xboxes to their dads and it magically worked fine, unless the kids did something different with their sequencing as to how they grouped up. I'll interrogate them soon.

@ta2oo The packets shown in these captures are all marked as retransmissions. That is a typical indication for enabled checksum offloading on Proxmox / KVM. But maybe there is another basically wrong configuration network in your virtual network. Are there also issues with other network protocols?

All depends on what your doing, what your serving, etc. Both methods are valid - you can get some security behind a reverse proxy like HAproxy.. But its normally easy to just forward based on IP than having to deal with the headers, etc. But with using a proxy you can also do some really neat stuff as well..

@cool_corona said in 10 port forwards.... one is not working.: all is fine for now. Other then horrible exposure of rdp to the public internet via a port forward ;)

@dennis-westhuis said in Port forward through site-to-site VPN: @edofede how did you solve this problem exactly? He solved it like how he said he did, by using OpenVPN. With OpenVPN, all these IPsec issues are non-existent. I should know because I came from using OpenVPN to trying out IPsec.

@ash-0 You don't map the OpenVPN subnet to your LAN, you have to map a fictitious network or IP. As I mentioned, for instance you map 172.29.136.15 to 192.168.0.15. So the client has to call 172.29.136.15 when he want to access the .15 in your LAN. I think, it may work without adding virtual IPs to the VPN interface, cause the client directs the packets to your VPN servers IP. Never done it with port forwarding, but should work with 1:1 at all. If it doesn't you have to add a virtual IP for each single LAN address the client should be able to access.

@tigs redirect to proxy although this thread is very old,basics still stand the gui i guess has changed so you might need to figure out where exactly the settings apply.

@derelict Yep, we discovered that the hard way. I had to remove the P2 with 0.0.0.0/0.