I upgraded three piholes this morning and now I cannot ssh into them. Anyone else having an issue like this?
What commands did you type exactly?
Hi @DanSchaper
~ % ssh pi@192.168.1.21
ping 192.168.1.21
PING 192.168.1.21 (192.168.1.21): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
I have three on my network for redundancy.
ping 192.168.1.22
PING 192.168.1.22 (192.168.1.22): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
ping 192.168.1.23
PING 192.168.1.23 (192.168.1.23): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
I tried rebooting .23 but it still does not respond
Sorry, I meant what commands did you type to update.
pihole -up
That's it, no other commands?
pihole -up on it's own wouldn't affect the networking like you are seeing. Are you able to ping other nodes, or ping 1.1.1.1 from the client? Are you able to ping 192.168.x.x addresses that are not Pi-holes? Are you able to ping the Pi-holes from other clients?
That was it.
I am able to ping my gateway:
% ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.686 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.889 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.928 ms
% ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=56 time=4.374 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=4.084 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=4.237 ms
I am going to reboot my Mac. I can hit the piholes from my iPhone. Maybe I was a victim of bad timing
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.