Connected to Internet but all browsers say I'm offline

#21

That's why I ping using an IP addresses. When using a domain name it has to do a DNS lookup first.
Did ping fail to lookup the hostname www.google.com, or did it look it up and return an IP address and then fail to ping it? If it returned an IP address for www.google.com, try pinging the IP address.

After you remove WARP, change the xFi gateway and your router, I would reboot the router and then your Channels DVR server, then see how it behaves. Things are probably cached and the reboots will clear them.

#22

When I pinged www.google.com one time I don't remember the response but it wasn't a reply from their servers. Just now when I did it the replies were from 142.250.217.100 with round trip times between 28ms and 61ms. And this was while getting a bunch of "no such host" responses in the Channels troubleshooter.

This one doesn't seem to want to be pinned down...

#23

What are you running your Channels DVR server on?

#24

It's an old (2009-ish) HP Z400 with a Xeon CPU that I put a 256 GB SSD drive and a couple of 10 TB storage drives in.

#25

Windows, Linux, ...

#26

Oh sorry - Windows 10 Pro

#27

Once you remove WARP from it and reboot, make sure WARP didn't leave behind any network drivers.

#28

Will do.
BTW - when I took over the router setting from my son when he moved away, I cleared out all the Port Forwarding as well and only added in two ports for Channels, 80 for HTTP, and a port for RDP. Do you think there might be any critical omissions I should've added as well?

#29

Not sure what you're trying to say about two ports for Channels?
I don't open any ports to the Internet. I use Tailscale instead.
Channels uses port 8089 by default, unless you change it.
If you're using Channels remote access you have to port forward 8089 on your router to the Channels DVR server and port forward 8089 on the xFi Gateway (think that can only be done using the Xfinity app) to your router.

#30

Please try ping 8.8.8.8 which is google's dns. 1.1.1.1 is a special IP that is only supposed to be routed locally and used for testing. Some organizations properly block 1.1.1.1 from exiting there network. Shame on Cloudflare for using it for there DNS.

#31

Documentation?
You might want to let IANA know about it. IANA IPv4 Special-Purpose Address Registry
You do know who IANA is, right?

#32

In early Cisco Router classes, this is what was recommended. Cloudflare admits that there have been and still are issues reaching 1.1.1.1 from some locations:

#33

Yah, so a few bad actors were doing things incorrectly. If you can't reach 1.1.1.1, then use 1.0.0.1
1.1.1.1 is registered, routable and should be globally reachable. Same with 1.0.0.1

I would like to know where you found this

#34

Earlier today I was pinging 8.8.8.8 as well as 1.1.1.1 with no discernable difference. I know a lot of IT professionals who use and even recommend Cloudflare for their DNS and I haven't heard of that being a problematic thing. Interestingly,

Prior to the last 2-1/2 years I was using pfSense on an old PC running Linux as our router with our current router being used solely as a wireless access point, and I don't remember ever seeing the kinds of errors I'm citing here. In fact, I was using Google's DNS (8.8.8.8) during the first 18 months and only switched over to Cloudflare due to the recommendations of others. When I did that these issues decreased significantly.

I'm definitely seeing a lot of errors that I've attributed to being DNS errors, but that's more of a guess due to symptoms than actual confirmation and there seems to be behavior that's inconsistent with that .

#35

If you have any ad blockers or safe dns stuff running on your router, whitelist the dvr server or disable them.

Also up to you, but I don't run firewalls on my NAS's or my router since they're behind the NAT of my xFi Gateway and not exposed directly to the Internet.

#36

Now that I'm home I've confirmed that the new modem is an Xfinity XB8-T.

#37

Should be pretty much the same admin UI interface, just has WiFi 6.

#38

I don't think I'm using any of those other than the built-in firewalls of Windows. When I moved from pfSense to the Netgear Nighthawk I did a factory reset on it and updated the firmware. Then I just added the bare minimum such as the SSIDs and passwords and port forwards. The second port for Channels was for a second instance of it that I had thought of setting up for another user.

#39

Is this only for if I'm not in bridge mode?

(I obviously can't figure out how to use quotes on this style forum, lol)

#40

Yes. If you're not in bridge mode you have to port forward the Xfi Gateway to your router and port forward your router to the channels server.

If you are in bridge mode then you just need to port forward your router to the channels server.

Getting to the Xfi Gateway port forward settings is a pain if you don't know where they are.
In the Xfinity app select WiFi
Select View WiFi equipment
Select Advanced Settings
Select Port forwarding

1 Like