XR500 WINDOWS VPN BUG

[BIG__DOG]

Hi.

 

 

I have noticed a bug in the dumaos/netgear firmware. When connecting to P.I.A via their wondows application as there is no current option to use them on the XR500 I have noticed that the router cannot be accessed by the routerlogin.net address only via 192.168.1.1. I cannot work out why this would be and why being connected to a vpn would stop access to routerlogin.net.

 

I have added a sceenshot of the page that appears if I use routerlogin.net

 

 

B.D

 

[Netduma Admin]

Thanks BD. This is the NETGEAR side so I'm guessing here, but I think that website probably looks at your public IP when you connect to it to redirtect you back to your LAN. But because you are masked by your VPN it doesn't work. I'm no dev so it's a guess! 

 

Fraser will be online tomorrow so he can take a look at it too.

[BIG__DOG]

Thanks BD. This is the NETGEAR side so I'm guessing here, but I think that website probably looks at your public IP when you connect to it to redirtect you back to your LAN. But because you are masked by your VPN it doesn't work. I'm no dev so it's a guess! 

 

Fraser will be online tomorrow so he can take a look at it too.

I thought that may be the reason but am not sure.

[Fathomless]

i do not know if you can link it to Netgear problem.

 

I think Corp VPN should bypass private ip range at least it works for me like that.

you mentioned that IP works, i would guess if you try nslookup you are not be able to resolve routerlogin.net.

that cold be because VPNs like ip vanish would probably use another interface and your DNS response might not come from the router.

 

if that is the case you could try hosts or even lmhosts files just to modify name to IP mapping. This would be static mapping it will take priority for name resolution, and fastest DSN server

 

location of the hosts and lmhoshosts:  C:\Windows\System32\drivers\etc, i think you have to rename lmhosts.sam to lmhosts (used for netbios name if you want shorten the name you could use name "R" with ip 192.168.1.1)

 

Disclaimer: i cannot repor exact situation; i just did reproduced similar scenario.

 

 

here is scenario i have two net gears, R6700 - access point with IP 192.168.1.9 and XR500 -router with IP of  192.168.1.1

normally i am connected to R6700 while testing disconnects, so for debugging i need to switch to XR500 WIFI. 

1. doing ping by dns name, i expect name to be resolved to 192.168.1.9

C:\Users\Administrator>ping routerlogin.net

Pinging routerlogin.net [192.168.1.9] with 32 bytes of data:
Reply from 192.168.1.9: bytes=32 time<1ms TTL=64
Reply from 192.168.1.9: bytes=32 time=1ms TTL=64
Reply from 192.168.1.9: bytes=32 time=1ms TTL=64
Reply from 192.168.1.9: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

 

2.hosts file modified with entry: 192.168.1.1   routerlogin.net; saved and we do ping again

 

C:\Users\Administrator>ping routerlogin.net

Pinging routerlogin.net [192.168.1.1] with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 15ms, Average = 6ms

 

3. now i can connect to XR500. when hosts file modified it will always come to XR500

verifying if DNS still pointing to 6700 and it is. After change you might need to use NBTSTAT -Rr and  ipconfig /flushdns, to flush cash or reboot computer if your results are different

C:\Users\Administrator>nslookup routerlogin.net
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
Name:    routerlogin.net
Addresses:  c0a8:109:6674:363:6f6d:0:1c00:1c0
          192.168.1.9
 

[Netduma Admin]

Wow, thanks Fathom! This is very helpful. 

 

By ‘Netgear problem’ I mean that it’s on their part of the firmware, so we don’t know how it works as well as we do our own firmware.

[BIG__DOG]

Thank you for that Fathom, very helpful indeed!