TP-Link CR1200

February 19, 2018 23:47

Hey everyone,

I use an ethernet cable to connect my TP-Link Router to my xfinity-supplied wireless router. This router is set up as a wireless router, but only a handful devices are connected through it. I instead set up the TP-Link Archer CR1200 router for general use. I give the SSID and pw info to my kids and guests and use that connection myself.

I double-checked that I have the right IP address and other settings are correct. However, when I browse to "welcome.opendns.com" the sites tells me I am NOT connected. I double-checked that my device is connected to the right wireless network (NOT the xfinity one) but still not luck. What am I doing wrong?

Comments

8 comments

christiaan February 19, 2018 23:48

And by "CR1200" I mean AC1200. My apologies!!

0

Comment actions Permalink
rotblitz February 20, 2018 07:56

It looks like you configured the OpenDNS resolver addresses at the wrong place. Where did you configure them? Can you post one or more screen shots here?

0

Comment actions Permalink
christiaan February 20, 2018 15:24

Here are a few screen shots. I hope they are what you need.

0

Comment actions Permalink
christiaan February 20, 2018 15:24

0

Comment actions Permalink
christiaan February 20, 2018 15:24

0

Comment actions Permalink
rotblitz February 20, 2018 15:39
Yes, these screen shots are useful to a certain extent. In case you only have IPv4 connectivity (and not IPv6 connectivity), I would expect that OpenDNS should be working for you. But I need to see more information.

Copy & paste the complete plain text output of the following diagnostic commands to here, from a computer connected to the TP-Link router:
```
nslookup -type=txt debug.opendns.com. 208.67.220.220
nslookup -type=txt which.opendns.com.
nslookup whoami.akamai.net.
netsh interface ipv4 show config
```
Ideally the xfinity device should be in bridged mode, but from your screen shots it is in NAT mode. Can you change this? If not, can you configure DNS servers on the xfinity device too?
0

Comment actions Permalink
christiaan March 26, 2018 18:29

I'll run this script in a minute.

My question is: why does it matter how my router gets it's packets (through an xfinity modem in bridge mode or NAT mode?) I don't know enough about how this works, so I'd love to learn.

0

Comment actions Permalink
christiaan March 26, 2018 18:53

Ok, Rotblitz, this is what I get back:

nslookup -type=txt debug.opendns.com. 208.67.220.220

Server:208.67.220.220

Address:208.67.220.220#53

** server can't find debug.opendns.com: NXDOMAIN

Kristinas-MacBook-Pro:~ kvheuvel$ nslookup -type=txt which.opendns.com.

Server:208.67.220.220

Address:208.67.220.220#53

Non-authoritative answer:

which.opendns.comtext = "I am not an OpenDNS resolver."

Authoritative answers can be found from:

Kristinas-MacBook-Pro:~ kvheuvel$ nslookup whoami.akamai.net.

Server:208.67.222.222

Address:208.67.222.222#53

Non-authoritative answer:

Name:whoami.akamai.net

Address: 76.96.15.67

Kristinas-MacBook-Pro:~ kvheuvel$ netsh interface ipv4 show config

-bash: netsh: command not found

Kristinas-MacBook-Pro:~ kvheuvel$ nslookup -type=txt debug.opendns.com. 208.67.220.220

Server:208.67.220.220

Address:208.67.220.220#53

** server can't find debug.opendns.com: NXDOMAIN

Kristinas-MacBook-Pro:~ kvheuvel$ nslookup -type=txt which.opendns.com.

Server:208.67.222.222

Address:208.67.222.222#53

Non-authoritative answer:

which.opendns.comtext = "I am not an OpenDNS resolver."

Authoritative answers can be found from:

Kristinas-MacBook-Pro:~ kvheuvel$ nslookup whoami.akamai.net.

Server:208.67.222.222

Address:208.67.222.222#53

Non-authoritative answer:

Name:whoami.akamai.net

Address: 76.96.15.67

Kristinas-MacBook-Pro:~ kvheuvel$ netsh interface ipv4 show config

0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?