Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - tantkomo

#1
That was it, what weird default behavior, oddly enough I didn't have to ever use that setting before. I guess it has to be a new addition to the firewall.
#2
Quote from: Monviech on September 28, 2023, 12:57:02 PM
I remember this:

(its german)
https://forum.opnsense.org/index.php?topic=35920.0

The solution was to enable "Advanced features: reply-to" with the VPN interface in the firewall rule that allows this port forward.

If I understand this right, I should enable the reply-to setting in the firewall rule on the VPN WAN interface that is generated by the port forward rule.

Issue is I don't have the option to edit the firewall rules generated by port forward rules and the port forward rule does not have such an option.





Unless I misunderstood where this option should be set.
#3
Hello,

I have a problem that has been driving me crazy for a week now. I had a very similar setup before and due to moving I had to redo it on a different machine.

Long story short I use AirVPN as a second WAN, I used to use the old OpenVPN client but I now switched to instances [new], client connects perfectly fine, hosts I want to go out over the VPN gateway go through it, but port forwarding through it simply isn't working no matter what I do.
The weirdest thing of all is that I see packets being logged by both the port forward rule and the firewall rule created by it.

To further test this I made a local Nginx site which I can access perfectly fine locally, but when I try to access it over my AirVPN WAN IP, both the firewall rules log the traffic as allowed which is expected, but I cannot load the page.







Any help would be greatly appreciated because I don't know what else to try here.