Doing my part to be a good forum member I have been researching this all day, and most of yesterday. Please excuse my ignorance as I’m new to this sort of thing, but really want to learn. I have used consumer routers in the past (Netgear, Linksys, Belkin) I am simply looking to forward SSH port 2230 to my computer. I have followed this http://wiki.mikrotik.com/wiki/Manual:Initial_Configuration#Port_forwarding using the web UI to the letter but still no luck. I fully realize there is probably some stupid mistake that I am making. Does anything have to be done to the firewall rules themselves or because NAT comes before in the chain it doesn’t matter?
Of course as soon as I make my post I figure it out…it’s working from outside my house but not inside so I assume a loopback issue. How is this accomplished in the NAT or in the Firewall?
Right after I made that post I reset my router so that I could set it up again and make sure I understood what I did the first time. I am stuck again with the hairpin NAT issue. I thought it was the same as last time but no luck. Could someone please tell me what I’m doing wrong?
The problem now is when I attempt to access the webserver from outside my house it works great! If I try to access the webserver using the local IP 192.168.0.1 it works great. If I try to access the webserver using the public IP from inside my house the connection breaks. The configuration I last posted was one I created by following the guide to create a hairpin nat which perfectly describes my problem but the published solution doesn’t seem to work.
This is the configuration now but it still doesn’t work.
In the mean time I’ve also tried resetting the router, restarting the modem, switching the modem, and using a different webserver. Same problem, but I’m sure it’s the router.
Do not specify the in-interface because you want to dst-nat to your local server for all in-interfaces. As you have it, Rule 0 lets a lan request for 1.1.1.1:80 go out ether1-gateway. Which is not what you want.
Rule 1 takes care of src-nat when the request comes from the lan only.
Rule 2 add: “out-interface=ether1-gateway” You don’t want to src-nat everything, only what goes out ether1-gateway.
If you access the internet more than the internal server, move rule 2 before rule 1. Less processing.
@All the people who have offered advice thank you so much!!! You’re willingness to share your intelligence has significantly lessened my blood pressure. In particular reverged thanks so much for not only helping me fix the problem but explaining why so I can learn.
I have the same problem!I spoke with my girlfriend and told her to open the address with chosen port by me!Everything works!I tried to open local host with special port!Works!But when I try to open public IP from my house nothing is happened!Just connect to …and stuck!
We srcnat everything from localnet to localnet going out anything but the WAN. It is probably overspecified here, but it works inside and out.
Port forward WAN:222 to 192.168.88.160:22.
EDIT: I thought I tested this. Apparently didn’t from outside network. IT DOES NOT WORK FOR INCOMING TRAFFIC PORT FORWARDING.
For the life of me, I cannot debug this firewall. Nothing works as expected. Input chain port 444? Nothing. Ever.
I have wasted enough of my time on it. I think I am going to trash this mikrotik and get something that can do port forwarding sensibly. This isn’t fun anymore.
EDIT: Is it turned on. Is it plugged in. DDNS was not up to date. External tests obviously fail.
I reverted to a previous implementation of the hairpin NAT which generally makes more sense to me and integrated it with the default configuration of the mikrotik: