NAT not working when added to controller management from stand alone
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I moved my ER605 from stand alone mode to controller management and applied the NAT rules again and both ports show closed 80 and 443. I checked them on portchecker.com and shields up which noted they were closed and not stealth like all of the other ports checked.
The NAT rules were written to the same IP address and ports in stand alone mode worked fine. Is there some other setting that is over riding this as I have just made the most basic changes to the firewall rules.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@dodgeman It works in standalone mode, and theoretically in Controller mode. Did you set the source Port and destination Port in controller mode the same as in standalone mode? I do not understand which firewall Settings can be changed to prevent NAT failure. Can you disable the firewall to make NAT work properly?
- Copy Link
- Report Inappropriate Content
after the success of adoption, you can consider rebooting it. this will reboot the kernel as well.
- Copy Link
- Report Inappropriate Content
After its joined you need to add the NAT again and that is when the NAt does not work. I have rebooted the router and no change
- Copy Link
- Report Inappropriate Content
there is an issue if you use it in controller mode, 80 443 will be used for the controller update. only when you in standalone, you can use 80 and 443.
https://www.tp-link.com/en/support/faq/3281/
I believe it works if you change it to a different one
- Copy Link
- Report Inappropriate Content
Thanks I've been looking for that, I figured it was the cause and the solution would be to adjust the ports used. Well reading that I cannot change the mgt ports on the router after the move to controller management. I've even checked the omada.properties folder on the controller to see if there is a way.
I do not understand since I modified it on the router in stand alone mode prior. I moved 80 to 8080 and 443 to 8443, now I cannot unless I am missing something.
- Copy Link
- Report Inappropriate Content
because when you make an adoption, your config will be erased first (equal a reset) and then adopted.
so what you made, the port changes mean nothing to the controller.
i think there is no way to bypass this until a fix is released.
- Copy Link
- Report Inappropriate Content
none of your settings in standalone would be applied to the router mode.
that's why it's useless even you have set it in standalone. and you still access the router by 80 and 443
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 735
Replies: 7
Voters 0
No one has voted for it yet.