You should be able to get that from your manufacturer's docs. Since it's on the far side of the FW, it's no different than going to any external website. My last 2 modems, Motorola and Netgear) used 192.168.100.1 while I use 192.168.0.0/24 inside.

@jkiel Yes, but this is only true for NAT reflection. And as I stated in my first sentence above, NAT reflection just reflects the NAT rule to other interfaces. So the proxy is only applied to traffic coming from OTHER interface, not from WAN, where the real NAT rule is defined on. Traffic forwarded from WAN still keeps its origin source address. Simply sniff the traffic on the LAN to verify this.

@eeebbune Port forwarding is typically used for inbound connections natting is for outbound It is not clear what the issue is and what is inside HM_PBX_DESK_phone too

@viragomann Hi again, I believe I have made it work now. The only thing I did was to push a route from the server side, like push "route 192.168.123.0 255.255.255.0" (this is a route to a LAN on the VPN server). I am not using this subnet in any way seen from the client side, so kind of strange that just adding a route made the NAT setup work. That made the client side use the ovpnc interface instead of lo0. Now both the internal monitor pings and the DNS lookups via the ovpnc interface translates correctly. Thanks again for the assistance, viragomann.

@nerdile In case anyone is struggling with a similar issue in the future, one thing I noticed that could indicate this issue is that the firewall shows allowing the SYN packets from the LAN client but never shows any responses later. (You have to turn on logging of your default allow rule to see this traffic flowing.)

@noreast-it said in Not able to open Odoo required ports and allow through the firewall.: a virtual IoT box running on a windows server 2019 VM in order to connect to all needed printers via ethernet. Well any firewall rules you need to do would be on that VM host then, not on pfsense. But nowhere do I see any talk of opening a port forward in your firewall allowing any ports inbound unsolicited from the internet. You clearly see the virtual iot box in their system.. Why it can't print would be on that box or their system.. Has nothing to do with firewall rules or port forwarding on pfsense.

Very helpful, thank you.

@sogorman well you don't really need to do a 1:1, you could do simple port forwards for the ports you want vs all of them ;) So you want this fqdn to resolve to the internal IP? Just setup a host override so your local.redacted.com resolves to the 192.168.0.7 What your seeing now is WAD, Works As Designed.

@paulvanduijn I have the exact same problem on two pfSense VMs running in KVM with VirtIO drivers. So far I cannot find a solution online. I tried to Disable hardware checksum offload and Disable hardware TCP segmentation offload and it did NOT work. My download speed is 500-600 Mbits but upload speed is 0.1 Mbit. This happens on the latest pfSense 2.7.2 and pfSense Plus 23.09.1

As in, Halt System. Then push the power button to turn back on.

In reviewing the same concern in opnsense, it appears commits were made some 3 years back to enable this exact functionality. https://github.com/opnsense/core/issues/5005 Any chance of this getting ported to pfsense?

@viragomann Thanks to your explanations, I understood and cleaned all pfSense rules and configs! Thanks you so much Viragomann !