¿ªÔÆÌåÓý

  1. RaspberryPi-4-HamRadio
  2. Messages
Single Messages Topics Expanded Polls

Re: Cannot Access RPi

 

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


$ 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

$ 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?
Join [email protected] to automatically receive all group messages.