Greg Wooledge <g...@wooledge.org> wrote: > On Wed, Jan 22, 2025 at 13:29:41 +0000, Chris Green wrote: > > I have a remote headless system (running bullseye, will be updating to > > bookworm when I'm next there) that can connect to some systems using > > ssh but not to others (to which I can connect from everywhere else). > > What *actually* happens when you try? Show us the command you're > running and its full output. > Absolutely nothing until ssh times out, ping just pings away and reports 100% packet loss when I kill it.
> If you need more details, try adding the -v option when you ssh. > > > It also can't ping the systems which it can't connect ssh to. > > Again, seeing the *error message* from ping would be helpful. See above. But *%$^*%$%(*JGJHB me, it's started working now (I just did an "ssh -v" to get more information). Typical! It's not been working for well over a month. All the ssh on the remote system have been automatically restarted quite recently (I use autossh to keep them alive) and that seems to have fixed everything. I didn't dare restart them manually because it's them that set up the reverse tunnel to enable me to ssh to the system. The whole (remote) system seems to be running more quickly now, I suspect something had 'stuck' somehow and has, for whatever reason, become unstuck. Sorry for the noise. -- Chris Green ยท
