Remote management
Hi,
I don't have the remote management enabled in the Administration page. Nevertheless, remote management is accessible through the public IP of the router. Is it a firmware bug? Anyone with the same issue?
Thanks,
Pedro
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Many routers support hairpinning (NAT loopback):
Hairpinning is a network process where traffic from an internal network that is directed to the network's public IP address is instead "hairpinned" or redirected back to the internal network to reach a server there. Also known as U-Turn NAT or NAT loopback, it allows local devices to access internal resources using the external IP address as if they were external users.
If that's the case, this is expected.
You should execute another test - run a hotspot from your mobile and connect a laptop to the hotsport, then try to connect the laptop to the router public IP address - you shouldn't be able to do that.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thanks for the feedback. That's what I thought, but somehow it's being exposed when not configured to it. I'll do it.
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the feedback.
Have you submitted the support email? Currently, I've seen a new support ticket under your email ID.
If you haven't yet, please also add some screenshots/files/logs showing how you found remote management is accessible through the public IP of the router when submitting the email.
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
I haven't submitted the email to support. I ran a few more tests and found that I can access the administration web UI from the public IP, but only when from the same internal network. Somehow, it resolves the public IP within the same private network. Is it expected?
Regards
- Copy Link
- Report Inappropriate Content
Many routers support hairpinning (NAT loopback):
Hairpinning is a network process where traffic from an internal network that is directed to the network's public IP address is instead "hairpinned" or redirected back to the internal network to reach a server there. Also known as U-Turn NAT or NAT loopback, it allows local devices to access internal resources using the external IP address as if they were external users.
If that's the case, this is expected.
You should execute another test - run a hotspot from your mobile and connect a laptop to the hotsport, then try to connect the laptop to the router public IP address - you shouldn't be able to do that.
- Copy Link
- Report Inappropriate Content
Thanks for the explanation. I've tested connecting to the public IP address from outside the internal network managed by the NX600 router, and I can't access the web UI. All seems to be working as expected, considering the U-Turn NAT or NAT loopback feature.
Regards
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 92
Replies: 6
Voters 1
