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:
toggle quoted message
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."
|
Michael WA7SKG