dstnat and srcnat Port Forwarding
Posted: Sat Aug 08, 2015 2:31 pm
Good afternoon,
I am currently having problems accessing some of the new TP-Link routers when port forwarding on the mikrotik router.
we access the router via the Wlan interface on a bridge IP address and then i would like to access a router that is on the Ethernet side of the router. The Wifi Router is plugged in to the LAN port and has the DHCP removed, this means that i have to use a srcnat and a dstnat to make sure the router thinks that i am coming from the local address and not our bridge address.
Recently in the new firmwares for TP-Link and Nucom, we cna not access the router this way.. It shows the login page but as soon as you try to login the screen just goes blank and if you reload you jsut go back to the login page.
the dstnat and srcnat that i use is this:
/ip firewall nat
add action=src-nat chain=srcnat comment="NAT access to wifi router" dst-address=192.168.0.222 out-interface=ether1 to-addresses=192.168.0.1
add action=dst-nat chain=dstnat dst-port=80 protocol=tcp to-addresses=192.168.0.222 to-ports=80
192.168.0.222 is the IP address of the TP-Link or Nucom router on its LAN side with no DHCP. This means that it is running as a bridge and all DHCP requests come from the Mikrotik board.
The Mikrotik board on the Lan side had an IP of 192.168.0.1/24 and a DHPC from 192.168.0.100 - 192.168.0.200
Does anybody have the same problem or any idea how to fix it?
Thanks
I am currently having problems accessing some of the new TP-Link routers when port forwarding on the mikrotik router.
we access the router via the Wlan interface on a bridge IP address and then i would like to access a router that is on the Ethernet side of the router. The Wifi Router is plugged in to the LAN port and has the DHCP removed, this means that i have to use a srcnat and a dstnat to make sure the router thinks that i am coming from the local address and not our bridge address.
Recently in the new firmwares for TP-Link and Nucom, we cna not access the router this way.. It shows the login page but as soon as you try to login the screen just goes blank and if you reload you jsut go back to the login page.
the dstnat and srcnat that i use is this:
/ip firewall nat
add action=src-nat chain=srcnat comment="NAT access to wifi router" dst-address=192.168.0.222 out-interface=ether1 to-addresses=192.168.0.1
add action=dst-nat chain=dstnat dst-port=80 protocol=tcp to-addresses=192.168.0.222 to-ports=80
192.168.0.222 is the IP address of the TP-Link or Nucom router on its LAN side with no DHCP. This means that it is running as a bridge and all DHCP requests come from the Mikrotik board.
The Mikrotik board on the Lan side had an IP of 192.168.0.1/24 and a DHPC from 192.168.0.100 - 192.168.0.200
Does anybody have the same problem or any idea how to fix it?
Thanks