Bypass account does not do anything - not bypassing
Hi,
I have set up moderate Ievel of security for my home network which is connected to the Internet by a DGND3700. Everything worked fine for the network level control. I then followed all the instructions of setting up a bypass account so that I can enjoy lower level of control when needed. However, I cannot get the bypass account to work at all. It does not matter whether I logged in to the bypass account or not, I am still governed by the network default level of control. What could I have done wrong?
Thanks,
-
Did you ensure that you do not have a network at https://dashboard.opendns.com/settings/? Your only dashboard is at https://netgear.opendns.com/, and the "normal" OpenDNS dashboard should not be used with LPC.
Did you successfully create the bypass account through the Management Utility or Netgear Genie?
Do you run the User Utility on the computer to login to the bypass account?
You may want to post the output of the following command here:
nslookup -type=txt debug.opendns.com. -
Hi,
I am 100% sure that I don't have a network managed by OpenDNS. I checked many times.
I created the bypass account through the Management Utility. Netgear Genie is not compatible with my router (DGND3700 V1). It crashes the router if I run it.
I used the User Utility on the computer to login to the bypass account and it was successful.
On running the command nslookup -type=txt debug.opendns.com, I got the following result. What does it tell you?
1.1.168.192.in-addr.arpa
primary name server = localhost
responsible mail addr = nobody.invalid
serial = 1
refresh = 600 (10 mins)
retry = 1200 (20 mins)
expire = 604800 (7 days)
default TTL = 10800 (3 hours)
Server: UnKnown
Address: 192.168.1.1
debug.opendns.com text =
"server 11.syd"
debug.opendns.com text =
"device 0000b5c22393c5f0"
debug.opendns.com text =
"flags 422 0 b6 7e00400014c3"
debug.opendns.com text =
"id 19021943"
debug.opendns.com text =
"source 115.64.14.229:32770" -
It tells me that you have enabled LPC with device ID b5c22393c5f0, but you're also using the normal OpenDNS Home Basic in parallel, although maybe not willingly.
You're using the Sydney OpenDNS location, and your IP address 115.64.14.229 is registered with OpenDNS network ID 19021943. You may want to open a support ticket to get your IP address removed from OpenDNS registration, else your bypass account configuration cannot work properly.
-
Hi,
My ticket with OpenDNS Support has been replied. However, they are merely saying that my netowrk had been removed by my own action. There is nothing they need to do to deregister my network on the "normal" OpenDNS.
I am a little confused here as you seemed to be quite sure that by looking at the debug output, you could tell my network is being controlled by the "normal" OpenDNS and Netgear in parallel. The OpenDNS guy does not seem to think that is the case. May I ask you which part of the debug output tells you that my network is still being managed by the "normal" OpenDNS please?
To be sure, I have run the command again and this is the output.
1.1.168.192.in-addr.arpa
primary name server = localhost
responsible mail addr = nobody.invalid
serial = 1
refresh = 600 (10 mins)
retry = 1200 (20 mins)
expire = 604800 (7 days)
default TTL = 10800 (3 hours)
Server: UnKnown
Address: 192.168.1.1debug.opendns.com text =
"server 11.syd"
debug.opendns.com text ="device 0000b5c22393c5f0"
debug.opendns.com text ="flags 422 0 b6 7e00400014c3"
debug.opendns.com text ="id 19021943"
debug.opendns.com text ="source 115.64.14.229:32770"
Or another way to ask the question - what should the debug output look like if my network is not managed by the "normal" OpenDNS?
Thanks,
-
"id 19021943" tells me that your IP address is registered with OpenDNS network ID 19021943. The output should return "id 0" in your case of using LPC.
You may try to obtain another IP address from your ISP while switching off the ISP facing device and switching it on again after a few minutes. This action may be able to solve your problem too.
Please sign in to leave a comment.
Comments
6 comments