Hello,
After the upgrade (6.44.5) - the port forwarding is not working.
add action=dst-nat chain=dstnat dst-address=!192.168.88.189 dst-address-type=local dst-port=12000 protocol=tcp to-addresses=192.168.88.189 to-ports=12000
What is wrong with it?
Thank you in advance.
If the goal is to reach inn to IP 192.168.88.189 on port 12000/tcp, try this instead.
add chain=dstnat action=dst-nat to-addresses=192.168.88.189 protocol=tcp in-interface=ether1 dst-port=12000
PS change in-interface to your outside interface, or use in-interface-list=WAN if you have an outside group WAN
.
Thanks for the answer.
Should I use pppoe-out1 for outside interface? But with pppoe-out1, as the outside interface, it does not work
It is working for internal IPs without the outside interface, or using the bridge. So far, I have no solution for external IPs.
My guess is that the problem is actually somewhere else, because it’s highly unlikely that upgrade would break something as basic as this. And even if it did, there would be many more people complaining.
Does the rule’s counter increase? If not, either no such packets are coming to router or they are caught by some other rule. In that case, check directly on interface with Tools->Torch if you see them there. If this rule gets some packets, then check what happens with them next, you can use Torch again on outgoing interface (where 192.168.88.189 is connected to) and you should see them there. If not, check what happens with then in forward chain.
Many thanks to all for help.
@Sob - thanks for the suggestion.
It was an undefined problem with dns (dynamic). Today, everything is ok.
Thanks again.