(sent from Thunderbird running in windows-7)
From Fedora-35, I cannot reach the internet at all.
- Firefox and Thunderbird each take several minutes trying before notifying me of time-out.
- If, as root, I do "dnf info firefox", it takes several minutes trying before giving me curl errors. So here too, apparently no internet access.
- In the corner of the display (gnome), there's usually a little fork-like symbol next to the little symbol that I click to log off or shutdown. That symbol is not showing.
- Firefox is able to communicate with the modem. I did not see anything in the modem's display in Firefox that looked like a problem.
- An rkhunter scan shows no problems, but I realize that doesn't check everything.
- Last night, I was in a 3-way zoom meeting on this work station (using Fedora-35 and Firefox) for almost 2 hours as a participant (not host). Immediately after that meeting ended, I shut down for the night. I noticed in the past that after a zoom meeting, some things do seem to be messed up in Fedora; I don't recall any details. I've been simply rebooting to solve that. Zoom does seem somehow "dirty".
- This is a dual-boot workstation. When booted up in windows-7 (like now), I am able to connect to some sites in Firefox, but not all. Some that I can connect to are unusually slow. Thunderbird also works, but is unusually slow.
The modem is an Arris T25 SURFboard, DOCSIS 3.1 for xfinity internet and voice. I originally thought the problem was the modem, but since it seems to be working when I boot into windows-7, I now think the problem is more likely to be in Fedora.
I have no formal training or experience in sys.admin.
H-E-E-E-L-P ! ! !
On 6/11/22 11:42, home user wrote:
- In the corner of the display (gnome), there's usually a little
fork-like symbol next to the little symbol that I click to log off or shutdown. That symbol is not showing.
I assume you're referring to the wired network symbol. If you go into the setting, what do you see in the network section?
- Firefox is able to communicate with the modem. I did not see anything
in the modem's display in Firefox that looked like a problem.
Then your local network is working fine.
- Last night, I was in a 3-way zoom meeting on this work station (using
Fedora-35 and Firefox) for almost 2 hours as a participant (not host). Immediately after that meeting ended, I shut down for the night. I noticed in the past that after a zoom meeting, some things do seem to be messed up in Fedora; I don't recall any details. I've been simply rebooting to solve that. Zoom does seem somehow "dirty".
That is rather odd. Zoom shouldn't be able to mess up anything system-wide.
- This is a dual-boot workstation. When booted up in windows-7 (like
now), I am able to connect to some sites in Firefox, but not all. Some that I can connect to are unusually slow. Thunderbird also works, but is unusually slow.
That doesn't sound like it's working properly.
The modem is an Arris T25 SURFboard, DOCSIS 3.1 for xfinity internet and voice. I originally thought the problem was the modem, but since it seems to be working when I boot into windows-7, I now think the problem is more likely to be in Fedora.
It doesn't really sound like it's working properly in Windows, so it's not just Fedora, but it's probably easier to debug the issue in Fedora.
What happens if you do the following commands: "ping 8.8.8.8" "host google.com" or "dig google.com" "ping google.com" "traceroute 8.8.8.8"
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and behaves normally.
When I started this thread, being able to connect to websites in windows-7 but not being able to connect to the same URLs in Fedora had me suspecting trouble in Fedora. But being able to connect to only some web sites in windows-7 had me thinking there was also trouble "out there" (beyond the scope of what I'm responsible for). It now seems the trouble was all "out there".
A question on my mind is why was I able to connect to google.com forecast.weather.gov wikipedia.org in windows-7 but not Fedora-35?
I suppose what you requested (below) is no longer needed, but in case I'm wrong, here goes...
On 6/11/22 11:42, home user wrote:
- In the corner of the display (gnome), there's usually a little
fork-like symbol next to the little symbol that I click to log off or shutdown. That symbol is not showing. >
I assume you're referring to the wired network symbol. If you go into the setting, what do you see in the network section?
I see now that my description of the symbol was incorrect. My apologies.
I now see: IPv4 Address 98.43.14.86 IPv6 ess fe80::3285:a9ff:fe97:537e Hardware Address 30:85:A9:97:53:7E Default Route: 98:43:12:1 fe80::dead:beef:2:1 DNS 75.75.75.75 75.75.76.76
- Firefox is able to communicate with the modem. I did not see
anything in the modem's display in Firefox that looked like a problem.
Then your local network is working fine.
- Last night, I was in a 3-way zoom meeting on this work station
(using Fedora-35 and Firefox) for almost 2 hours as a participant (not host). Immediately after that meeting ended, I shut down for the night. I noticed in the past that after a zoom meeting, some things do seem to be messed up in Fedora; I don't recall any details. I've been simply rebooting to solve that. Zoom does seem somehow "dirty".
That is rather odd. Zoom shouldn't be able to mess up anything system-wide.
"shouldn't". But it does, though probably not intentionally.
- This is a dual-boot workstation. When booted up in windows-7 (like
now), I am able to connect to some sites in Firefox, but not all. Some that I can connect to are unusually slow. Thunderbird also works, but is unusually slow.
That doesn't sound like it's working properly.
The modem is an Arris T25 SURFboard, DOCSIS 3.1 for xfinity internet and voice. I originally thought the problem was the modem, but since it seems to be working when I boot into windows-7, I now think the problem is more likely to be in Fedora.
It doesn't really sound like it's working properly in Windows, so it's not just Fedora, but it's probably easier to debug the issue in Fedora.
What happens if you do the following commands: "ping 8.8.8.8" "host google.com" or "dig google.com" "ping google.com" "traceroute 8.8.8.8"
bash.3[~]: ping -c 5 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=12.1 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=11.3 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=10.1 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=12.6 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=9.35 ms
--- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 9.345/11.083/12.616/1.216 ms bash.4[~]: host google.com google.com has address 142.250.72.14 google.com has IPv6 address 2607:f8b0:400f:807::200e google.com mail is handled by 10 smtp.google.com. bash.5[~]: dig google.com
; <<>> DiG 9.16.29-RH <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6920 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;google.com. IN A
;; ANSWER SECTION: google.com. 80 IN A 142.250.72.14
;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Jun 11 16:14:51 MDT 2022 ;; MSG SIZE rcvd: 55
bash.6[~]: ping -c 5 google.com PING google.com (142.250.72.14) 56(84) bytes of data. 64 bytes from den08s06-in-f14.1e100.net (142.250.72.14): icmp_seq=1 ttl=115 time=10.1 ms 64 bytes from den08s06-in-f14.1e100.net (142.250.72.14): icmp_seq=2 ttl=115 time=9.84 ms 64 bytes from den08s06-in-f14.1e100.net (142.250.72.14): icmp_seq=3 ttl=115 time=20.1 ms 64 bytes from den08s06-in-f14.1e100.net (142.250.72.14): icmp_seq=4 ttl=115 time=9.48 ms 64 bytes from den08s06-in-f14.1e100.net (142.250.72.14): icmp_seq=5 ttl=115 time=10.8 ms
--- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 9.483/12.071/20.113/4.043 ms bash.7[~]: traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 10.144.233.194 (10.144.233.194) 44.145 ms 44.154 ms 10.144.233.195 (10.144.233.195) 17.340 ms 2 96.110.246.153 (96.110.246.153) 14.270 ms 96.110.246.149 (96.110.246.149) 14.193 ms 15.727 ms 3 162.151.50.121 (162.151.50.121) 14.006 ms 96.108.139.141 (96.108.139.141) 15.793 ms 15.834 ms 4 96.216.22.45 (96.216.22.45) 19.315 ms 162.151.50.121 (162.151.50.121) 15.664 ms 13.944 ms 5 96.216.22.45 (96.216.22.45) 19.327 ms 19.124 ms 19.194 ms 6 be-3302-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.122) 16.994 ms be-3102-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.114) 10.842 ms be-36011-cs01.1601milehigh.co.ibone.comcast.net (96.110.43.241) 17.516 ms 7 23.30.207.162 (23.30.207.162) 17.409 ms 23.30.206.218 (23.30.206.218) 18.842 ms be-3202-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.118) 14.203 ms 8 23.30.206.218 (23.30.206.218) 15.855 ms * 108.170.252.193 (108.170.252.193) 13.991 ms 9 108.170.254.65 (108.170.254.65) 12.752 ms * dns.google (8.8.8.8) 18.129 ms bash.8[~]:
Thank-you, Samuel. Bill.
On 6/11/22 16:26, home user wrote:
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and behaves normally.
When I started this thread, being able to connect to websites in windows-7 but not being able to connect to the same URLs in Fedora had me suspecting trouble in Fedora. But being able to connect to only some web sites in windows-7 had me thinking there was also trouble "out there" (beyond the scope of what I'm responsible for). It now seems the trouble was all "out there".
A question on my mind is why was I able to connect to google.com forecast.weather.gov wikipedia.org in windows-7 but not Fedora-35?
That's hard to say. Maybe it was starting to get fixed by the time you switched. Did you switch back and forth or only switch to Windows once? A DNS issue could cause the symptoms you saw. But without the diagnostic tests being run during the problem time, there's no way to tell for sure.
I suppose what you requested (below) is no longer needed, but in case I'm wrong, here goes...
Yes, it's not useful now that everything's working.
On 6/11/22 5:40 PM, Samuel Sieb wrote:
On 6/11/22 16:26, home user wrote:
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and behaves normally.
When I started this thread, being able to connect to websites in windows-7 but not being able to connect to the same URLs in Fedora had me suspecting trouble in Fedora. But being able to connect to only some web sites in windows-7 had me thinking there was also trouble "out there" (beyond the scope of what I'm responsible for). It now seems the trouble was all "out there".
A question on my mind is why was I able to connect to google.com forecast.weather.gov wikipedia.org in windows-7 but not Fedora-35?
That's hard to say. Maybe it was starting to get fixed by the time you switched. Did you switch back and forth or only switch to Windows once?
Multiple times over 4-5 hours I - powered down and powered up the modem; - reset the modem; - disconnected and reconnected the yellow ethernet cable; and - rebooted the work station, trying both OSs. So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
A DNS issue could cause the symptoms you saw. But without the diagnostic tests being run during the problem time, there's no way to tell for sure.
Another question... It took multiple minutes for dnf, Firefox, and Thunderbird to decide to give up on connecting. What is a reasonable time that should be allowed, and how do I permanently customize those for that time?
home user writes:
Another question... It took multiple minutes for dnf, Firefox, and Thunderbird to decide to give up on connecting. What is a reasonable time that should be allowed, and how do I permanently customize those for that time?
Connection timeouts are determined by some combination of kernel and application-specific logic. It also depends on the nature of the timeout, whether it's a DNS lookup timing out, or an actual socket connection attempt timeout. Sometimes they are configurable, but not usually.
On 6/11/22 19:50, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
If it didn't work the first time, why did you think that doing the same thing again would work?
On 6/11/22 8:56 PM, Joe Zeff wrote:
On 6/11/22 19:50, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
If it didn't work the first time, why did you think that doing the same thing again would work?
A few days before, I had similar problems. I called the ISP's customer service for help. After trying a few things, the problem was fixed. I don't know whether it was something the rep had me do or something she did. This morning, I was trying different combinations of things in different sequences, somewhat based on the experience of a few days ago.
On Sat, 2022-06-11 at 19:50 -0600, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
Sounds like your ISP had problems. Do they have a status page? If so, have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).
On Sun, Jun 12, 2022 at 12:21 AM Tim via users < users@lists.fedoraproject.org> wrote:
On Sat, 2022-06-11 at 19:50 -0600, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
Sounds like your ISP had problems. Do they have a status page? If so, have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).
Randomly rebooting without gathering data is time consuming and not very informative.
Many ISP's provide a support site that offers a speed test and in some cases even include information about current status of their service. A speed test can tell you if the problems you see are local or in your ISP's access to the wider internet. There are also sites like downdector that collect problem reports and provide graphs of the numbers of reports over time. Those peaks often coincide with times when I encountered problems, so can help to confirm that a problem wasn't something on my end.
During periods of high demand (Superbowl, public hearings by US Congress) the internet may fall back to less optimal routing. Your zoom issues could be due to "rate limiting" by your ISP, generally imposed during periods where customer aggregate demand exceeds capacity.
You appear to be using a wired connection, but if you have wifi you should check that only "known to you" devices are connecting. Your router should list connected devices by their MAC address, so you may want to collect the MAC addresses of "known to you" devices and turn off MAC address randomizaton for portable devices when connected to your home wifi.
On 6/11/22 9:21 PM, Tim via users wrote:
On Sat, 2022-06-11 at 19:50 -0600, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were other URLs that worked in windows-7 but not Fedora-35, but I think 3 URLs were enough of a sample for this thread.
Sounds like your ISP had problems. Do they have a status page? If so, have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).
My ISP is comcast (or xfinity). I found a status page. I did not see anything about past outages. How do I find the IP for that status page?
On 6/12/22 4:25 AM, George N. White III wrote:
On Sun, Jun 12, 2022 at 12:21 AM Tim via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On Sat, 2022-06-11 at 19:50 -0600, home user wrote: > Multiple times over 4-5 hours I > - powered down and powered up the modem; > - reset the modem; > - disconnected and reconnected the yellow ethernet cable; and > - rebooted the work station, trying both OSs. > So I switched back and forth multiple times. There also were other > URLs > that worked in windows-7 but not Fedora-35, but I think 3 URLs were > enough of a sample for this thread. Sounds like your ISP had problems. Do they have a status page? If so, have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).Randomly rebooting without gathering data is time consuming and not very informative.
It was not random. The rebooting was done to: * compare windows-7 and Fedora-35 in hopes of determining whether the problem was in Fedora-35, the modem, or "out there". * see if something done to the modem helped. I did what I knew to do, though I recognize that my knowledge on these things is poor.
Many ISP's provide a support site that offers a speed test and in some cases even include information about current status of their service. A speed test can tell you if the problems you see are local or in your ISP's access to the wider internet. There are also sites like downdector that collect problem reports and provide graphs of the numbers of reports over time. Those peaks often coincide with times when I encountered problems, so can help to confirm that a problem wasn't something on my end.
The only speed test I've ever seen seemed very "snoopy" and intrusive the last time I accessed it. That was some time ago, I don't recall when. I do recall Firefox and/or NoScript not liking the site. I've never seen any hint of a speed test being offered by my ISP (comcast/xfinity), though I log into that company's site at least once per month. Status site for comcast: see my reply to Tim. What if I can't access comcast's/xfinity's site?
I could not access downdetector Saturday morning.
During periods of high demand (Superbowl, public hearings by US Congress) the internet may fall back to less optimal routing. Your zoom issues could be due to "rate limiting" by your ISP, generally imposed during periods where customer aggregate demand exceeds capacity.
My zoom issues occur after the zoom meeting is done and I've left (disconnected from) the zoom site in Firefox, not during the meeting. I have not tried any diagnosis.
You appear to be using a wired connection, but if you have wifi you should check that only "known to you" devices are connecting. Your router should list connected devices by their MAC address, so you may want to collect the MAC addresses of "known to you" devices and turn off MAC address randomizaton for portable devices when connected to your home wifi.
I'm using a wired connection only. No wifi. No router.
Tim:
Sounds like your ISP had problems. Do they have a status page? If so, have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).
home user:
My ISP is comcast (or xfinity). I found a status page. I did not see anything about past outages.
Some don't update their pages, they never have faults (pah!). One of our ISPs tried that line with me, I argued that's why you don't have any technicians... Their user forums were full of complaints about service failures.
How do I find the IP for that status page?
Let's say, for example, that your ISP has a status page at:
http://www.example.com/status.html
You could do
dig www.example.com
To find it's IP
Then, you could try:
http://93.184.216.34/status.html
With a big ISP, that may work. Other ISPs may actually need a hostname to go with the HTTP request. In that case, you'd have to TEMPORARILY add the IP to your /etc/hosts file, and use the address with the hostname written in it (like my first example).
e.g.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 98.184.216.34 www.example.com
I say do that temporarily, because their IP may change. ISPs fiddle with things as much as some users do. And with a big ISP, you might connect to different machines when you disconnect and reconnect with a sufficient time delay.
Regarding speed tests, you can google for broadband speed tests, there's plenty. But beware that some ISPs fudge things. They'll optimise their configuration so that speed tests go through with flying speeds, but the rest of their network is throttled. Mine does that.
There are some speed test sites that aren't all fancy graphics with speedometer dials, you just download a huge file and time it. Those ones that fly under the radar a bit more don't get the tricked results by the ISPs.
I look for overseas speed test sites to test my real speed, most of our Australian servers are reasonably fast, but our overseas links can be dire. And a lot of things I want to use, and occasionally have trouble with, are overseas.
I'll probably be going through this pain, soon, changing ISPs. Mine has decided to change my plan without my approval, halving the speed, and jacking up the price by around a third.
On Mon, Jun 13, 2022 at 12:34 AM home user mattisonw@comcast.net wrote:
On 6/12/22 4:25 AM, George N. White III wrote:
On Sun, Jun 12, 2022 at 12:21 AM Tim via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On Sat, 2022-06-11 at 19:50 -0600, home user wrote: > Multiple times over 4-5 hours I > - powered down and powered up the modem; > - reset the modem; > - disconnected and reconnected the yellow ethernet cable; and > - rebooted the work station, trying both OSs. > So I switched back and forth multiple times. There also wereother
> URLs > that worked in windows-7 but not Fedora-35, but I think 3 URLswere
> enough of a sample for this thread. Sounds like your ISP had problems. Do they have a status page? Ifso,
have a look, see if it lists past outages, bookmark it for next time (also find its IP, now, so you can check if DNS doesn't work in the future).Randomly rebooting without gathering data is time consuming and not very informative.
It was not random. The rebooting was done to:
- compare windows-7 and Fedora-35 in hopes of determining whether the
problem was in Fedora-35, the modem, or "out there".
- see if something done to the modem helped.
I did what I knew to do, though I recognize that my knowledge on these things is poor.
You will find it well worth the effort to learn some basics of network troubleshooting: A beginner's guide to network troubleshooting in Linux | Enable Sysadmin (redhat.com) https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linux
Many ISP's provide a support site that offers a speed test and in some cases even include information about current status of their service. A speed test can tell you if the problems you see are local or in your ISP's access to the wider internet. There are also sites like downdector that collect problem reports and provide graphs of the numbers of reports over time. Those peaks often coincide with times when I encountered problems, so can help to confirm that a problem wasn't something on my end.
The only speed test I've ever seen seemed very "snoopy" and intrusive the last time I accessed it. That was some time ago, I don't recall when. I do recall Firefox and/or NoScript not liking the site. I've never seen any hint of a speed test being offered by my ISP (comcast/xfinity), though I log into that company's site at least once per month. Status site for comcast: see my reply to Tim. What if I can't access comcast's/xfinity's site?
If you can't connect to your ISP's site you should call their support line and be prepared to wait in a queue with all the others having problems (I connect my phone to the charge and put in speaker mode so i can do other stuff while I wait).
"Speed tests" are a popular way bad actors get victims to sites that try to extract money. Using your ISP's test should be as safe as anything from your ISP. ShieldsUP! https://www.grc.com/ is a reputable site that you can use to scan your system for internet accessible ports.
I could not access downdetector Saturday morning.
That is what I see when I'm having problems, but once service is restored I can usually see the spike in reports around the time I had a problem, which means I don't pester admins at the remote site I couldn't reach.
During periods of high demand (Superbowl, public hearings by US Congress) the internet may fall back to less optimal routing. Your zoom issues could be due to "rate limiting" by your ISP, generally imposed during periods
where
customer aggregate demand exceeds capacity.
My zoom issues occur after the zoom meeting is done and I've left (disconnected from) the zoom site in Firefox, not during the meeting. I have not tried any diagnosis.
Compare "ss -tl" results before, during, and after a zoom session.
You appear to be using a wired connection, but if you have wifi you
should
check that only "known to you" devices are connecting. Your router
should
list connected devices by their MAC address, so you may want to collect
the
MAC addresses of "known to you" devices and turn off MAC address randomizaton for portable devices when connected to your home wifi.
I'm using a wired connection only. No wifi. No router.
Are you running internet facing services (web page, ssh, etc.)? To list active tcp connections and listening ports, use "ss -tl". "ShieldsUp!!": https://www.grc.com/ is a reputable site that will tell you which ports are open to the internet.
On 6/13/22 4:30 AM, George N. White III wrote:
You will find it well worth the effort to learn some basics of network troubleshooting: A beginner's guide to network troubleshooting in Linux | Enable Sysadmin (redhat.com) https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linux
I gave it a first pass. For me, it seemed to be overkill; much was over my head. But I'll give it a second-pass reading later.
The only speed test I've ever seen seemed very "snoopy" and intrusive the last time I accessed it. That was some time ago, I don't recall when. I do recall Firefox and/or NoScript not liking the site. I've never seen any hint of a speed test being offered by my ISP (comcast/xfinity), though I log into that company's site at least once per month. Status site for comcast: see my reply to Tim. What if I can't access comcast's/xfinity's site?
"Speed tests" are a popular way bad actors get victims to sites that try to extract money. Using your ISP's test should be as safe as anything from your ISP. ShieldsUP! https://www.grc.com/ https://www.grc.com/ is a reputable site that you can use to scan your system for internet accessible ports.
Tried that this morning, from Firefox running in Fedora. It seemed to think it was a windows box that I was testing. Otherwise, the tests seemed to work, and claimed my workstation was clean.
I could not access downdetector Saturday morning.That is what I see when I'm having problems, but once service is restored I can usually see the spike in reports around the time I had a problem, which means I don't pester admins at the remote site I couldn't reach.
I looked at that this morning to see if it would report on comcast/xfinity. It did. Would have been nice if it had given me a way of seeing back to Saturday morning, but I did not see any such functionality.
Compare "ss -tl" results before, during, and after a zoom session.
I'll try to remember to try that.
I'm using a wired connection only. No wifi. No router.Are you running internet facing services (web page, ssh, etc.)? To list active tcp connections and listening ports, use "ss -tl". "ShieldsUp!!": https://www.grc.com/ https://www.grc.com/ is a
reputable site that will tell you which ports are open to the internet.
This is a "simple" home workstation: tower connected via 1 yellow ethernet cable to one internet&voice modem. The phone is a land line. I'm not running any internet-facing services that I know of. GRC says I have no ports open to the internet, but it also seems to think this is a windows box. (It is a Fedora and windows-7 dual boot system, but I was using Fedora for the GRC tests.)
Thank-you, George.
On Mon, Jun 13, 2022 at 4:45 PM home user mattisonw@comcast.net wrote:
On 6/13/22 4:30 AM, George N. White III wrote:
You will find it well worth the effort to learn some basics of network troubleshooting: A beginner's guide to network troubleshooting in Linux | Enable Sysadmin (redhat.com) <
https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linu...
I gave it a first pass. For me, it seemed to be overkill; much was over my head. But I'll give it a second-pass reading later.
The only speed test I've ever seen seemed very "snoopy" and intrusive the last time I accessed it. That was some time ago, I don't recall when. I do recall Firefox and/or NoScript not liking the site. I've never seen any hint of a speed test being offered by my ISP (comcast/xfinity), though I log into that company's site at leastonce
per month. Status site for comcast: see my reply to Tim. What if I can't access comcast's/xfinity's site?"Speed tests" are a popular way bad actors get victims to sites that try to extract money. Using your ISP's test should be as safe as anything from your ISP. ShieldsUP! https://www.grc.com/ https://www.grc.com/ is a reputable site that you can use to scan your system for internet accessible ports.
Tried that this morning, from Firefox running in Fedora. It seemed to think it was a windows box that I was testing. Otherwise, the tests seemed to work, and claimed my workstation was clean.
I could not access downdetector Saturday morning.
The graph is for the past 24 hours. I usually see problems from coffee break to coffee break and evening peak times, so if I had problems I check early the next morning.
That is what I see when I'm having problems, but once service is restored I can usually see the spike in reports around the time I had a problem, which means I don't pester admins at the remote site I couldn't reach.
I looked at that this morning to see if it would report on comcast/xfinity. It did. Would have been nice if it had given me a way of seeing back to Saturday morning, but I did not see any such functionality.
Compare "ss -tl" results before, during, and after a zoom session.
I'll try to remember to try that.
I'm using a wired connection only. No wifi. No router.Are you running internet facing services (web page, ssh, etc.)? To list active tcp connections and listening ports, use "ss -tl". "ShieldsUp!!": https://www.grc.com/ https://www.grc.com/ is a
reputable site that will tell you which ports are open to the internet.
This is a "simple" home workstation: tower connected via 1 yellow ethernet cable to one internet&voice modem. The phone is a land line. I'm not running any internet-facing services that I know of. GRC says I have no ports open to the internet, but it also seems to think this is a windows box. (It is a Fedora and windows-7 dual boot system, but I was using Fedora for the GRC tests.)
I don't think GRC cares about your OS -- it can check for "most common" ports or all ports. Some ports were first used for Microsoft protocols, but Linux often provides versions of Windows services.
-
George N. White III -
home user -
Joe Zeff -
Sam Varshavchik -
Samuel Sieb -
Tim