Remote Login redirects to local LAN devices
planned
I
Ian England
I was trying to use the remote login feature to login to some Access Network WAPS on my clients network. It seemed to correctly follow the links and redirects but at the last moment re-directed itself to our local network for that IP address. To explain - my clients WAP is at 10.0.1.6 on their private network network across town. I used OVRC to remote connect to that WAP, like I have done a dozens of times with other clients. When OVRC finally made the last remote connection processes, it suddenly redirected to MY OWN local LAN 10.0.1.6 address, which just happened to be a Araknis Network WAP on my local LAN. I tested this issue in the legacy version and could not reproduce it. It appears to only happen on the new version.
It appears that the connection port is missing in the new app for the Access Networks WAPS as well ( I see the port 443 link, but not the port 80 link ), FYI.
D
Dan Stevens
Its been over a year now and this problem is still there. Im trying to connect to a Draytek router and I am redirected each time. Also seeing the same issues with a couple of other routers and devices.
The draytek tries to redirect to here
https://192.168.1.1/index.php/cgi-bin/webporshow.cgi?target=http://webconnect.ovrc.com/
James Zabel
planned
We're in the process of fixing this, thanks! This will be updated in the next OvrC Pro firmware release.
M
Mark feinberg
I would recommend always using a different IP scheme for clients than you use at home or the office. Connected remotely to a network using the same IP addresses will often result in this issue.
I
Ian England
Mark feinberg: I disagree simply based upon my experience. Many years of remote connecting into hundreds of clients via OVRC, never had the issue before. Also, my local LAN happens to have multiple VLANS at my office, the WAPS just so happen to be on .1 is all. My PC is on another. But it also worked fine on legacy OVRC today, just the pro freaked out.
*shrug, who knows.
C
Caleb Purvis
Mark feinberg: Thats not the issue, it happens even if the subnets are different. In my experience it seems to be whenever the device you are connecting to has it's own redirect. It redirects you to it's own IP, however since that IP is a local address the browser attempts to connect on your local LAN instead of using the tunnel.
If you happen to have a device on your local LAN with that IP you will be connected to it instead, if not you just get a 404 error.