Pi4 troubleshooting


Bruce KX4AZ
 

SOLVED!!!  I tried pinging the ipv6address via the LAN, and the Pi4 responded.  Next, I tried to ssh in via that ipv6 address and was successful - and I was able to see that the wsprdaemon directory was still there....all good signs.  Next, I decided to  re-enable the wifi interface via raspi-config.  I had disabled it a couple of weeks ago in favor of a direct ethernet connection, but figured it was worth a try.  Once I re-enabled the wifi and rebooted the Pi, the DSL modem/router showed that the Pi4 had been assigned an ipv4address via DHCP, and the Pi4 host name was displayed....a very welcome sight  The final confirmation was checking the two Kiwis and seeing that the usual connections for WSPR were all present, and wspr.rocks confirmed that spots were once again being uploaded.  The DSL modem/router says that the Pi4 is connected via ethernet, so I'm not completely clear whether enabling the wifi somehow restored that, or wifi is the actual interface being used....but I'll take the "win", regardless.

Now all I need is a remote control to keep the deer from pulling down the Beverage antenna used for the 630/160/80/40m bands (!).


Bruce KX4AZ
 

Thanks all for the suggestions, I did cycle the PI4 via it's wifi controlled outlet a few times, to no avail so far.  Good idea about wireshark to see if there is some network traffic of use.  I don't know much about ipv6 addressing but that merits a second look, since the DSL modem shows it was assigned one...though there's no host name displayed as it normally is for that Pi4.  Now that I have perfect hindsight, I should have left a monitor plugged into the Pi4, and aimed an ip cameras at it to observe what the boot process (if any) looks like.  But even then, it would probably just identify an issue that requires in person presence to address.


Rob Robinett
 

You could run Wireshark on the PC and have it look for the DHCP broadcast packets on your LAN. 
If you can see them coming from your Pi after it is powered up, then you might find it is self assigning a 169.254.x.y address through which you could reach it.
Also try 'nmap' to scan your LAN address space.


On Sat, Nov 19, 2022 at 6:00 AM Bruce KX4AZ <bruce@...> wrote:
My remote spotter site in MI went offline yesterday, the day after I departed the area, after months of no major glitches - of course!  I am also no longer able to access the Pi4 via ssh or VNC.  The ADSL modem (BWG-210-700 model) it is plugged into does "see" it in the device list, but has not assigned it an ipv4 address via DHCP, as it would normally do.  It does list an ipv6 address for the Pi4, but I don't know how/if that protocol would work with ssh or VNC access.  A couple of power cycles on the Pi4, and restarting the ADSL modem, did not yield any changes.

Seeking troubleshooting advice for this non-responsive Pi4.  In person, the first thing I would do is check the power supply and then attach a monitor to observe whether there is any sort of boot process at power on.  I do have remote access to a Win10 PC on the same LAN, so wonder if there are any other "tricks" I might employ (ssh/VNS using the ipv6 address?).  My (fairly non-tech) brother will be at the site in person next week, so I may just have him mail the Pi4 to me for the in person troubleshooting I need to do.



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


WA2TP - Tom
 

As a suggestion, I added these to my system p/s, and wd server. 

They connect via wi-fi and you can use an app on your phone to turn on and off, should you need to reboot from anywhere.

Do not use on your router/modem network gear; once you kill that’s stupid you won’t be able to turn it back on. 

IMG_0301

On Nov 19, 2022, at 9:00 AM, Bruce KX4AZ <bruce@...> wrote:

My remote spotter site in MI went offline yesterday, the day after I departed the area, after months of no major glitches - of course!  I am also no longer able to access the Pi4 via ssh or VNC.  The ADSL modem (BWG-210-700 model) it is plugged into does "see" it in the device list, but has not assigned it an ipv4 address via DHCP, as it would normally do.  It does list an ipv6 address for the Pi4, but I don't know how/if that protocol would work with ssh or VNC access.  A couple of power cycles on the Pi4, and restarting the ADSL modem, did not yield any changes.

Seeking troubleshooting advice for this non-responsive Pi4.  In person, the first thing I would do is check the power supply and then attach a monitor to observe whether there is any sort of boot process at power on.  I do have remote access to a Win10 PC on the same LAN, so wonder if there are any other "tricks" I might employ (ssh/VNS using the ipv6 address?).  My (fairly non-tech) brother will be at the site in person next week, so I may just have him mail the Pi4 to me for the in person troubleshooting I need to do.


Bruce KX4AZ
 

My remote spotter site in MI went offline yesterday, the day after I departed the area, after months of no major glitches - of course!  I am also no longer able to access the Pi4 via ssh or VNC.  The ADSL modem (BWG-210-700 model) it is plugged into does "see" it in the device list, but has not assigned it an ipv4 address via DHCP, as it would normally do.  It does list an ipv6 address for the Pi4, but I don't know how/if that protocol would work with ssh or VNC access.  A couple of power cycles on the Pi4, and restarting the ADSL modem, did not yield any changes.

Seeking troubleshooting advice for this non-responsive Pi4.  In person, the first thing I would do is check the power supply and then attach a monitor to observe whether there is any sort of boot process at power on.  I do have remote access to a Win10 PC on the same LAN, so wonder if there are any other "tricks" I might employ (ssh/VNS using the ipv6 address?).  My (fairly non-tech) brother will be at the site in person next week, so I may just have him mail the Pi4 to me for the in person troubleshooting I need to do.