Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. Uncategorized
  4. anybody have an idea why some recent FreeBSD update would have broken the ability of ssh(1) to attach to a remote machine using

anybody have an idea why some recent FreeBSD update would have broken the ability of ssh(1) to attach to a remote machine using

Uncategorized
1 1 2
  • gumnos@mastodon.bsd.cafeundefined

    anybody have an idea why some recent FreeBSD update would have broken the ability of ssh(1) to attach to a remote machine using .ssh/config settings that set the HostName to an IP address, but it works if the HostName has an actual name? It doesn't seem to be *all* my ssh-by-IP-address items. Issuing with -vvv shows it hanging after

    debug3: Fssh_set_sock_tos: set socket 3 IP_TOS 0x48

    If I switch my .ssh/config to have "HostName full.server.name.example.com", it works fine, and FWIW, doing a `host $SERVERNAME` does return the correct/same IP address that was used in the .ssh/config file originally.

    For now I've updated it to just use the hostname and it works, but I can reliably switch back and forth and trigger the hang every time. In case it matters, this was with the 14.2p6 I was running as well as the 14.3p3 I just (finally) upgraded to in the hopes it would fix the issue:

    $ ssh -V
    OpenSSH_9.9p2, OpenSSL 3.0.16 11 Feb 2025

    1
    0
  • stefano@mastodon.bsd.cafeundefined stefano@mastodon.bsd.cafe shared this topic on
Log in to reply

Feed RSS
anybody have an idea why some recent FreeBSD update would have broken the ability of ssh(1) to attach to a remote machine using

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti