Re: RPi-4 w/Bookworm & Samsung Smart Monitor; Anyone?

is the Apt like thing something like apt install xxx?

On Sun, Dec 10, 2023 at 9:40?AM John <radio@...> wrote:

Just bought a Samsung M50C Smart Monitor, but I'm having trouble getting it to work on my RPi-4b w/Bookworm.

The set up screen does not show a Linux option, only Windows PC and Apple and some other Apt like thing.? I'm not able to get the sound working on the monitor, but the video works.

Anyone try using one of these monitors?? Any advice?

John,? W0GN

RPi-4 w/Bookworm & Samsung Smart Monitor; Anyone?

#15387

Just bought a Samsung M50C Smart Monitor, but I'm having trouble getting it to work on my RPi-4b w/Bookworm.

The set up screen does not show a Linux option, only Windows PC and Apple and some other Apt like thing.? I'm not able to get the sound working on the monitor, but the video works.

Anyone try using one of these monitors?? Any advice?

John,? W0GN

Re: Zero Browser

#15386

I have not found *any* browser that works on a pi zero that isn't slow, and doesn't crash the pi

Get

Zero Browser

#15385

Hi! Somebody can recommend a light browser for the Pi Zero?
Thanks in advance,

Jorge VE3EAD

Fw: A shipment from order #1162 is on the way

#15384

----- Forwarded Message -----

Show quoted text

From: Pineberry Pi <mgapinski@...>

To: "ldighera@..." <ldighera@...>

Sent: Friday, December 8, 2023 at 05:33:35 PM PST

Subject: A shipment from order #1162 is on the way


Order #12345

?

FedEx tracking number: xxxxxxxxxxx

Items in this shipment

HatDrive! Top (NVMe 2230, 2242 GEN 3) for Raspberry Pi 5?×?1

HatDrive! Bottom (NVMe 2230, 2242, 2280 GEN 3) for Raspberry Pi 5?×?1

Re: Cannot Access RPi

#15383

Ah, Leland and I took a lot of discussion direct, not on the forum. As he had not posted before, he was "New Member Moderated" which delayed his post, so he contacted me directly. That's why my response and the rest of our discussion did not show on the forum.

Looked closely at the ***noprefixroute issue. The entry is exactly the same as on a couple other Pis which work without problem and changing it had no effect on the situation. In fact, all six Linux computers on my network contain the noprefixroute entry and all except the hamclock-pi work fine. It is not the problem. It only pertains to adding an address and route permanently to the routing table.

Michael WA7SKG

N5XMT wrote on 12/7/23 6:24 PM:

Show quoted text

Here is your info and a reply from Leland explaining the issue...
This is from yesterday afternoon:
? $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
 ???? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 ???? inet 127.0.0.1/8 <> scope host lo
 ??????? valid_lft forever preferred_lft forever
 ???? inet6 ::1/128 scope host
 ??????? valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
 ???? link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
 ???? link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
 ???? inet 192.168.2.150/24 <> brd 192.168.2.255 <> scope global dynamic
noprefixroute wlan0
 ??????? valid_lft 5346sec preferred_lft 4446sec
 ???? inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
 ??????? valid_lft forever preferred_lft forever
And the reply from Leland:
if you issue the below command:
sudo route add default gw 192.168.2.1 <> wlan0
do things start working? if so, this ***noprefixroute (inline in your copy pasted output below) is probably your issue. noprefixroute means that a default gateway is not being added to the interface when the address is assigned. how did you set the IP address on WLAN0? through dhcpcd.conf or something else? if you're using dhcpcd.conf, do you have a static router=192.168.2.1 <> line?
-Leland
W7JQP
Get BlueMail for Android <>
On Dec 7, 2023, at 19:42, Michael WA7SKG <wa7skg@... <mailto:wa7skg@...>> wrote:
Maybe I am not receiving all the messages for some reason. I just reread
    every message I have received on the subject. I have not found any
    message that shows anything different than what I sent below. Nothing
    has changed in the listing for the default gateway and none of what I
    previously sent is any different than the route information I have
    listed below. Please cite the specific date and time of the message(s)
    you are referring to, as "something else in front of it" really does not
    help much in finding what you are talking about, and exactly what advice
    was given that I am ignoring.
You are telling me that the default gateway is not set properly, so
    please tell me what exactly is wrong with it and suggest how I may fix it.
Michael WA7SKG
N5XMT wrote on 12/7/23 2:23 PM:
When you sent this information the other day, the default
        192.168.2.1 <>
        <> line had something else in front of it.? 2
        different people stated that it meant that the default gateway
        wasn't
        set properly, so the packets couldn't see anything beyond the
        router.
Get BlueMail for Android <>
        On Dec 7, 2023, at 15:57, Michael WA7SKG <wa7skg@...
        <mailto:wa7skg@...>> wrote:
Please forgive my ignorance. Here is my gateway info:
$ route
        Kernel IP routing table
        Destination Gateway Genmask Flags Metric Ref Use
        Iface
        default192.168.2.1 <> <>
        0.0.0.0 UG 303 0 0
        wlan0
        192.168.2.0 <> <>
        0.0.0.0255.255.255.0 <>
        <> U 303 0 0
        wlan0
$ ip route
        default via192.168.2.1 <> <>
        dev wlan0 proto dhcp src192.168.2.150 <>
        <> metric 303
        192.168.2.0/24 <> <>
        dev wlan0 proto dhcp scope link src192.168.2.150
        <> <> metric 303
What exactly is incorrect about it and how do I fix it? These
        entries,
        other than the ip addresses, are identical to the RPi that works.
I have carefully read each response and tried to answer each
        one. Which
        responses have I ignored?
Pretend I am a six year old and explain it to me again.
Michael WA7SKG
N5XMT wrote on 12/7/23 11:39 AM:
Not sure why you aren't taking the advice that has been given,
        and only
        repeating yourself over and over.? Your default gateway is NOT set
        properly on the hamclock pi.? That is why you can only ping the
        router
        directly, but nothing else connected to it.? I saw 2 responses last
        night to you that showed how to troubleshoot and fix that, and it
        appears you just ignored them completely.
Get BlueMail for Android <>
        On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@...
        <mailto: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 (), 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 issue
        hamclock-pi $ ssh <anything else on network> No Route To Host
Hamclock-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 WA7SKG
TSC-60 Man Washington viagroups.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."

Re: Cannot Access RPi

#15382

Here is your info and a reply from Leland explaining the issue...

This is from yesterday afternoon:

? $ ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN

group default qlen 1000

???? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

???? inet scope host lo

??????? valid_lft forever preferred_lft forever

???? inet6 ::1/128 scope host

??????? valid_lft forever preferred_lft forever

2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast

state DOWN group default qlen 1000

???? link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP

group default qlen 1000

???? link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff

???? inet brd scope global dynamic

noprefixroute wlan0

??????? valid_lft 5346sec preferred_lft 4446sec

???? inet6 fe80::b167:b0a9:4308:e8e9/64 scope link

??????? valid_lft forever preferred_lft forever

And the reply from Leland:

if you issue the below command:

sudo route add default gw wlan0

do things start working? if so, this ***noprefixroute (inline in your copy pasted output below) is probably your issue. noprefixroute means that a default gateway is not being added to the interface when the address is assigned. how did you set the IP address on WLAN0? through dhcpcd.conf or something else? if you're using dhcpcd.conf, do you have a static router= line?

-Leland

W7JQP

Get

On Dec 7, 2023, at 19:42, Michael WA7SKG <wa7skg@...> wrote:

Show quoted text

Maybe I am not receiving all the messages for some reason. I just reread 
every message I have received on the subject. I have not found any 
message that shows anything different than what I sent below. Nothing 
has changed in the listing for the default gateway and none of what I 
previously sent is any different than the route information I have 
listed below. Please cite the specific date and time of the message(s) 
you are referring to, as "something else in front of it" really does not 
help much in finding what you are talking about, and exactly what advice 
was given that I am ignoring.

You are telling me that the default gateway is not set properly, so 
please tell me what exactly is wrong with it and suggest how I may fix it.

Michael WA7SKG



N5XMT wrote on 12/7/23 2:23 PM:
 When you sent this information the other day, the default  
 <> line had something else in front of it.? 2 
 different people stated that it meant that the default gateway wasn't 
 set properly, so the packets couldn't see anything beyond the router.
 
 Get BlueMail for Android <>
 On Dec 7, 2023, at 15:57, Michael WA7SKG <wa7skg@... 
 <mailto:wa7skg@...>> wrote:
 
     Please forgive my ignorance. Here is my gateway info:
 
        $ route
     Kernel IP routing table
     Destination     Gateway         Genmask         Flags Metric Ref    Use
     Iface
     default  <>      0.0.0.0         UG    303    0        0
     wlan0
       <>      0.0.0.0  <>    U     303    0        0
     wlan0
 
        $ ip route
     default via  <>  dev wlan0 proto dhcp src  <>  metric 303
       <>  dev wlan0 proto dhcp scope link src  <>  metric 303
 
 
     What exactly is incorrect about it and how do I fix it? These entries,
     other than the ip addresses, are identical to the RPi that works.
 
     I have carefully read each response and tried to answer each one. Which
     responses have I ignored?
 
     Pretend I am a six year old and explain it to me again.
 
     Michael WA7SKG
 
 
 
     N5XMT wrote on 12/7/23 11:39 AM:
 
         Not sure why you aren't taking the advice that has been given,
         and only
         repeating yourself over and over.? Your default gateway is NOT set
         properly on the hamclock pi.? That is why you can only ping the
         router
         directly, but nothing else connected to it.? I saw 2 responses last
         night to you that showed how to troubleshoot and fix that, and it
         appears you just ignored them completely.
 
         Get BlueMail for Android <>
         On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@...
         <mailto:wa7skg@...>> wrote:
 
         TSC-60 Man Washington:
 
         Issue Recap:
 
         On the local network are two RPis, hamclock-pi (
         <> <>) and
         trailer-pi( <>
         <>) (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 (), 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( <> <>) no
         problem, cannot ping anything else on local network.
 
         hamclock-pi $ ssh [email protected] connects to itself without issue
         hamclock-pi $ ssh <anything else on network> No Route To Host
 
         Hamclock-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 WA7SKG
 
 
         TSC-60 Man Washington  <>
         <> 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."

Re: Cannot Access RPi

#15381

Maybe I am not receiving all the messages for some reason. I just reread every message I have received on the subject. I have not found any message that shows anything different than what I sent below. Nothing has changed in the listing for the default gateway and none of what I previously sent is any different than the route information I have listed below. Please cite the specific date and time of the message(s) you are referring to, as "something else in front of it" really does not help much in finding what you are talking about, and exactly what advice was given that I am ignoring.

You are telling me that the default gateway is not set properly, so please tell me what exactly is wrong with it and suggest how I may fix it.

Michael WA7SKG

N5XMT wrote on 12/7/23 2:23 PM:

Show quoted text

When you sent this information the other day, the default 192.168.2.1 <> line had something else in front of it.? 2 different people stated that it meant that the default gateway wasn't set properly, so the packets couldn't see anything beyond the router.
Get BlueMail for Android <>
On Dec 7, 2023, at 15:57, Michael WA7SKG <wa7skg@... <mailto:wa7skg@...>> wrote:
Please forgive my ignorance. Here is my gateway info:
$ route
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use
    Iface
    default192.168.2.1  <>      0.0.0.0         UG    303    0        0
    wlan0
    192.168.2.0  <>      0.0.0.0255.255.255.0  <>    U     303    0        0
    wlan0
$ ip route
    default via192.168.2.1  <>  dev wlan0 proto dhcp src192.168.2.150  <>  metric 303
    192.168.2.0/24  <>  dev wlan0 proto dhcp scope link src192.168.2.150  <>  metric 303
What exactly is incorrect about it and how do I fix it? These entries,
    other than the ip addresses, are identical to the RPi that works.
I have carefully read each response and tried to answer each one. Which
    responses have I ignored?
Pretend I am a six year old and explain it to me again.
Michael WA7SKG
N5XMT wrote on 12/7/23 11:39 AM:
Not sure why you aren't taking the advice that has been given,
        and only
        repeating yourself over and over.? Your default gateway is NOT set
        properly on the hamclock pi.? That is why you can only ping the
        router
        directly, but nothing else connected to it.? I saw 2 responses last
        night to you that showed how to troubleshoot and fix that, and it
        appears you just ignored them completely.
Get BlueMail for Android <>
        On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@...
        <mailto: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 (), 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 issue
        hamclock-pi $ ssh <anything else on network> No Route To Host
Hamclock-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 WA7SKG
TSC-60 Man Washington viagroups.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."

Re: Cannot Access RPi

#15380

When you sent this information the other day, the default line had something else in front of it.? 2 different people stated that it meant that the default gateway wasn't set properly, so the packets couldn't see anything beyond the router.

Get

On Dec 7, 2023, at 15:57, Michael WA7SKG <wa7skg@...> wrote:

Show quoted text

Please forgive my ignorance. Here is my gateway info:

  $ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
default              0.0.0.0         UG    303    0        0 
wlan0
     0.0.0.0            U     303    0        0 
wlan0

  $ ip route
default via  dev wlan0 proto dhcp src  metric 303
 dev wlan0 proto dhcp scope link src  metric 303


What exactly is incorrect about it and how do I fix it? These entries, 
other than the ip addresses, are identical to the RPi that works.

I have carefully read each response and tried to answer each one. Which 
responses have I ignored?

Pretend I am a six year old and explain it to me again.

Michael WA7SKG



N5XMT wrote on 12/7/23 11:39 AM:
 Not sure why you aren't taking the advice that has been given, and only 
 repeating yourself over and over.? Your default gateway is NOT set 
 properly on the hamclock pi.? That is why you can only ping the router 
 directly, but nothing else connected to it.? I saw 2 responses last 
 night to you that showed how to troubleshoot and fix that, and it 
 appears you just ignored them completely.
 
 Get BlueMail for Android <>
 On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@... 
 <mailto:wa7skg@...>> wrote:
 
     TSC-60 Man Washington:
 
     Issue Recap:
 
     On the local network are two RPis, hamclock-pi (  <>) and
     trailer-pi(  <>) (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 (), 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(  <>) no
     problem, cannot ping anything else on local network.
 
     hamclock-pi $ ssh [email protected] connects to itself without issue
     hamclock-pi $ ssh <anything else on network> No Route To Host
 
     Hamclock-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 WA7SKG
 
 
     TSC-60 Man Washington   <>  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."

Re: Cannot Access RPi

#15379

Please forgive my ignorance. Here is my gateway info:

 $ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.2.1     0.0.0.0         UG    303    0        0 wlan0
192.168.2.0     0.0.0.0         255.255.255.0   U     303    0        0 wlan0

 $ ip route
default via 192.168.2.1 dev wlan0 proto dhcp src 192.168.2.150 metric 303
192.168.2.0/24 dev wlan0 proto dhcp scope link src 192.168.2.150 metric 303

What exactly is incorrect about it and how do I fix it? These entries, other than the ip addresses, are identical to the RPi that works.

I have carefully read each response and tried to answer each one. Which responses have I ignored?

Pretend I am a six year old and explain it to me again.

Michael WA7SKG

N5XMT wrote on 12/7/23 11:39 AM:

Show quoted text

Not sure why you aren't taking the advice that has been given, and only repeating yourself over and over.? Your default gateway is NOT set properly on the hamclock pi.? That is why you can only ping the router directly, but nothing else connected to it.? I saw 2 responses last night to you that showed how to troubleshoot and fix that, and it appears you just ignored them completely.
Get BlueMail for Android <>
On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@... <mailto: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 (), 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 issue
    hamclock-pi $ ssh <anything else on network> No Route To Host
Hamclock-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 WA7SKG
TSC-60 Man Washington viagroups.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."

Re: Cannot Access RPi

#15378

开云体育

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

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 issue
hamclock-pi $ ssh <anything else on network> No Route To Host

Hamclock-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 WA7SKG

TSC-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."

Re: Cannot Access RPi

#15377

Not sure why you aren't taking the advice that has been given, and only repeating yourself over and over.? Your default gateway is NOT set properly on the hamclock pi.? That is why you can only ping the router directly, but nothing else connected to it.? I saw 2 responses last night to you that showed how to troubleshoot and fix that, and it appears you just ignored them completely.

Get

On Dec 7, 2023, at 12:56, Michael WA7SKG <wa7skg@...> wrote:

Show quoted text

TSC-60 Man Washington:

Issue Recap:

On the local network are two RPis, hamclock-pi () and 
trailer-pi() (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 (), 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() no 
problem, cannot ping anything else on local network.

hamclock-pi $ ssh [email protected] connects to itself without issue
hamclock-pi $ ssh <anything else on network> No Route To Host

Hamclock-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 WA7SKG


TSC-60 Man Washington via  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."

Re: Cannot Access RPi

#15376

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 (), 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 issue
hamclock-pi $ ssh <anything else on network> No Route To Host

Hamclock-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 WA7SKG

TSC-60 Man Washington via groups.io wrote on 12/7/23 10:04 AM:

Show quoted text

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."

Re: Cannot Access RPi

#15375

开云体育

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

Show quoted text

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."

Re: Cannot Access RPi

#15374

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:

Show quoted text

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."

Re: Cannot Access RPi

#15373

I'd ssh enabled in rpi config? The pi has to be listening for connections from the network.?

Show quoted text

On Tue, Dec 5, 2023, 5:32?PM Michael WA7SKG <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."

Re: Cannot Access RPi

#15372

if you issue this command:
sudo route add default gw 192.168.2.1 wlan0

do things start working? if so, this is probably your issue. noprefixroute means that a default gateway is not being added to the interface when the address is assigned. how did you set the IP address on WLAN0? through dhcpcd.conf or something else? if you're using dhcpcd.conf, do you have a static router=192.168.2.1 line?

-Leland

W7JQP

? $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
? ? ?link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
? ? ?inet??scope host lo
? ? ? ? valid_lft forever preferred_lft forever
? ? ?inet6 ::1/128 scope host
? ? ? ? valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
? ? ?link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
? ? ?link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
? ? ?inet??brd 192.168.2.255 scope global dynamic
noprefixroute wlan0
? ? ? ? valid_lft 5346sec preferred_lft 4446sec
? ? ?inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
? ? ? ? valid_lft forever preferred_lft forever

On Tue, Dec 5, 2023 at 6:29?PM Michael WA7SKG <wa7skg@...> wrote:

I've rebooted several times to no avail.? I have multiple RPis and I see
no difference between them, other than they all work except this one.

? $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
? ? ?link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
? ? ?inet scope host lo
? ? ? ? valid_lft forever preferred_lft forever
? ? ?inet6 ::1/128 scope host
? ? ? ? valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
? ? ?link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
? ? ?link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
? ? ?inet brd 192.168.2.255 scope global dynamic
noprefixroute wlan0
? ? ? ? valid_lft 5346sec preferred_lft 4446sec
? ? ?inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
? ? ? ? valid_lft forever preferred_lft forever

? $ ip route
default via 192.168.2.1 dev wlan0 proto dhcp src 192.168.2.150 metric 303
dev wlan0 proto dhcp scope link src 192.168.2.150 metric 303

$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target? ? ?prot opt source? ? ? ? ? ? ? ?destination

Chain FORWARD (policy ACCEPT)
target? ? ?prot opt source? ? ? ? ? ? ? ?destination

Chain OUTPUT (policy ACCEPT)
target? ? ?prot opt source? ? ? ? ? ? ? ?destination

Any other details that may help? It does access the internet, web pages
come up and the HamClock data updates correctly. I can tell that ssh is
enabled and working as it can ssh to itself, but not to other computers
on the network, nor can it ping.

Two essentially the same RPis, .163 works, .150 does not.

michael@Desk-3 ~ $ nmap -Pn 192.168.2.150

Starting Nmap 7.01 ( ) at 2023-12-05 18:23 PST
Nmap scan report for 192.168.2.150
Host is up (0.068s latency).
All 1000 scanned ports on 192.168.2.150 are filtered

Nmap done: 1 IP address (1 host up) scanned in 5.90 seconds
michael@Desk-3 ~ $
michael@Desk-3 ~ $
michael@Desk-3 ~ $
michael@Desk-3 ~ $ nmap -Pn 192.168.2.163

Starting Nmap 7.01 ( ) at 2023-12-05 18:23 PST
Nmap scan report for 192.168.2.163
Host is up (0.10s latency).
Not shown: 998 closed ports
PORT? ? ?STATE SERVICE
22/tcp? ?open? ssh
5900/tcp open? vnc

Nmap done: 1 IP address (1 host up) scanned in 2.44 seconds

? $ route
Kernel IP routing table
Destination? ? ?Gateway? ? ? ? ?Genmask? ? ? ? ?Flags Metric Ref? ? Use
Iface
default? ? ? ? ?192.168.2.1? ? ?0.0.0.0? ? ? ? ?UG? ? 100? ? 0? ? ? ? 0
wlan0
192.168.2.0? ? ?*? ? ? ? ? ? ? ?255.255.255.0? ?U? ? ?100? ? 0? ? ? ? 0
wlan0

Michael

David Ranch wrote on 12/5/23 5:23 PM:
>
> Without having all the details here, I would have to guess you might
> have an incorrect subnet mask configured on your Rpi.? While logged into
> the Rpi via the console (HDMI display, etc),
>
> 1. gracefully reboot the pi - this might easily resolve the issue but
> won't tell you what happened
>
> 2. send us the output of:
>
>? ?? ip addr
>? ?? ip route
>? ?? sudo iptables -L
>
> --David
> KI6ZHD
>
> 12/05/2023 02:32 PM, Michael 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?
>>
>>
>
>

Re: Cannot Access RPi

#15371

if you issue the below command:
sudo route add default gw 192.168.2.1 wlan0

do things start working? if so, this (inline in your copy pasted output below) is probably your issue. noprefixroute means that a default gateway is not being added to the interface when the address is assigned. how did you set the IP address on WLAN0? through dhcpcd.conf or something else? if you're using dhcpcd.conf, do you have a static router=192.168.2.1 line?

-Leland
W7JQP

? $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
? ? ?link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
? ? ?inet??scope host lo
? ? ? ? valid_lft forever preferred_lft forever
? ? ?inet6 ::1/128 scope host
? ? ? ? valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
? ? ?link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
? ? ?link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
? ? ?inet??brd 192.168.2.255 scope global dynamic
noprefixroute wlan0
? ? ? ? valid_lft 5346sec preferred_lft 4446sec
? ? ?inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
? ? ? ? valid_lft forever preferred_lft forever

Re: Cannot Access RPi

#15370

if you issue the below command:
sudo route add default gw 192.168.2.1 wlan0

do things start working? if so, this ***noprefixroute (inline in your copy pasted output below) is probably your issue. noprefixroute means that a default gateway is not being added to the interface when the address is assigned. how did you set the IP address on WLAN0? through dhcpcd.conf or something else? if you're using dhcpcd.conf, do you have a static router=192.168.2.1 line?

-Leland
W7JQP

? $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
? ? ?link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
? ? ?inet scope host lo
? ? ? ? valid_lft forever preferred_lft forever
? ? ?inet6 ::1/128 scope host
? ? ? ? valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
? ? ?link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
? ? ?link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
? ? ?inet brd 192.168.2.255 scope global dynamic
***noprefixroute wlan0
? ? ? ? valid_lft 5346sec preferred_lft 4446sec
? ? ?inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
? ? ? ? valid_lft forever preferred_lft forever

Show quoted text

On Wed, Dec 6, 2023 at 9:17?AM Michael WA7SKG <wa7skg@...> wrote:

It was working fine six months ago. Hasn't been touched since, just
sitting there running HamClock. Just the RPi with a monitor.

Since I built it a year or more ago, I always used ssh to access it and
pulled up HamClock via the web browser interface when I needed to change
it. Haven't needed to touch it for a long time. Decided to change some
things in HamClock and the web couldn't connect. Tried ssh and that did
not work, either, nor could I ping it.

I plugged in a keyboard and mouse since I could not ssh into it to check
things. I can ping the router but nothing else. I can access web pages
and anything over the internet. Just nothing on the local network.
Nothing has been changed in my router in over a year.

Very strange.

Michael WA7SKG

David Ranch wrote on 12/6/23 8:46 AM:
>
> Since this seems to be over wifi, I have seen some access points that
> will NOT allow wifi clients to communicate to other adjacent wifi
> devices.? Some APs will allow you to enable/disable that cross-client
> communications but since it sounds like you have another Wifi-connected
> Raspberry Pi that doesn't have this issue, it's hard to explain this
> behavior. Maybe these different RPIs are using different hardware (one
> is a v3 and the other is a v4) and there is a Wifi HW behavior
> difference here?? Another command to try and see what's going on is "arp
> -an".? From the problem Rpi, try pinging other known devices on your
> internal network be it that they are connected via wifi or wired and
> then run the arp command to see if your "broken" Rpi learns the remote
> host's MAC address.
>
> Maybe get another SD card, put Raspberry Pi OS 12/Bookworm, and
> temporarily boot it on your problem Rpi device and see if that makes any
> difference.
>
> --David
> KI6ZHD
>
>
> On 12/05/2023 06:29 PM, Michael WA7SKG wrote:
>> I've rebooted several times to no avail.? I have multiple RPis and I
>> see no difference between them, other than they all work except this one.
>>
>> ?$ ip addr
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> group default qlen 1000
>> ??? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> ??? inet scope host lo
>> ?????? valid_lft forever preferred_lft forever
>> ??? inet6 ::1/128 scope host
>> ?????? valid_lft forever preferred_lft forever
>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>> state DOWN group default qlen 1000
>> ??? link/ether b8:27:eb:27:b3:e0 brd ff:ff:ff:ff:ff:ff
>> 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
>> group default qlen 1000
>> ??? link/ether 74:da:38:41:e7:dc brd ff:ff:ff:ff:ff:ff
>> ??? inet brd 192.168.2.255 scope global dynamic
>> noprefixroute wlan0
>> ?????? valid_lft 5346sec preferred_lft 4446sec
>> ??? inet6 fe80::b167:b0a9:4308:e8e9/64 scope link
>> ?????? valid_lft forever preferred_lft forever
>>
>>
>> ?$ ip route
>> default via 192.168.2.1 dev wlan0 proto dhcp src 192.168.2.150 metric 303
>> dev wlan0 proto dhcp scope link src 192.168.2.150
>> metric 303
>>
>> $ sudo iptables -L
>> Chain INPUT (policy ACCEPT)
>> target???? prot opt source?????????????? destination
>>
>> Chain FORWARD (policy ACCEPT)
>> target???? prot opt source?????????????? destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target???? prot opt source?????????????? destination
>>
>>
>>
>> Any other details that may help? It does access the internet, web
>> pages come up and the HamClock data updates correctly. I can tell that
>> ssh is enabled and working as it can ssh to itself, but not to other
>> computers on the network, nor can it ping.
>>
>> Two essentially the same RPis, .163 works, .150 does not.
>>
>> michael@Desk-3 ~ $ nmap -Pn 192.168.2.150
>>
>> Starting Nmap 7.01 ( ) at 2023-12-05 18:23 PST
>> Nmap scan report for 192.168.2.150
>> Host is up (0.068s latency).
>> All 1000 scanned ports on 192.168.2.150 are filtered
>>
>> Nmap done: 1 IP address (1 host up) scanned in 5.90 seconds
>> michael@Desk-3 ~ $
>> michael@Desk-3 ~ $
>> michael@Desk-3 ~ $
>> michael@Desk-3 ~ $ nmap -Pn 192.168.2.163
>>
>> Starting Nmap 7.01 ( ) at 2023-12-05 18:23 PST
>> Nmap scan report for 192.168.2.163
>> Host is up (0.10s latency).
>> Not shown: 998 closed ports
>> PORT???? STATE SERVICE
>> 22/tcp?? open? ssh
>> 5900/tcp open? vnc
>>
>> Nmap done: 1 IP address (1 host up) scanned in 2.44 seconds
>>
>> ?$ route
>> Kernel IP routing table
>> Destination???? Gateway???????? Genmask???????? Flags Metric Ref? ?
>> Use Iface
>> default???????? 192.168.2.1???? 0.0.0.0???????? UG??? 100 0??????? 0
>> wlan0
>> 192.168.2.0???? *?????????????? 255.255.255.0?? U???? 100 0??????? 0
>> wlan0
>>
>>
>>
>> Michael
>>
>>
>>
>>
>> David Ranch wrote on 12/5/23 5:23 PM:
>>>
>>> Without having all the details here, I would have to guess you might
>>> have an incorrect subnet mask configured on your Rpi. While logged
>>> into the Rpi via the console (HDMI display, etc),
>>>
>>> 1. gracefully reboot the pi - this might easily resolve the issue but
>>> won't tell you what happened
>>>
>>> 2. send us the output of:
>>>
>>> ??? ip addr
>>> ??? ip route
>>> ??? sudo iptables -L
>>>
>>> --David
>>> KI6ZHD
>>>
>>> 12/05/2023 02:32 PM, Michael 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?
>>>>
>>>>

Re: Cannot Access RPi

#15369

Could have reflashed it by now hihi?

I like the puzzle, what about disable ssh service reboot and re-enable it?

via rasp-conf?

k