Big Al <alan@invalid.com> wrote:

> Xfinity tech came today, and he replaced the modem/router box and all
> was fine. When he activated it, it assigned my SSID and password so
> the net just works.
>
> I had to put a password on the login via browser 10.0.0.1 but that
> was simple. And my thermostat would not connect so I had to
> completely reset all the settings on the unit itself.
>
> But https://www.howtogeek.com is working, and others.
>
> Traceroute doesn't get any further but I'm not concerned.

Curious: How far away is a Comcast/Xfinity store? They had one 4.8
miles away from me, but all city street driving. They closed that
store, and moved to a new store 5 miles away, but nearly all easy
highway driving. I'm in the burbs. I just drive to the store to report
problems, give them the old hardware, and they give me new hardware.
They just want a reason why I suspect the old hardware. The store
counter guys are not techs, so any reason is good enough for them. You
can see their eyes glaze over as I describe all the troubleshooting that
I did.

On 2/27/24 05:24 PM, VanguardLH wrote:
> Big Al <alan@invalid.com> wrote:
>
>> Xfinity tech came today, and he replaced the modem/router box and all
>> was fine. When he activated it, it assigned my SSID and password so
>> the net just works.
>>
>> I had to put a password on the login via browser 10.0.0.1 but that
>> was simple. And my thermostat would not connect so I had to
>> completely reset all the settings on the unit itself.
>>
>> But https://www.howtogeek.com is working, and others.
>>
>> Traceroute doesn't get any further but I'm not concerned.
>
> Curious: How far away is a Comcast/Xfinity store? They had one 4.8
> miles away from me, but all city street driving. They closed that
> store, and moved to a new store 5 miles away, but nearly all easy
> highway driving. I'm in the burbs. I just drive to the store to report
> problems, give them the old hardware, and they give me new hardware.
> They just want a reason why I suspect the old hardware. The store
> counter guys are not techs, so any reason is good enough for them. You
> can see their eyes glaze over as I describe all the troubleshooting that
> I did.
Yes, I would think the eyes would roll in my case.
I'm a bit handicapped and it was only 2 days and only one website. Besides, it may not have been
the router. I would love to do the forensics on that box!!! or at least hear why.
--
Linux Mint 21.3 Cinnamon 6.0.4
Al

Big Al wrote:
> Andy Burns wrote:
>
>> Coming at it from across the Atlantic, I don't get any further than
>>    8    95 ms    96 ms    96 ms  ixp1-xe-7-0-3-0.us-ash.gia.bt.net
>> [166.49.195.143]
>>    9     *        *        *     Request timed out.
>
> So does this mean that you can't pull up https://www.howtogeek.com ?
The page loads fine for me.

VanguardLH wrote:

> Andy Burns wrote:
>
>> 7 12 ms 12 ms 13 ms 166-49-209-132.gia.bt.net [166.49.209.132]
>> 8 95 ms 96 ms 96 ms ixp1-xe-7-0-3-0.us-ash.gia.bt.net
>> [166.49.195.143]
>
> Going overseas can involve using the underwater cable which has a long
> delay.

Better than going up 22,500 miles, then back down 22,500 miles

> You will see hops that take only a dozen milliseconds, but then
> the delay jumps to way over 100 ms when going over the undersea cable.

Ye cannae change the laws of physics, Jim

> Seems you got to BT (British Telecom),
> and died somewhere inside their network.

BT owns my ISP, so essentially it stays within their network as far as
possible, I would interpret 166.49.209.132 as being the last hop within
the UK and 166.49.195.143 as being the first hop within the USA, at
which point it leaves BT's network and meets another peer, who decides
they don't like replying to traceroute packets.

On 2/28/24 03:10 AM, Andy Burns wrote:
> Big Al wrote:
>
>> Andy Burns wrote:
>>
>>> Coming at it from across the Atlantic, I don't get any further than
>>>    8    95 ms    96 ms    96 ms  ixp1-xe-7-0-3-0.us-ash.gia.bt.net [166.49.195.143]
>>>    9     *        *        *     Request timed out.
>>
>> So does this mean that you can't pull up https://www.howtogeek.com ?
>
> The page loads fine for me.
>
I does here now also. I had the router/modem replaced
--
Linux Mint 21.3 Cinnamon 6.0.4
Al

Am 28.02.24 um 14:30 schrieb Big Al:
> On 2/28/24 03:10 AM, Andy Burns wrote:
>> Big Al wrote:
>>
>>> Andy Burns wrote:
>>>
>>>> Coming at it from across the Atlantic, I don't get any further than
>>>>    8    95 ms    96 ms    96 ms  ixp1-xe-7-0-3-0.us-ash.gia.bt.net [166.49.195.143]
>>>>    9     *        *        *     Request timed out.
>>>
>>> So does this mean that you can't pull up https://www.howtogeek.com ?
>>
>> The page loads fine for me.
>>
> I does here now also. I had the router/modem replaced

With a different DNS-setting?

--
"Roma locuta, causa finita" (Augustinus)

On 2/28/24 12:43 PM, Jörg Lorenz wrote:
> Am 28.02.24 um 14:30 schrieb Big Al:
>> On 2/28/24 03:10 AM, Andy Burns wrote:
>>> Big Al wrote:
>>>
>>>> Andy Burns wrote:
>>>>
>>>>> Coming at it from across the Atlantic, I don't get any further than
>>>>>     8    95 ms    96 ms    96 ms  ixp1-xe-7-0-3-0.us-ash.gia.bt.net [166.49.195.143]
>>>>>     9     *        *        *     Request timed out.
>>>>
>>>> So does this mean that you can't pull up https://www.howtogeek.com ?
>>>
>>> The page loads fine for me.
>>>
>> I does here now also.   I had the router/modem replaced
>
> With a different DNS-setting?
>
Don't know, just put in a new unit and a quick setup to restore my SSID / password, and away I went.
The traceroute by the way still stops about 9-10 hops but the page loads now, so problem solved with
no idea why other than new modem.
--
Linux Mint 21.3 Cinnamon 6.0.4
Al

On Tue, 27 Feb 2024 16:28:16 -0500, Big Al <alan@invalid.com> wrote:

>On 2/26/24 10:33 AM, Big Al wrote:
>> For about a week I have not been able to get to https://www.howtogeek.com
>> https://www.isitdownrightnow.com/ says it's up.
>>
>> No internet device in the house can get to it.  2 laptops, and my phone.
>> However if I disconnect the wi-fi on the phone and connect via cell, then I can get the page.
>>
>> So what is common to everything?   I rebooted the router.
>>
>> Error:
>>
>>
>> Secure Connection Failed
>>
>> An error occurred during a connection to www.howtogeek.com.
>>
>>     The page you are trying to view cannot be shown because the authenticity of the received data
>> could not be verified.
>Xfinity tech came today, and he replaced the modem/router box and all was fine.
>When he activated it, it assigned my SSID and password so the net just works.
>
>I had to put a password on the login via browser 10.0.0.1 but that was simple.
>And my thermostat would not connect so I had to completely reset all the settings on the unit itself.
>
>But https://www.howtogeek.com is working, and others.
>
>Traceroute doesn't get any further but I'm not concerned.
>
>Thanks for all the input. It was a fun(?) experience, and I learned a bit from all of you!!

There was a surprisingly long excursion into DNS-land, when it should have been
obvious that it was never a DNS issue. As you may know, DNS has one job, which
is to resolve an FQDN into an IP address, and you showed us that your DNS was
resolving properly very early in the thread.

You also showed us very early on, from the first post actually, that not only
was it not DNS, but it also wasn't a routing issue, so the excursion into
traceroute was also a distraction.

Good discussion, though. Good to see it resolved.

On 3/1/24 09:12 PM, Char Jackson wrote:
> On Tue, 27 Feb 2024 16:28:16 -0500, Big Al <alan@invalid.com> wrote:
>
>> On 2/26/24 10:33 AM, Big Al wrote:
>>> For about a week I have not been able to get to https://www.howtogeek.com
>>> https://www.isitdownrightnow.com/ says it's up.
>>>
>>> No internet device in the house can get to it.  2 laptops, and my phone.
>>> However if I disconnect the wi-fi on the phone and connect via cell, then I can get the page.
>>>
>>> So what is common to everything?   I rebooted the router.
>>>
>>> Error:
>>>
>>>
>>> Secure Connection Failed
>>>
>>> An error occurred during a connection to www.howtogeek.com.
>>>
>>>     The page you are trying to view cannot be shown because the authenticity of the received data
>>> could not be verified.
>> Xfinity tech came today, and he replaced the modem/router box and all was fine.
>> When he activated it, it assigned my SSID and password so the net just works.
>>
>> I had to put a password on the login via browser 10.0.0.1 but that was simple.
>> And my thermostat would not connect so I had to completely reset all the settings on the unit itself.
>>
>> But https://www.howtogeek.com is working, and others.
>>
>> Traceroute doesn't get any further but I'm not concerned.
>>
>> Thanks for all the input. It was a fun(?) experience, and I learned a bit from all of you!!
>
> There was a surprisingly long excursion into DNS-land, when it should have been
> obvious that it was never a DNS issue. As you may know, DNS has one job, which
> is to resolve an FQDN into an IP address, and you showed us that your DNS was
> resolving properly very early in the thread.
>
> You also showed us very early on, from the first post actually, that not only
> was it not DNS, but it also wasn't a routing issue, so the excursion into
> traceroute was also a distraction.
>
> Good discussion, though. Good to see it resolved.
>
Yes, early on in my mind it was the router (modem to Xfinity), it was a new unit about a month old.
But I enjoyed all the diagnostic things suggested and I DID learn a ton of things, probably forget
80% of it though :-).

--
Linux Mint 21.3 Cinnamon 6.0.4
Al

On Fri, 1 Mar 2024 22:42:39 -0500, Big Al <alan@invalid.com> wrote:

>On 3/1/24 09:12 PM, Char Jackson wrote:
>> On Tue, 27 Feb 2024 16:28:16 -0500, Big Al <alan@invalid.com> wrote:
>>
>>> On 2/26/24 10:33 AM, Big Al wrote:
>>>> For about a week I have not been able to get to https://www.howtogeek.com
>>>> https://www.isitdownrightnow.com/ says it's up.
>>>>
>>>> No internet device in the house can get to it.  2 laptops, and my phone.
>>>> However if I disconnect the wi-fi on the phone and connect via cell, then I can get the page.
>>>>
>>>> So what is common to everything?   I rebooted the router.
>>>>
>>>> Error:
>>>>
>>>>
>>>> Secure Connection Failed
>>>>
>>>> An error occurred during a connection to www.howtogeek.com.
>>>>
>>>>     The page you are trying to view cannot be shown because the authenticity of the received data
>>>> could not be verified.
>>> Xfinity tech came today, and he replaced the modem/router box and all was fine.
>>> When he activated it, it assigned my SSID and password so the net just works.
>>>
>>> I had to put a password on the login via browser 10.0.0.1 but that was simple.
>>> And my thermostat would not connect so I had to completely reset all the settings on the unit itself.
>>>
>>> But https://www.howtogeek.com is working, and others.
>>>
>>> Traceroute doesn't get any further but I'm not concerned.
>>>
>>> Thanks for all the input. It was a fun(?) experience, and I learned a bit from all of you!!
>>
>> There was a surprisingly long excursion into DNS-land, when it should have been
>> obvious that it was never a DNS issue. As you may know, DNS has one job, which
>> is to resolve an FQDN into an IP address, and you showed us that your DNS was
>> resolving properly very early in the thread.
>>
>> You also showed us very early on, from the first post actually, that not only
>> was it not DNS, but it also wasn't a routing issue, so the excursion into
>> traceroute was also a distraction.
>>
>> Good discussion, though. Good to see it resolved.
>>
>Yes, early on in my mind it was the router (modem to Xfinity), it was a new unit about a month old.
>But I enjoyed all the diagnostic things suggested and I DID learn a ton of things, probably forget
>80% of it though :-).

It's the 80/20 rule. Very common. :)

Char Jackson <none@none.invalid> wrote:

> Big Al <alan@invalid.com> wrote:
>
>> But I enjoyed all the diagnostic things suggested and I DID learn a
>> ton of things, probably forget 80% of it though :-).
>
> It's the 80/20 rule. Very common. :)

Reminds me of the comedy skit:

5-minute University
https://www.youtube.com/watch?v=c00GPvns31U

On 02.03.24 23:02, Char Jackson wrote:
> On Fri, 1 Mar 2024 22:42:39 -0500, Big Al <alan@invalid.com> wrote:
>> Yes, early on in my mind it was the router (modem to Xfinity), it was a new unit about a month old.
>> But I enjoyed all the diagnostic things suggested and I DID learn a ton of things, probably forget
>> 80% of it though :-).
>
> It's the 80/20 rule. Very common. :)

The keyword is "Half-Life".

--
"Manus manum lavat."

On 3/3/24 12:16, Joerg Lorenz wrote:
> On 02.03.24 23:02, Char Jackson wrote:
>> On Fri, 1 Mar 2024 22:42:39 -0500, Big Al <alan@invalid.com> wrote:
>>> Yes, early on in my mind it was the router (modem to Xfinity), it was a new unit about a month old.
>>> But I enjoyed all the diagnostic things suggested and I DID learn a ton of things, probably forget
>>> 80% of it though :-).
>>
>> It's the 80/20 rule. Very common. :)
>
> The keyword is "Half-Life".

where two halves DON'T make a whole.

In article <3hpFN.519730$xHn7.256258@fx14.iad>,
Sam E <not.email@all.invalid> wrote:
> On 3/3/24 12:16, Joerg Lorenz wrote:
> > On 02.03.24 23:02, Char Jackson wrote:
> >> On Fri, 1 Mar 2024 22:42:39 -0500, Big Al <alan@invalid.com> wrote:
> >>> Yes, early on in my mind it was the router (modem to Xfinity), it
> >>> was a new unit about a month old. But I enjoyed all the diagnostic
> >>> things suggested and I DID learn a ton of things, probably forget
> >>> 80% of it though :-).
> >>
> >> It's the 80/20 rule. Very common. :)
> >
> > The keyword is "Half-Life".

> where two halves DON'T make a whole.

Funny old world innit!

If you brought two suitable sized halves of Plutonium together with enough
force, you'd make a very large hole. ;-)

D.

On 04.03.24 20:27, Sam E wrote:
> On 3/3/24 12:16, Joerg Lorenz wrote:
>> On 02.03.24 23:02, Char Jackson wrote:
>>> On Fri, 1 Mar 2024 22:42:39 -0500, Big Al <alan@invalid.com> wrote:
>>>> Yes, early on in my mind it was the router (modem to Xfinity), it was a new unit about a month old.
>>>> But I enjoyed all the diagnostic things suggested and I DID learn a ton of things, probably forget
>>>> 80% of it though :-).
>>>
>>> It's the 80/20 rule. Very common. :)
>>
>> The keyword is "Half-Life".
>
> where two halves DON'T make a whole.

That is the mathematical concept indeed.
And the best is: There are more than two halfs and it is still not a whole.

--
"Ave Caesar! Morituri te salutant!"