dst-nat/dst-port and HTTPS redirection problem
Posted: Thu May 21, 2009 5:43 pm
hello!
We have RB450 which is sitting between I-net and local network and doing traffic shaping, firewalling, port forwarding and some more functions.
We have many units inside our network who has http-access to give the possibility of control.
To give the http-access to these units from outside (I-net) I configured the RB this way:
222.11.123.4 -- public IP of RB
192.168.11.227 -- local IP of a unit
/ip firewall nat>
add action=dst-nat chain=dstnat dst-address=222.11.123.4 dst-port=34227 \
protocol=tcp to-addresses=192.168.11.227 to-ports=80
so when a client hits http://222.11.123.4:34227 in it's browser, it to be asked login/pw then gets access to 192.168.11.227:80 -- the problem is solved. BUT, recently we've updated the firmware of that unit and discovered that from now after successful login the unit trying to redirect the client to https (port 443) !, but, as you can guess, it doesn't work. I tried to add similar NAT rule for port 443, like:
/ip firewall nat>
add action=dst-nat chain=dstnat dst-address=222.11.123.4 dst-port=54227 \
protocol=tcp to-addresses=192.168.11.227 to-ports=443
so when I hit https://222.11.123.4:54227 in my browser it asks for login/password, but after that the browser shows white blank screen and you can wait forever...
Please help me to bypass this obstacle.
Thank you in advance.
We have RB450 which is sitting between I-net and local network and doing traffic shaping, firewalling, port forwarding and some more functions.
We have many units inside our network who has http-access to give the possibility of control.
To give the http-access to these units from outside (I-net) I configured the RB this way:
222.11.123.4 -- public IP of RB
192.168.11.227 -- local IP of a unit
/ip firewall nat>
add action=dst-nat chain=dstnat dst-address=222.11.123.4 dst-port=34227 \
protocol=tcp to-addresses=192.168.11.227 to-ports=80
so when a client hits http://222.11.123.4:34227 in it's browser, it to be asked login/pw then gets access to 192.168.11.227:80 -- the problem is solved. BUT, recently we've updated the firmware of that unit and discovered that from now after successful login the unit trying to redirect the client to https (port 443) !, but, as you can guess, it doesn't work. I tried to add similar NAT rule for port 443, like:
/ip firewall nat>
add action=dst-nat chain=dstnat dst-address=222.11.123.4 dst-port=54227 \
protocol=tcp to-addresses=192.168.11.227 to-ports=443
so when I hit https://222.11.123.4:54227 in my browser it asks for login/password, but after that the browser shows white blank screen and you can wait forever...
Please help me to bypass this obstacle.
Thank you in advance.