Community discussions

 
zhup
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Thu Dec 03, 2015 10:10 pm

After the upgrade - the port forwarding not working

Sun Jul 14, 2019 5:37 pm

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.
zhup
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 1302
Joined: Sat Dec 24, 2016 11:17 am
Location: jo.overland at gmail.com

Re: After the upgrade - the port forwarding not working

Sun Jul 14, 2019 7:03 pm

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
 
How to use Splunk to monitor your MikroTik Router

MikroTik->Splunk
 
 
zhup
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Thu Dec 03, 2015 10:10 pm

Re: After the upgrade - the port forwarding not working

Sun Jul 14, 2019 8:44 pm

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
Image
It is working for internal IPs without the outside interface, or using the bridge. So far, I have no solution for external IPs.
zhup
 
Sob
Forum Guru
Forum Guru
Posts: 4655
Joined: Mon Apr 20, 2009 9:11 pm

Re: After the upgrade - the port forwarding not working

Sun Jul 14, 2019 9:23 pm

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.
People who quote full posts should be spanked with ethernet cable. Some exceptions for multi-topic threads may apply.
 
zhup
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Thu Dec 03, 2015 10:10 pm

Re: After the upgrade - the port forwarding not working

Mon Jul 15, 2019 10:48 pm

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.
zhup

Who is online

Users browsing this forum: No registered users and 33 guests