Hi Michael,
I used to have a supervisor named Michael in my Guard unit where we maintained a TSC-60.
Check out https://w7tsc.org
Thank you for the recap. ?I¡¯ll try to unpack this best I can, no guarantee of clues,
Using a browser -on- the HamClock Pi works, assuming you¡¯ve tried many sites not otherwise configured in a hosts file. ?That should mean IP, gateway IP, and DNS are working. ?General network connectivity seems okay. ?It¡¯s passing port 80 and probably port 443 just fine.
Ping and ssh are different animals, and they use different methods. ?SSH uses port 22, while ping uses ICMP on any port.
To see if Ping is enabled/disabled, use
cat /proc/sys/net/ipv4/icmp_echo_ignore_all
0 = enabled
1 = disabled?
Ping can be blocked either at the Pi or at the router. ?SSH uses a conf file for the server -and- authentication keys. ?If you had an invalid key, I believe you would get a message about that when you try to connect.
To me, this leaves a few potential culprits.
- The router, somehow configured to not let that Pi¡¯s IP address route Ping or ssh requests but ok with browser. ?I don¡¯t know your router so don¡¯t know how it can be set up. ?This would also prevent other computers on the network from pinging the PI. ?I assume you are pinging using IP address and not a host name.
- Sshd config file has a bad setting not allowing incoming connections from other IP addresses. ?This would still allow ssh to self as you¡¯ve described. ?But if other computers get a destination host unreachable, I don¡¯t think it¡¯s in the conf file. ?It goes back to a network problem.
- Ports allowed:disallowed on the Pi. ?It was working six months ago but not now. ?Do you have automatic updates enabled on that Pi? ?I¡¯ve seen updates do funny things like close ports I once had open, or replace a driver and end up breaking functionality. ?I recently had an update on something (many months back) and it turned off ping. ?Took me hours to figure out. ?This is reaching for straws but it must be eliminated as a possibility.
Past that, if it were my system, here is what I would do.
- Grab a different router NOT on the network. ?Essentially create a standalone network with a spare router. ?Plug in the HamClock Pi to that standalone router. ?Plug in another computer to that router and not to the internet. ?Try ping and ssh both ways through that standalone router. ?If it works, the problem might be rules on your original router.
- Grab a spare Raspberry Pi. ?Remove the sd card from the HamClock Pi and put into the spare Pi. ?Connect that spare to the network. ?Boot, test. ?If it works, then something is up with the hardware.
- Swap the IP address between the HamClock Pi and the trailer Pi. ?Does the issue then follow to the trailer Pi and the HamClock Pi now works? ?If so, then the problem is following the IP address and you¡¯re back to finding a goofy config on your router.
And that is honestly all I can think of at the moment.
- Network connectivity?
- Proper IP addressing?
- Routing
- Ports open
- TCP, UDP, ICMP protocols allowed
- SSH configuration?
Browser yes, ping no? ?Sounds like protocols either at the Pi or the router.
Asa ?Jay
Sent via radio waves
toggle quoted message
Show quoted text
On Dec 7, 2023, at 10:57, Michael WA7SKG <wa7skg@...> wrote:
?
TSC-60 Man Washington:Issue Recap:On the local network are two RPis, hamclock-pi (192.168.2.150) and trailer-pi(192.168.2.163) (along with many other things on the network). Both RPis pretty much the same. The hamclock-pi has been running over a year and I would ssh into it as needed, last time over six months ago. Otherwise, not touched. If I wanted to do anything with hamclock, I would access it via the built-in web interface, no problems.Recently, I tried to ssh into hamclock-pi with No Route to Host error. Tried to ping hamclock-pi, Destination Unreachable error. Tried from trailer-pi and other computers, same results. Tried to access hamclock via web interface (http://192.168.2.150:8081/live.html), unable to connect.Connected keyboard and mouse to hamclock-pi and opened terminal. Compared ip addr, route, iptables, etc with trailer-pi. All settings basically identical with proper ip addresses. HamClock running on hamclock-pi and connecting to hamclock servers. Open browser on hamclock-pi and can surf the web. I can ping the router(192.168.2.1) no problem, cannot ping anything else on local network.hamclock-pi $ ssh [email protected] connects to itself without issuehamclock-pi $ ssh <anything else on network> No Route To HostHamclock-pi has been rebooted several times, no change. Hamclock-pi connected to network via Wi-Fi, gets address etc from DHCP on router.Again, had been working fine for over a year, not touched in any way for over six months, now does not work. No config settings or anything else has been changed.BTW, I used to maintain TSC-60 40 years ago. Nice system. Would be a dream to have one.Michael WA7SKGTSC-60 Man Washington via groups.io wrote on 12/7/23 10:04 AM:Please define ¡°it can ssh to itself.¡± ?That statement makes no sense to me.
From where, to where, via what route? ?Please be painfully specific.
Can you successfully ping the HamClock Pi from any other computer? ?If not, then you need to fix that problem first and it¡¯s a network problem.
You¡¯ve been given some good advice to check so far.
You can ping the router from the HamClock Pi but can¡¯t reach any other computer past it. ?That sounds like the gateway IP has not been configured (or has changed) on the Pi.
Have you run ifconfig on the HamClock Pi and shown the results here? ??(Sorry, I¡¯ve not been tracking this closely)
What is:
?* The IP address of the Pi
?* The subnet mask address entered in the Pi
?* The gateway IP address entered in the Pi
?* Connection to gateway (cat or Wi-Fi)
?* Gateway running DHCP or Static addressing
?* The IP address range allowed by the gateway
?* The ports allowed settings in the gateway
?* The contents of the sshd.conf file
This is a problem that needs more data. ?Get the answers and listings from above and perhaps someone can help further.
Asa ?Jay
Sent via radio waves
On Dec 7, 2023, at 09:41, Michael WA7SKG <wa7skg@...> wrote:
?Yes, it is enabled. It can ssh to itself, just nowhere else. It was working fine six months or so ago and hasn't been touched since until now.
Michael WA7SKG
Patrick Ouellette wrote on 12/5/23 3:55 PM:
I'd ssh enabled in rpi config? The pi has to be listening for connections from the network.
On Tue, Dec 5, 2023, 5:32?PM Michael WA7SKG <wa7skg@... <mailto:wa7skg@...>> wrote:
???I've got a Raspberry Pi that just runs HamClock (for now). It accesses
???the internet without problem. However, I cannot access it from my
???normal
???desktop or any other computer. It shows up as a connected device in my
???router, and I have the correct IP address. From the RPi, I can ping the
???router fine, but anything else in the network comes back as Destination
???Unreachable. It can ssh to itself, but trying to ssh to anything else
???returns No Route To Host. When I try to ssh or ping it from any other
???computer on the network, I get the same results. It has been maybe six
???months or more since I tried to ssh into it and it worked fine then.
???Nothing has changed, it basically hasn't been touched for months.
???Any ideas?
???-- ????73,
???Michael WA7SKG
???"Any day you do not learn one new thing is a wasted day."
