• Re: ssh issue that I don't understand

    From Joe@3:633/10 to All on Sunday, July 05, 2026 22:50:02
    On Sun, 5 Jul 2026 20:19:12 +0100
    Chris Green <cl@isbd.net> wrote:

    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?


    Could the issue be that technically isbd.biz is a domain name and not a hostname? That ssh is trying to log you into a network account rather
    than a particular computer, and is using the only name it knows you by?

    If so, it may well be that Alexander's recommendation will fix things.

    --
    Joe

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Sunday, July 05, 2026 22:50:02
    Robert Heller <heller@deepsoft.com> wrote:
    At Sun, 5 Jul 2026 20:19:12 +0100 Chris Green <cl@isbd.net> wrote:


    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?


    This probably relates to the contents of ~/.ssh/known_hosts. 213.171.194.64 is in ~/.ssh/known_hosts, but isbd.biz is not.

    None of my systems have a known_hosts file, I have it disabled as
    follows:-

    HashKnownHosts no
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null
    LogLevel=ERROR

    Like quite a few people nowadays I find it more of a nusiance than a
    help.

    I can log in to other systems using the hostname rather than the IP
    address. E.g. I have another VPS at gvps.uk and I can log in to that
    using 'ssh gvps.uk'. I can't see any real difference between the
    setup of gvps.uk and isbd.biz in my ~/.ssh/config file but one works
    OK using the hostname and the other doesn't.

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Sunday, July 05, 2026 23:00:01
    Simon Hollenbach <ionpowered@gmail.com> wrote:
    Hi Chris,

    On Sun, 5 Jul 2026 at 21:40, Chris Green <cl@isbd.net> wrote:

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.
    Your domain also has an AAAA record, could it be that ssh is trying to
    reach that instead of the IP you tested above?
    You should be able to test this by forcing SSH to use IPv4, using `ssh
    -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't understand what's going on, you can repeat `--verbose` or use multiple
    `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further.

    Brilliant! That's what was causing the oddity.

    I can fix the issue simply by adding an entry in ~/.ssh/config but I
    wanted to understand (better) what was going on.

    Thanks! :-)

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeffrey Walton@3:633/10 to All on Monday, July 06, 2026 02:10:01
    On Sun, Jul 5, 2026 at 6:35?PM Simon Hollenbach <ionpowered@gmail.c
    wrote:

    On Sun, 5 Jul 2026 at 21:40, Chris Green <cl@isbd.net> wrote:

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.
    Your domain also has an AAAA record, could it be that ssh is trying to
    reach that instead of the IP you tested above?
    You should be able to test this by forcing SSH to use IPv4, using `ssh
    -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't understand what's going on, you can repeat `--verbose` or use multiple
    `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further.

    That does not make sense (to me). Isn't that like saying you connect
    to one host using IPv4, and another host using IPv6, under the same
    DNS name. Why would someone do that???

    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?
    Do you have some custom ssh client config on the machines connecting
    to your VPS? It should be in ~/.ssh/config or /etc/ssh/ssh_config ,
    See `man 5 ssh_config`. If so, does any of it concern the host you're connecting to?

    Jeff

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Michel Verdier@3:633/10 to All on Monday, July 06, 2026 07:20:01
    On 2026-07-05, Chris Green wrote:

    None of my systems have a known_hosts file, I have it disabled as
    follows:-

    HashKnownHosts no
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null
    LogLevel=ERROR

    Like quite a few people nowadays I find it more of a nusiance than a
    help.

    But it protects you from man-in-the-middle attacks which is a bigger
    nuisance. And which could cause your problem.

    I can log in to other systems using the hostname rather than the IP
    address. E.g. I have another VPS at gvps.uk and I can log in to that
    using 'ssh gvps.uk'. I can't see any real difference between the
    setup of gvps.uk and isbd.biz in my ~/.ssh/config file but one works
    OK using the hostname and the other doesn't.

    If you have problem using hostname it could be a DNS problem.
    gvps.uk has no IPv6 but isbd.biz has one.

    $ dig +short isbd.biz aaaa
    2a00:1098:82::6:1

    Is 2a00:1098:82::6:1 the correct IPv6 adress ?
    If so could you try ssh 2a00:1098:82::6:1 ?

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Darac Marjal@3:633/10 to All on Monday, July 06, 2026 10:10:01
    On 06/07/2026 01:02, Jeffrey Walton wrote:
    On Sun, Jul 5, 2026 at 6:35?PM Simon Hollenbach <ionpowered@gmail.com> wrote:
    On Sun, 5 Jul 2026 at 21:40, Chris Green <cl@isbd.net> wrote:
    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's
    password" which doesn't exist and I can't log in.
    Your domain also has an AAAA record, could it be that ssh is trying to
    reach that instead of the IP you tested above?
    You should be able to test this by forcing SSH to use IPv4, using `ssh
    -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't
    understand what's going on, you can repeat `--verbose` or use multiple
    `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further.
    That does not make sense (to me). Isn't that like saying you connect
    to one host using IPv4, and another host using IPv6, under the same
    DNS name. Why would someone do that???

    I think there's an old adage that "hosts don't have IP addresses,
    interfaces do". It's easy to think that the isbd.biz box has two IP
    addresses, but in practice there's always going to be _some_ sort of
    split between IPv4 and IPv6, even if it's just down to the "network
    stack" being different.

    The target here is to make a connection to the SSH daemon. So if that's
    only listening on one interface that MIGHT not be the one with the IPv6 address on (maybe IPv6 is tunnel, as an example). Even if there's only
    one interface, SSHd could still be listening on "0.0.0.0" rather than
    "::" (I think the default can be changed, but in practice "::" means "everything IPv4 *and* IPv6).

    For most purposes, IPv4 and IPv6 do look very similar to "different hosts".



    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?
    Do you have some custom ssh client config on the machines connecting
    to your VPS? It should be in ~/.ssh/config or /etc/ssh/ssh_config ,
    See `man 5 ssh_config`. If so, does any of it concern the host you're
    connecting to?
    Jeff



    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 10:20:02
    Alexander V. Makartsev <avbetev@gmail.com> wrote:
    [-- text/plain, size 1.3K, charset UTF-8, 43 lines, encoding 8bit --]

    On 7/6/26 00:19, Chris Green wrote:
    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for"chris@isbd.biz's password"
    which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?

    Check your ssh client config file (should be at /home/chris/.ssh/config)
    You probably didn't setup it for the host isbd.biz, or didn't put the IdentityFile directive correctly.
    The host entry in your case should look like this:

    Host isbd.biz
    ÿ ÿHostName isbd.biz
    ÿ ÿPort 22
    ÿ ÿUser chris
    ÿ ÿIdentityFile ~/.ssh/my-ssh-key-for-isbd-biz.key

    But that's all default settings. Sites work without entries in
    ~/.ssh/config if the configuration is as you've shown above.

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 10:20:02
    Joe <joe@jretrading.com> wrote:
    On Sun, 5 Jul 2026 20:19:12 +0100
    Chris Green <cl@isbd.net> wrote:

    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh. My user
    account on both my local machine (desktop and laptop) is 'chris' and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?


    Could the issue be that technically isbd.biz is a domain name and not a hostname? That ssh is trying to log you into a network account rather
    than a particular computer, and is using the only name it knows you by?

    It's a single host at that address/domain. As I said it's a VPS and
    the isbd.biz domain is mine and has A and AAAA records pointing solely
    at the VPS.

    As pointed out elsewhere the issue is caused by isbd.biz having an
    IPV6 address as well as an IPV4 one.

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Monday, July 06, 2026 11:00:02
    use correct route

    On lun., 2026-07-06 at 10:50 +0200, jean-christophe wrote:


    On lun., 2026-07-06 at 08:53 +0100, Chris Green wrote:
    Joe <joe@jretrading.com> wrote:
    On Sun, 5 Jul 2026 20:19:12 +0100
    Chris Green <cl@isbd.net> wrote:

    This isn't a problem as such but I don't understand why it's
    happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh.ÿ My
    user
    account on both my local machine (desktop and laptop) is
    'chris'
    and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only
    using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get
    prompted
    for
    my local system's public key passphrase and I can log in
    successfully.

    However if I try 'ssh isbd.biz' I get prompted for
    "chris@isbd.biz's
    password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so
    why
    does ssh not work using the name rather than the IP address?


    Could the issue be that technically isbd.biz is a domain name and
    not a
    hostname? That ssh is trying to log you into a network account
    rather
    than a particular computer, and is using the only name it knows
    you
    by?

    It's a single host at that address/domain. As I said it's a VPS and
    the isbd.biz domain is mine and has A and AAAA records pointing
    solely
    at the VPS.

    may be you add ipv6 in A records


    As pointed out elsewhere the issue is caused by isbd.biz having an
    IPV6 address as well as an IPV4 one.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Monday, July 06, 2026 11:00:02


    On lun., 2026-07-06 at 08:53 +0100, Chris Green wrote:
    Joe <joe@jretrading.com> wrote:
    On Sun, 5 Jul 2026 20:19:12 +0100
    Chris Green <cl@isbd.net> wrote:

    This isn't a problem as such but I don't understand why it's
    happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh.ÿ My user
    account on both my local machine (desktop and laptop) is 'chris'
    and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only
    using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted
    for
    my local system's public key passphrase and I can log in
    successfully.

    However if I try 'ssh isbd.biz' I get prompted for
    "chris@isbd.biz's
    password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz so
    why
    does ssh not work using the name rather than the IP address?


    Could the issue be that technically isbd.biz is a domain name and
    not a
    hostname? That ssh is trying to log you into a network account
    rather
    than a particular computer, and is using the only name it knows you
    by?

    It's a single host at that address/domain. As I said it's a VPS and
    the isbd.biz domain is mine and has A and AAAA records pointing
    solely
    at the VPS.

    may be you add ipv6 in A records


    As pointed out elsewhere the issue is caused by isbd.biz having an
    IPV6 address as well as an IPV4 one.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Monday, July 06, 2026 11:10:01
    $ sudo route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    default _gateway 0.0.0.0 UG 100 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s31f6

    route isn't ipv6

    On lun., 2026-07-06 at 10:52 +0200, jean-christophe wrote:
    use correct route

    On lun., 2026-07-06 at 10:50 +0200, jean-christophe wrote:


    On lun., 2026-07-06 at 08:53 +0100, Chris Green wrote:
    Joe <joe@jretrading.com> wrote:
    On Sun, 5 Jul 2026 20:19:12 +0100
    Chris Green <cl@isbd.net> wrote:

    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    I have a VPS called isbd.biz and I access it using ssh.ÿ My
    user
    account on both my local machine (desktop and laptop) is
    'chris'
    and
    my user account on isbd.biz is also 'chris'.

    I have account 'chris' on isbd.biz set up to allow login only
    using
    public key authentication.

    The ip address of isbd.biz is 213.171.194.64.

    If I log in with 'ssh 213.171.194.64' I, correctly, get
    prompted
    for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for
    "chris@isbd.biz's
    password" which doesn't exist and I can't log in.

    'host isbd.biz' returns the correct IP address for isbd.biz
    so
    why
    does ssh not work using the name rather than the IP address?


    Could the issue be that technically isbd.biz is a domain name
    and
    not a
    hostname? That ssh is trying to log you into a network account
    rather
    than a particular computer, and is using the only name it knows
    you
    by?

    It's a single host at that address/domain. As I said it's a VPS
    and
    the isbd.biz domain is mine and has A and AAAA records pointing
    solely
    at the VPS.

    may be you add ipv6 in A records


    As pointed out elsewhere the issue is caused by isbd.biz having
    an
    IPV6 address as well as an IPV4 one.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Alexander V. Makartsev@3:633/10 to All on Monday, July 06, 2026 12:30:02
    On 7/6/26 12:50, Chris Green wrote:
    Alexander V. Makartsev<avbetev@gmail.com> wrote:
    [-- text/plain, size 1.3K, charset UTF-8, 43 lines, encoding 8bit --]

    On 7/6/26 00:19, Chris Green wrote:
    ...
    'host isbd.biz' returns the correct IP address for isbd.biz so why
    does ssh not work using the name rather than the IP address?

    Check your ssh client config file (should be at /home/chris/.ssh/config)
    You probably didn't setup it for the host isbd.biz, or didn't put the
    IdentityFile directive correctly.
    The host entry in your case should look like this:

    Host isbd.biz
    ? ?HostName isbd.biz
    ? ?Port 22
    ? ?User chris
    ? ?IdentityFile ~/.ssh/my-ssh-key-for-isbd-biz.key

    But that's all default settings. Sites work without entries in
    ~/.ssh/config if the configuration is as you've shown above.

    SSH client uses password authentication by default, so if you want to authenticate with private key then you need to explicitly setup
    "IdentityFile" directive or use "-i" command line parameter to select a
    key file.
    It is a good practice, at least for me, to explicitly setup separate
    entries for each host, because different hosts might have different
    keys, different ports and protocols, different users, different
    encryption algorithms, etc.
    If you have one-ssh-key-for-everything and always use the default port,
    then you can use "Host *" directive to choose default settings, but
    doing this might complicate things in the future.
    --
    With kindest regards, Alexander.
    Debian - The universal operating system
    https://www.debian.org


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Monday, July 06, 2026 12:50:02


    On lun., 2026-07-06 at 15:25 +0500, Alexander V. Makartsev wrote:
    ÿ
    On 7/6/26 12:50, Chris Green wrote:
    ÿ
    ÿ
    ÿ
    Alexander V. Makartsev <avbetev@gmail.com> wrote:
    ÿ
    ÿ
    [-- text/plain, size 1.3K, charset UTF-8, 43 lines, encoding 8bit
    --]

    On 7/6/26 00:19, Chris Green wrote:
    ÿ
    ÿ
    ...
    'host isbd.biz' returns the correct IP address for isbd.biz so
    why
    does ssh not work using the name rather than the IP address?

    ÿ
    ÿ
    Check your ssh client config file (should be at
    /home/chris/.ssh/config)
    You probably didn't setup it for the host isbd.biz, or didn't put
    the
    IdentityFile directive correctly.
    The host entry in your case should look like this:

    Host isbd.biz
    ÿ ÿHostName isbd.biz
    ÿ ÿPort 22
    ÿ ÿUser chris
    ÿ ÿIdentityFile ~/.ssh/my-ssh-key-for-isbd-biz.key

    ÿ
    ÿ
    But that's all default settings. Sites work without entries in ~/.ssh/config if the configuration is as you've shown above.

    ÿ
    ÿSSH client uses password authentication by default, so if you want
    to authenticate with private key then you need to explicitly setup "IdentityFile" directive or use "-i" command line parameter to select
    a key file.
    ÿIt is a good practice, at least for me, to explicitly setup separate
    entries for each host, because different hosts might have different
    keys, different ports and protocols, different users, different
    encryption algorithms, etc.
    ÿIf you have one-ssh-key-for-everything and always use the default
    port, then you can use "Host *" directive to choose default settings,
    but doing this might complicate things in the future.

    Port xxxx
    PermitRootLogin no
    PasswordAuthentication no
    PubkeyAuthentication yes

    you need to

    ssh-copy-id -i ~/.ssh/keyname user@host

    sudo systemctl restart sshd

    regards,
    jean-christophe

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Greg Wooledge@3:633/10 to All on Monday, July 06, 2026 13:10:01
    On Mon, Jul 06, 2026 at 15:25:55 +0500, Alexander V. Makartsev wrote:
    On 7/6/26 12:50, Chris Green wrote:
    Alexander V. Makartsev<avbetev@gmail.com> wrote:
    The host entry in your case should look like this:

    Host isbd.biz
    ? ?HostName isbd.biz
    ? ?Port 22
    ? ?User chris
    ? ?IdentityFile ~/.ssh/my-ssh-key-for-isbd-biz.key

    But that's all default settings. Sites work without entries in ~/.ssh/config if the configuration is as you've shown above.

    The IdentityFile line there is not a default setting.

    SSH client uses password authentication by default, so if you want to authenticate with private key then you need to explicitly setup "IdentityFile" directive or use "-i" command line parameter to select a key file.

    This is incorrect. ssh will use key authentication by default, but
    only if your key has one of the default filenames.

    Obviously ~/.ssh/my-ssh-key-for-isbd-biz.key is not a default filename
    that ssh will look for.

    In Trixie's ssh(1) (10.0p1):

    -i identity_file
    Selects a file from which the identity (private key) for public
    key authentication is read. You can also specify a public key
    file to use the corresponding private key that is loaded in
    ssh-agent(1) when the private key file is not present locally.
    The default is ~/.ssh/id_rsa, ~/.ssh/id_ecdsa,
    ~/.ssh/id_ecdsa_sk, ~/.ssh/id_ed25519 and ~/.ssh/id_ed25519_sk.
    Identity files may also be specified on a per-host basis in the
    configuration file.

    If your key is in one of those filenames, then you don't need to specify
    it with a -i option. ssh will simply try to use it. (The list of
    filenames changes from time to time, so consult your own ssh(1) to be sure
    of which ones are being used.)

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Greg Wooledge@3:633/10 to All on Monday, July 06, 2026 13:20:01
    On Mon, Jul 06, 2026 at 08:53:59 +0100, Chris Green wrote:
    It's a single host at that address/domain. As I said it's a VPS and
    the isbd.biz domain is mine and has A and AAAA records pointing solely
    at the VPS.

    As pointed out elsewhere the issue is caused by isbd.biz having an
    IPV6 address as well as an IPV4 one.

    There's still a mystery here -- why do you get different results
    when you connect to the IPv6 address instead of the IPv4 address?

    You'd probably have to investigate the server side to figure out why
    those two addresses have different behaviors. It could be that you're
    running two separate instances of sshd. I don't think that's the
    most likely answer, but it's a possibility.

    You could also be using a Match block in your sshd_config, which
    disables key authentication (either globally or for specific users)
    when the local or remote address is IPv6. This would be a weird setup,
    but I can't rule it out.

    It could also be something else that I can't currently imagine.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From tomas@3:633/10 to All on Monday, July 06, 2026 14:00:01
    On Mon, Jul 06, 2026 at 12:43:13PM +0200, jean-christophe wrote:
    [...]
    Port xxxx
    PermitRootLogin no
    PasswordAuthentication no
    PubkeyAuthentication yes

    you need to

    ssh-copy-id -i ~/.ssh/keyname user@host
    Not relevant for the OP, since it was working when using the IP (v4)
    address, just not with the name (which seems to resolve first to the
    IPv6, so that seems to be a clue).
    Cheers
    --
    t


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 15:20:02
    Hello,

    On Sun, Jul 05, 2026 at 09:28:57PM +0100, Chris Green wrote:
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null

    Like quite a few people nowadays I find it more of a nusiance than a
    help.

    lolwat

    In a thread where you tell us you've been confused about which host you
    are trying to log in to, and if you had been trying a password you would
    have been typing it into someone else's server (!), you disable host key checking because "like quite a few people nowadays I find it more of a nuisance"

    Please do spread the message to all these other wrong people you know!

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 15:30:01
    Hello,

    On Mon, Jul 06, 2026 at 08:53:59AM +0100, Chris Green wrote:
    the issue is caused by isbd.biz having an IPV6 address as well as an
    IPV4 one.

    Unless you meant to say, "it has an IPv6 address in DNS that is
    incorrect and pointing at some other host", no, that is not your issue.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Vincent Lefevre@3:633/10 to All on Monday, July 06, 2026 16:10:01
    On 2026-07-06 07:10:43 -0400, Greg Wooledge wrote:
    On Mon, Jul 06, 2026 at 08:53:59 +0100, Chris Green wrote:
    It's a single host at that address/domain. As I said it's a VPS and
    the isbd.biz domain is mine and has A and AAAA records pointing solely
    at the VPS.

    As pointed out elsewhere the issue is caused by isbd.biz having an
    IPV6 address as well as an IPV4 one.

    There's still a mystery here -- why do you get different results
    when you connect to the IPv6 address instead of the IPv4 address?

    You'd probably have to investigate the server side to figure out why
    those two addresses have different behaviors. It could be that you're running two separate instances of sshd. I don't think that's the
    most likely answer, but it's a possibility.

    You could also be using a Match block in your sshd_config, which
    disables key authentication (either globally or for specific users)
    when the local or remote address is IPv6. This would be a weird setup,
    but I can't rule it out.

    It could also be something else that I can't currently imagine.

    I rather think that these are different machines.

    "whois 213.171.194.64" and "whois 2a00:1098:82::6:1" give very
    different results.

    The OP should have kept the host checking! At least, this would
    have given a clue.

    --
    Vincent Lef?vre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
    100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
    Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 16:20:02
    Andy Smith <andy@strugglers.net> wrote:
    Hello,

    On Sun, Jul 05, 2026 at 09:28:57PM +0100, Chris Green wrote:
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null

    Like quite a few people nowadays I find it more of a nusiance than a
    help.

    lolwat

    In a thread where you tell us you've been confused about which host you
    are trying to log in to, and if you had been trying a password you would
    have been typing it into someone else's server (!), you disable host key checking because "like quite a few people nowadays I find it more of a nuisance"

    Please do spread the message to all these other wrong people you know!

    Well here's one post that I found in a few seconds:-

    https://linuxvox.com/blog/ssh-on-linux-disabling-host-key-checking-for-hosts-on-local-subnet-known-hosts/

    Yes, it relates to having lots of local ssh hosts on a LAN, that's
    basically my situation except for a couple of remote systems.

    A search for "ssh disable known host check" produces a huge number of
    hits, so I'm not alone! :-)

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Vincent Lefevre@3:633/10 to All on Monday, July 06, 2026 16:30:02
    On 2026-07-06 14:54:34 +0100, Chris Green wrote:
    Well here's one post that I found in a few seconds:-

    https://linuxvox.com/blog/ssh-on-linux-disabling-host-key-checking-for-hosts-on-local-subnet-known-hosts/

    "In *trusted local networks*" but by doing a DNS resolution,
    you did *not* ensure the use of your local networks.

    Yes, it relates to having lots of local ssh hosts on a LAN, that's
    basically my situation except for a couple of remote systems.

    Things can be automatized. But...

    Also note that by default, ssh does not complain when the host key is
    not present in the known_hosts file, just when the key has apparently
    changed (which usually means something bad, unless the machine has
    been reinstalled). So one needs to be careful only for the first
    connection to some host.

    There are also some places where all hosts on the LAN are set up with
    the same host key (I don't know whether this can be a bad thing), so
    that strict host checking can easily be enabled by default.

    --
    Vincent Lef?vre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
    100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
    Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Greg Wooledge@3:633/10 to All on Monday, July 06, 2026 16:50:01
    On Mon, Jul 06, 2026 at 16:29:02 +0200, Vincent Lefevre wrote:
    On 2026-07-06 14:54:34 +0100, Chris Green wrote:
    Well here's one post that I found in a few seconds:-

    https://linuxvox.com/blog/ssh-on-linux-disabling-host-key-checking-for-hosts-on-local-subnet-known-hosts/

    "In *trusted local networks*" but by doing a DNS resolution,
    you did *not* ensure the use of your local networks.

    I'm slowly being convinced that name resolution is the real problem here.

    Chris, can you please do

    ssh -v isbd.biz

    and post the resulting output here? At the very least, show us the
    part up to and including the line that says "debug1: Connecting to ...".

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 17:00:01
    On Mon, Jul 06, 2026 at 10:41:36AM -0400, Greg Wooledge wrote:
    I'm slowly being convinced that name resolution is the real problem here.

    I agree, but in a much simpler way.

    OP has been repeatedly asked to confirm whether the IPv6 address in DNS
    is actually pointing at the same host as the IPv4 address, but has not
    yet confirmed.

    Someone (Vincent?) pointed out that the whois records for the two IP
    addresses show very different entities. Still feasible for it to be the
    same host, but looking suspicious by now. But for me, when I traceroute
    to the IPv4 address it's about 5.6ms from me, whereas the IPv6 address is
    about 0.6ms from me.

    The reverse DNS of the IPv6 address is caracal.mythic-beasts.com., which
    bears nbo relation to OP and is a well-known hosting outfit in UK.

    So my conclusion is that two two addresses are in very different parts
    of the Internet. Not 100% confirmed since one can easily introduce weird routing and fake delays, but that would require some weird scheme, so
    the most likely answer is it's simply a wrong IPv6 address.

    The reason why it always goes wrong when using host name is that Linux
    prefers to use IPv6 addresses when it has both.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Simon Hollenbach@3:633/10 to All on Monday, July 06, 2026 18:30:02
    Hi folks,

    have you seen this message from Chris aka OP?:

    On Sun, 5 Jul 2026 at 22:50, Chris Green <cl@isbd.net> wrote:

    Simon Hollenbach <ionpowered@gmail.com> wrote:
    [...]
    On Sun, 5 Jul 2026 at 21:40, Chris Green <cl@isbd.net> wrote:
    [...]
    If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for
    my local system's public key passphrase and I can log in successfully.

    However if I try 'ssh isbd.biz' I get prompted for "chris@isbd.biz's password" which doesn't exist and I can't log in.
    Your domain also has an AAAA record, could it be that ssh is trying to reach that instead of the IP you tested above?
    You should be able to test this by forcing SSH to use IPv4, using `ssh
    -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't understand what's going on, you can repeat `--verbose` or use multiple `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further.

    Brilliant! That's what was causing the oddity.

    I can fix the issue simply by adding an entry in ~/.ssh/config but I
    wanted to understand (better) what was going on.

    I think OP fixed the problem they were coming here for, it was a
    problem of SSH client preferring IPv6 and the server's daemon
    apparently not listening on the advertised address.

    You might still help OP fix his server config, but I think the intial
    question is resolved.

    Ciao,
    Simon

    On Mon, 6 Jul 2026 at 16:54, Andy Smith <andy@strugglers.net> wrote:

    On Mon, Jul 06, 2026 at 10:41:36AM -0400, Greg Wooledge wrote:
    I'm slowly being convinced that name resolution is the real problem here.

    I agree, but in a much simpler way.

    OP has been repeatedly asked to confirm whether the IPv6 address in DNS
    is actually pointing at the same host as the IPv4 address, but has not
    yet confirmed.

    Someone (Vincent?) pointed out that the whois records for the two IP addresses show very different entities. Still feasible for it to be the
    same host, but looking suspicious by now. But for me, when I traceroute
    to the IPv4 address it's about 5.6ms from me, whereas the IPv6 address is about 0.6ms from me.

    The reverse DNS of the IPv6 address is caracal.mythic-beasts.com., which bears nbo relation to OP and is a well-known hosting outfit in UK.

    So my conclusion is that two two addresses are in very different parts
    of the Internet. Not 100% confirmed since one can easily introduce weird routing and fake delays, but that would require some weird scheme, so
    the most likely answer is it's simply a wrong IPv6 address.

    The reason why it always goes wrong when using host name is that Linux prefers to use IPv6 addresses when it has both.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 19:00:02
    Hi,

    On Mon, Jul 06, 2026 at 06:28:59PM +0200, Simon Hollenbach wrote:
    have you seen this message from Chris aka OP?:

    Yes. Did you?

    On Sun, 5 Jul 2026 at 22:50, Chris Green <cl@isbd.net> wrote:
    Simon Hollenbach <ionpowered@gmail.com> wrote:
    Your domain also has an AAAA record, could it be that ssh is trying to reach that instead of the IP you tested above?
    You should be able to test this by forcing SSH to use IPv4, using `ssh
    -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't understand what's going on, you can repeat `--verbose` or use multiple `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further.

    Brilliant! That's what was causing the oddity.

    I can fix the issue simply by adding an entry in ~/.ssh/config but I
    wanted to understand (better) what was going on.

    Note that OP says that the AAAA record is what "caused the oddity" but
    does not elaborate as to *why* that is so. I later followed up to say
    that *if* that's because the AAAA record is pointing at some other
    incorrect host then yes, that would be why. It looks like that is the
    case.

    I think OP fixed the problem they were coming here for

    I don't think so, because the same AAAA record is there now as was there
    at the start of this thread. It very much looks like a totally unrelated
    host to what is at the A record.

    it was a problem of SSH client preferring IPv6 and the server's daemon apparently not listening on the advertised address.

    Incorrect. If that were the case then OP would have got a connection
    refused message. Furthermore there actually *is* something listening on
    SSH port on that IPv6 address.

    The fact that OP made the extremely unwise decision to disable host key checking, coupled with the hypothesis that the IPv6 address
    2a00:1098:82::6:1 is *not* under control of the OP, explains everything
    that the OP has experienced.

    It's unlikely this thread would even exist if OP had used sensible SSH configuration, since their SSH would warn that they were trying to
    connect to a different host.

    You might still help OP fix his server config, but I think the intial question is resolved.

    While there could be further errors in OP's setup, the existence of an incorrect AAAA record is still the biggest known problem here.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nicolas George@3:633/10 to All on Monday, July 06, 2026 19:10:01
    Andy Smith (HE12026-07-06):
    OP has been repeatedly asked to confirm whether the IPv6 address in DNS
    is actually pointing at the same host as the IPv4 address, but has not
    yet confirmed.

    Have you noticed how some OPs answer to people who suggest stupid things
    at random that only address half the symptoms exposed in the first
    place, and never the to people who lead them into an investigative
    process that will lead you to the solution with good probability?

    There is probably a psychology PhD to write on that.

    But for me, when I traceroute
    to the IPv4 address it's about 5.6ms from me, whereas the IPv6 address is about 0.6ms from me.

    Are you sure of your numbers? For a host two gigabit switches away, I am already at 0.390/0.676/0.806/0.112 ms. That a random host on the
    Internet would happen to be at 0.6 ms from you seems really unlikely to
    me.

    Not that it invalidates the rest of your diagnosis.

    Regards,

    --
    Nicolas George

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 19:30:01
    Hi,

    On Mon, Jul 06, 2026 at 07:02:38PM +0200, Nicolas George wrote:
    Are you sure of your numbers? For a host two gigabit switches away, I am already at 0.390/0.676/0.806/0.112 ms. That a random host on the
    Internet would happen to be at 0.6 ms from you seems really unlikely to
    me.

    The destination (2a00:1098:82::6:1), judging by reverse DNS and RTT
    time, is in Sovereign House datacentre (London Docklands). The host I
    traced from is in another Docklands datacentre probably less than 1 mile
    away. The IONOS VPS is a fair bit further away than that.

    $ mtr -rc 10 2a00:1098:82::6:1
    Start: 2026-07-06T17:08:10+0000
    HOST: use Loss% Snt Last Avg Best Wrst StDev
    1.|-- strugglers.ipv6.bitfolk.c 0.0% 10 0.2 0.2 0.2 0.4 0.1
    2.|-- e4a.jump.net.uk 0.0% 10 0.4 0.4 0.3 0.4 0.0
    3.|-- c4.jump.net.uk 0.0% 10 0.4 0.6 0.3 1.9 0.5
    4.|-- i1b.jump.net.uk 0.0% 10 0.4 0.4 0.3 0.6 0.1
    5.|-- router-ths-a.mythic-beast 0.0% 10 0.3 0.3 0.2 0.5 0.1
    6.|-- router-sov-c.mythic-beast 0.0% 10 0.4 0.4 0.3 0.5 0.1
    7.|-- spine-sov-20-1.mythic-bea 0.0% 10 0.7 0.6 0.4 0.7 0.1
    8.|-- leaf-sov-20-1.mythic-beas 0.0% 10 0.7 0.7 0.5 1.0 0.2
    9.|-- vds-sov-ab.mythic-beasts. 0.0% 10 0.6 0.6 0.4 0.7 0.1
    10.|-- caracal.mythic-beasts.com 0.0% 10 0.8 0.8 0.6 0.9 0.1


    $ mtr -rc 10 213.171.194.64
    Start: 2026-07-06T17:13:33+0000
    HOST: use Loss% Snt Last Avg Best Wrst StDev
    1.|-- pisang.bitfolk.com 0.0% 10 0.2 0.2 0.1 0.3 0.1
    2.|-- e4a.jump.net.uk 0.0% 10 0.3 0.3 0.2 0.4 0.1
    3.|-- c3.jump.net.uk 0.0% 10 0.3 0.3 0.3 0.4 0.1
    4.|-- i1b.jump.net.uk 0.0% 10 0.3 0.3 0.2 0.4 0.1
    5.|-- linx.bb-d.ba.slo.gb.onean 0.0% 10 1.5 1.4 1.1 1.5 0.1
    6.|-- lo-0.rc-b.ce6.wtr.gb.net. 0.0% 10 6.3 6.3 6.1 6.4 0.1
    7.|-- po1-2.nf1-bp1-l1.ce6.wtr. 0.0% 10 5.9 5.8 5.8 5.9 0.0
    8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

    The first 4 hops are still inside London - jump.net.uk is my colo
    provider so I can tell you where that 4th hop router physically is. Hop 5 is a little further away and by the "slo.gb" I'm going to guess is one of the
    big Slough datacentres. I don't know what "wtr.gb"? might be but as it's
    5ms further away I will guess it's either in the North of England, or
    Scotland.

    Anyway, the IPv4 is ~5ms more distant than the IPv6 so barring
    shenanigans they are not the same device.

    Thanks,
    Andy

    ? The full reverse DNS of that hop is lo-0.rc-b.ce6.wtr.gb.net.ionos.com.

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 21:00:01
    Nicolas George <george@nsup.org> wrote:
    Andy Smith (HE12026-07-06):
    OP has been repeatedly asked to confirm whether the IPv6 address in DNS
    is actually pointing at the same host as the IPv4 address, but has not
    yet confirmed.

    "Repeatedly"??

    But possibly not (the IPV6 address not pointing at the same system
    that is). It'll take me a while to check out because this hostname
    (isbd.biz) has had a rather troubled history. When I tried to move it
    away from TsoHost I had lots of trouble because it's a 'premium' name.
    I finally got it hosted at spaceship.com.

    However it looks as if the IPV6 address may stillÿpoint at a Mythic
    Beasts system because I did try and move the domain hosting there and
    it sort of half worked before they said they couldn't handle the
    'premium' name.

    I'll go and sort it out.

    Have you noticed how some OPs answer to people who suggest stupid things
    at random that only address half the symptoms exposed in the first
    place, and never the to people who lead them into an investigative
    process that will lead you to the solution with good probability?

    There is probably a psychology PhD to write on that.

    But for me, when I traceroute
    to the IPv4 address it's about 5.6ms from me, whereas the IPv6 address is about 0.6ms from me.

    Yes, likely because the IPV6 address appears to be a well connected
    server at Mythic Beasts whereas the IPV4 address goes to a very low
    powered VPS at FastHosts.

    Are you sure of your numbers? For a host two gigabit switches away, I am already at 0.390/0.676/0.806/0.112 ms. That a random host on the
    Internet would happen to be at 0.6 ms from you seems really unlikely to
    me.

    Not that it invalidates the rest of your diagnosis.

    Regards,

    --
    Nicolas George

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 21:00:01
    Andy Smith <andy@strugglers.net> wrote:
    Hi,

    On Mon, Jul 06, 2026 at 07:02:38PM +0200, Nicolas George wrote:
    Are you sure of your numbers? For a host two gigabit switches away, I am already at 0.390/0.676/0.806/0.112 ms. That a random host on the
    Internet would happen to be at 0.6 ms from you seems really unlikely to
    me.

    The destination (2a00:1098:82::6:1), judging by reverse DNS and RTT
    time, is in Sovereign House datacentre (London Docklands). The host I
    traced from is in another Docklands datacentre probably less than 1 mile away. The IONOS VPS is a fair bit further away than that.

    $ mtr -rc 10 2a00:1098:82::6:1
    Start: 2026-07-06T17:08:10+0000
    HOST: use Loss% Snt Last Avg Best Wrst StDev
    1.|-- strugglers.ipv6.bitfolk.c 0.0% 10 0.2 0.2 0.2 0.4 0.1
    2.|-- e4a.jump.net.uk 0.0% 10 0.4 0.4 0.3 0.4 0.0
    3.|-- c4.jump.net.uk 0.0% 10 0.4 0.6 0.3 1.9 0.5
    4.|-- i1b.jump.net.uk 0.0% 10 0.4 0.4 0.3 0.6 0.1
    5.|-- router-ths-a.mythic-beast 0.0% 10 0.3 0.3 0.2 0.5 0.1
    6.|-- router-sov-c.mythic-beast 0.0% 10 0.4 0.4 0.3 0.5 0.1
    7.|-- spine-sov-20-1.mythic-bea 0.0% 10 0.7 0.6 0.4 0.7 0.1
    8.|-- leaf-sov-20-1.mythic-beas 0.0% 10 0.7 0.7 0.5 1.0 0.2
    9.|-- vds-sov-ab.mythic-beasts. 0.0% 10 0.6 0.6 0.4 0.7 0.1
    10.|-- caracal.mythic-beasts.com 0.0% 10 0.8 0.8 0.6 0.9 0.1


    $ mtr -rc 10 213.171.194.64
    Start: 2026-07-06T17:13:33+0000
    HOST: use Loss% Snt Last Avg Best Wrst StDev
    1.|-- pisang.bitfolk.com 0.0% 10 0.2 0.2 0.1 0.3 0.1
    2.|-- e4a.jump.net.uk 0.0% 10 0.3 0.3 0.2 0.4 0.1
    3.|-- c3.jump.net.uk 0.0% 10 0.3 0.3 0.3 0.4 0.1
    4.|-- i1b.jump.net.uk 0.0% 10 0.3 0.3 0.2 0.4 0.1
    5.|-- linx.bb-d.ba.slo.gb.onean 0.0% 10 1.5 1.4 1.1 1.5 0.1
    6.|-- lo-0.rc-b.ce6.wtr.gb.net. 0.0% 10 6.3 6.3 6.1 6.4 0.1
    7.|-- po1-2.nf1-bp1-l1.ce6.wtr. 0.0% 10 5.9 5.8 5.8 5.9 0.0
    8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

    The first 4 hops are still inside London - jump.net.uk is my colo
    provider so I can tell you where that 4th hop router physically is. Hop 5 is a
    little further away and by the "slo.gb" I'm going to guess is one of the
    big Slough datacentres. I don't know what "wtr.gb"? might be but as it's
    5ms further away I will guess it's either in the North of England, or Scotland.

    Anyway, the IPv4 is ~5ms more distant than the IPv6 so barring
    shenanigans they are not the same device.

    See my earlier reply. I think the IPV6 address is plain wrong as a
    result of a failed attempt to move the domain hosting to Mythic Beasts.

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeffrey Walton@3:633/10 to All on Monday, July 06, 2026 21:10:01
    On Mon, Jul 6, 2026 at 12:20?PM Andy Smith <andy@strugglers.net> wr
    ote:

    On Sun, Jul 05, 2026 at 09:28:57PM +0100, Chris Green wrote:
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null

    Like quite a few people nowadays I find it more of a nusiance than a
    help.

    lolwat

    In a thread where you tell us you've been confused about which host you
    are trying to log in to, and if you had been trying a password you would
    have been typing it into someone else's server (!), you disable host key checking because "like quite a few people nowadays I find it more of a nuisance"

    Please do spread the message to all these other wrong people you know!

    ++. I almost looked up the reference for the precursor to StrictHostKeyChecking, but decided against it. But since you took the
    time I should, too. Here it is:

    "Perspectives: Improving SSH-style Host Authentication with Multi-Path Probing?, Dan Wendlandt, David Anderson and Adrian Perrig, Proceedi
    ngs
    of the USENIX Annual Technical Conference (USENIX ?08), June 2008,
    p.321.

    The paper can be found at <https://www.cs.cmu.edu/~dga/papers/perspectives-usenix2008/>.

    Jeff

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Monday, July 06, 2026 22:00:01
    Chris Green <cl@isbd.net> wrote:
    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.

    [snip details]

    This question has provoked quite a lot of, at times, rather heated
    discussion! I'm sorry if I provoked any of the heat but lots of
    useful information came out of it all I think.

    One thread got me looking into what the IPV6 address for isbd.biz was
    pointing at. It turns out that it wasn't pointing at the right system
    at all, I'm not sure how this happened but I'll try and explain how it probably/possibly occurred.

    Quite a few years ago I had quite a few domains hosted at TsoHost who,
    many years ago, were an excellent hosting provider. However they were
    taken over and their service and support deteriorated so I moved my
    domains away from them. I moved most of my mail hosting (and the
    associated domains) to Mythic Beasts. After a while I had got all my
    domains away from TsoHost apart from one fly in the ointment which was isbd.biz.

    The problem with isbd.biz was that it is a 'premium' name and many
    hosting providers couldn't handle it. Initially Mythic Beasts seemed
    like they could host it so I started the move to them, however it all
    went pear-shaped and they found that they couldn't host it. It stayed
    with TsoHost a little longer and then I found a US based provider
    called spaceship.com who could host the isbd.biz domain and who were a
    lot cheaper than Tsohost.

    So I moved isbd.biz to spaceship.com a year or so ago and it was all
    working OK, or so I thought. It doesn't actually have much of an
    existence, there's no web sites on isbd.biz and no significant E-Mail
    either. My only current use is as the name of a VPS on FastHosts
    which runs a DavCal calendar server.

    Having stirred the wasp's nest that was this discussion :-) I
    discovered that the domain hosting move was very much half done. The
    IPV4 address was correct, the IPV6 address for some wierd reason
    pointd at a Mythic Beasts server (maybe happened due to the failed
    move to Mythic Beasts), the MX record seemed to be OK as it was
    pointing at my mailboxes on Mythic Beasts. The DNS was still on
    TsoHost (I **think**).

    I have now, hopefully, sorted it out somewhat. I've moved the DNS to spaceship's nameservers. The VPS on FastHosts has no IPV6 address (or
    if it does I'm not using it) so I have removed the AAAA record. It
    may need some more records for DKIM and SPF but they can wait, at
    present no mail is sent from the system and very little, if any, is
    sent to isbd.biz.

    It's amazing what a little ssh quirk can unearth! :-)

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeffrey Walton@3:633/10 to All on Monday, July 06, 2026 22:30:02
    On Mon, Jul 6, 2026 at 3:50?PM Chris Green <cl@isbd.net> wrote:

    Chris Green <cl@isbd.net> wrote:
    This isn't a problem as such but I don't understand why it's happening
    and I'd like to understand.
    [...]

    Quite a few years ago I had quite a few domains hosted at TsoHost who,
    many years ago, were an excellent hosting provider. However they were
    taken over and their service and support deteriorated so I moved my
    domains away from them. I moved most of my mail hosting (and the
    associated domains) to Mythic Beasts. After a while I had got all my
    domains away from TsoHost apart from one fly in the ointment which was isbd.biz.

    The problem with isbd.biz was that it is a 'premium' name and many
    hosting providers couldn't handle it. Initially Mythic Beasts seemed
    like they could host it so I started the move to them, however it all
    went pear-shaped and they found that they couldn't host it. It stayed
    with TsoHost a little longer and then I found a US based provider
    called spaceship.com who could host the isbd.biz domain and who were a
    lot cheaper than Tsohost.

    So I moved isbd.biz to spaceship.com a year or so ago and it was all
    working OK, or so I thought. It doesn't actually have much of an
    existence, there's no web sites on isbd.biz and no significant E-Mail
    either. My only current use is as the name of a VPS on FastHosts
    which runs a DavCal calendar server.

    Related and off-topic, you should open an OpenSRS account and become a reseller. You will be the registrar, and you can basically buy
    domains at cost. No need to pay the premiums to hosting providers to
    register and renew domains.

    Becoming a reseller does not cost much. You pay a one-time fee, if I
    recall correctly. It cost me about $100 USD about 15 years ago. I
    got a full return on investment once I renewed 3 or 4 domains since
    each renewal saved me about $25.

    As the registrar, you also control the EPC codes (or EPP code or Auth
    Codes). You can generate them at will. No need to depend on others
    to transfer or sell a domain. And you can do the other things, like
    add privacy and block transfer.

    Jeff

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Monday, July 06, 2026 22:40:01
    Hi,

    On Mon, Jul 06, 2026 at 04:25:35PM -0400, Jeffrey Walton wrote:
    Related and off-topic, you should open an OpenSRS account and become a reseller. You will be the registrar, and you can basically buy
    domains at cost. No need to pay the premiums to hosting providers to register and renew domains.

    So how much is a renewal of a .biz domain as an OpenSRS reseller?

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeffrey Walton@3:633/10 to All on Tuesday, July 07, 2026 01:50:01
    On Mon, Jul 6, 2026 at 7:40?PM Andy Smith <andy@strugglers.net> wro
    te:

    On Mon, Jul 06, 2026 at 04:25:35PM -0400, Jeffrey Walton wrote:
    Related and off-topic, you should open an OpenSRS account and become a reseller. You will be the registrar, and you can basically buy
    domains at cost. No need to pay the premiums to hosting providers to register and renew domains.

    So how much is a renewal of a .biz domain as an OpenSRS reseller?

    It looks like a *.biz domain is $23 USD per year. Confer, <https://opensrs.com/tld-price-changes/>.

    (And thanks for the subject: change. I was too lazy to do it.)

    Jeff

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Tuesday, July 07, 2026 16:20:01
    Hi,

    On Mon, Jul 06, 2026 at 07:00:02PM -0600, Sean Reifschneider wrote:
    CloudFlare is doing domain registrations at cost, which is hard to
    beat. $18.20

    They require you to host your DNS with them. In my opinion Cloudflare
    are a data mining company pretending to be a network services company.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Tuesday, July 07, 2026 16:30:01
    Hi,

    On Mon, Jul 06, 2026 at 07:45:23PM -0400, Jeffrey Walton wrote:
    It looks like a *.biz domain is $23 USD per year. Confer, <https://opensrs.com/tld-price-changes/>.

    Looks like .biz domains are renewed at $19.05 at prokbun.com with no
    need to enter into any reseller relationship.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Christian Groessler@3:633/10 to All on Wednesday, July 08, 2026 01:00:01
    On 7/6/26 4:29 PM, Vincent Lefevre wrote:
    On 2026-07-06 14:54:34 +0100, Chris Green wrote:
    Well here's one post that I found in a few seconds:-

    https://linuxvox.com/blog/ssh-on-linux-disabling-host-key-checking-for-hosts-on-local-subnet-known-hosts/

    "In *trusted local networks*" but by doing a DNS resolution,
    you did *not* ensure the use of your local networks.


    In "trusted local networks" one could use telnet and forget about ssh overhead...

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Wednesday, July 08, 2026 02:30:01
    Hello,

    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote:
    In "trusted local networks" one could use telnet and forget about ssh overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login. The trivial overhead of encryption
    and initial key exchange won't be at all noticeable in an interactive
    terminal session so why would you ever use antiquated and
    poorly-maintained software like telnet? ssh is right there and works
    fine.

    Even when it comes to bulk data transfer, SSH is not really slowed down
    that much by encryption and key exchange. I have no problem doing
    500MB/s from an nvme, through SSH over the local network to another
    nvme. The bottleneck isn't the CPU unless we are talking very weak
    systems. The bottleneck is down to the fact that SSH isn't a dedicated
    file transfer tool and just uses a single TCP stream with conservative
    window scaling. This still works quite well on reliable, low latency
    links. TCP really falls apart on high latency links with even a tiny
    amount of loss, but local networks aren't usually like that.

    But even if you DID find encryption overhead to be an issue, you
    wouldn't try to shove massive amounts of data though telnet, you would
    just us something like nc! It's packaged in Debian and installing it on
    both ends is far more sane than running telnetd on one end and telnet
    client on the other!

    There is almost no scenario in which running telnetd makes sense, even
    on an isolated network where every host is on your desk, except perhaps nostalgia.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    "I am the permanent milk monitor of all hobbies!" ? Simon Quinlank

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Wednesday, July 08, 2026 07:30:02
    scp for transfer or rsync may be...

    On mer., 2026-07-08 at 00:24 +0000, Andy Smith wrote:
    Hello,

    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote:
    In "trusted local networks" one could use telnet and forget about
    ssh
    overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login. The trivial overhead of
    encryption
    and initial key exchange won't be at all noticeable in an interactive terminal session so why would you ever use antiquated and
    poorly-maintained software like telnet? ssh is right there and works
    fine.

    Even when it comes to bulk data transfer, SSH is not really slowed
    down
    that much by encryption and key exchange.ÿ I have no problem doing
    500MB/s from an nvme, through SSH over the local network to another
    nvme. The bottleneck isn't the CPU unless we are talking very weak
    systems. The bottleneck is down to the fact that SSH isn't a
    dedicated
    file transfer tool and just uses a single TCP stream with
    conservative
    window scaling. This still works quite well on reliable, low latency
    links. TCP really falls apart on high latency links with even a tiny
    amount of loss, but local networks aren't usually like that.

    But even if you DID find encryption overhead to be an issue, you
    wouldn't try to shove massive amounts of data though telnet, you
    would
    just us something like nc! It's packaged in Debian and installing it
    on
    both ends is far more sane than running telnetd on one end and telnet
    client on the other!

    There is almost no scenario in which running telnetd makes sense,
    even
    on an isolated network where every host is on your desk, except
    perhaps
    nostalgia.

    Thanks,
    Andy

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From jean-christophe@3:633/10 to All on Wednesday, July 08, 2026 07:30:03
    there are fusefs under linux if you like do a persistent link

    On mer., 2026-07-08 at 07:24 +0200, jean-christophe wrote:
    scp for transfer or rsync may be...

    On mer., 2026-07-08 at 00:24 +0000, Andy Smith wrote:
    Hello,

    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler
    wrote:
    In "trusted local networks" one could use telnet and forget about
    ssh
    overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login. The trivial overhead of
    encryption
    and initial key exchange won't be at all noticeable in an
    interactive
    terminal session so why would you ever use antiquated and
    poorly-maintained software like telnet? ssh is right there and
    works
    fine.

    Even when it comes to bulk data transfer, SSH is not really slowed
    down
    that much by encryption and key exchange.ÿ I have no problem doing
    500MB/s from an nvme, through SSH over the local network to another
    nvme. The bottleneck isn't the CPU unless we are talking very weak
    systems. The bottleneck is down to the fact that SSH isn't a
    dedicated
    file transfer tool and just uses a single TCP stream with
    conservative
    window scaling. This still works quite well on reliable, low
    latency
    links. TCP really falls apart on high latency links with even a
    tiny
    amount of loss, but local networks aren't usually like that.

    But even if you DID find encryption overhead to be an issue, you
    wouldn't try to shove massive amounts of data though telnet, you
    would
    just us something like nc! It's packaged in Debian and installing
    it
    on
    both ends is far more sane than running telnetd on one end and
    telnet
    client on the other!

    There is almost no scenario in which running telnetd makes sense,
    even
    on an isolated network where every host is on your desk, except
    perhaps
    nostalgia.

    Thanks,
    Andy

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Christian Groessler@3:633/10 to All on Wednesday, July 08, 2026 12:10:01
    Hi,

    On 7/8/26 2:24 AM, Andy Smith wrote:
    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote:
    In "trusted local networks" one could use telnet and forget about ssh
    overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login.


    I wasn't aware that it's about file transfer. (ftp to the rescue? :-))

    I have some "older" systems which cannot handle the ssh/encryption
    overhead. (Older ssh versions allowed to set encryption to "none" but
    this is somehow gone.)

    Think about 68k, VAX, Z80, 6502 machines. No way for the latter two to
    support ssh. And these are machines sitting in my network which I want
    to access to/from remote.

    And, after all, if you insist on ssh on your "trusted local network", is
    it then really "trusted"?

    regards,
    chris

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From tomas@3:633/10 to All on Wednesday, July 08, 2026 12:50:02
    On Wed, Jul 08, 2026 at 12:05:52PM +0200, Christian Groessler wrote:
    Hi,

    On 7/8/26 2:24 AM, Andy Smith wrote:
    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote:
    In "trusted local networks" one could use telnet and forget about ssh overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login.


    I wasn't aware that it's about file transfer. (ftp to the rescue? :-))
    The older among us know to use sz/rz for that (still in the package
    lrzsz). Designed to transfer binary files over channels requiring an
    escape layer (plus some error correction on top).
    But yes, nowadays I'd consider telnet mostly dead. The last legit
    application for a long time, using the client to interact with clear
    text protocol servers (http, smtp, you name them) is pretty well
    served by "socat -", which uses readline to edit each line before
    sending it.
    Cheers
    --
    t


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Green@3:633/10 to All on Wednesday, July 08, 2026 15:20:01
    tomas@tuxteam.de wrote:
    [-- text/plain, size 0.9K, charset utf-8, 28 lines, encoding quoted-printable --]

    On Wed, Jul 08, 2026 at 12:05:52PM +0200, Christian Groessler wrote:
    Hi,

    On 7/8/26 2:24 AM, Andy Smith wrote:
    On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote:
    In "trusted local networks" one could use telnet and forget about ssh overhead...

    I don't really follow the logic. telnet is not designed for file
    transfer but for interactive login.


    I wasn't aware that it's about file transfer. (ftp to the rescue? :-))

    The older among us know to use sz/rz for that (still in the package
    lrzsz). Designed to transfer binary files over channels requiring an
    escape layer (plus some error correction on top).

    But yes, nowadays I'd consider telnet mostly dead. The last legit
    application for a long time, using the client to interact with clear
    text protocol servers (http, smtp, you name them) is pretty well
    served by "socat -", which uses readline to edit each line before
    sending it.

    I occasionally use telnet to test if a port has a server listening on
    it. I know I could use nmap (or other things) but the telnet syntax
    is burnt into my brain and is very simple:-

    telnet <server> <port number>

    Some server daemons even tell you who they are:-

    chris$ telnet q957 22
    Trying 192.168.1.5...
    Connected to q957.
    Escape character is '^]'.
    SSH-2.0-OpenSSH_10.0p2 Debian-7+deb13u4

    --
    Chris Green
    ú

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nicolas George@3:633/10 to All on Wednesday, July 08, 2026 15:20:01
    Chris Green (HE12026-07-08):
    telnet <server> <port number>

    Better use netcat / nc for that: telnet has an escaping character and
    does tty control, that could interfere with your interaction with the
    server.

    And if you can change the syntax a little:

    socat - tcp:server:port

    is extremely more powerful.

    Regards,

    --
    Nicolas George

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Stefan Monnier@3:633/10 to All on Wednesday, July 08, 2026 18:30:01
    Think about 68k, VAX, Z80, 6502 machines. No way for the latter two to support ssh. And these are machines sitting in my network which I want
    to access to/from remote.

    I think it's perfectly normal if remote access to retro 8bit computers
    requires special efforts. AFAICT, for the C64, all the support for
    networking happens by attaching another computer (called "network card")
    to your C64 and the two computers talk over a serial connection.
    IIUC it's the network card which takes care of the TCP/IP protocol, so
    I'd disagree with the "no way" above: the network card could be improved
    to add support for the SSH protocol.
    The network card is already a more beefy computer than the C64
    itself anyway.


    === Stefan

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Wednesday, July 08, 2026 19:00:01
    Hi,

    On Wed, Jul 08, 2026 at 01:57:34PM +0100, Chris Green wrote:
    I occasionally use telnet to test if a port has a server listening on
    it.

    Me too, because of deeply ingrained habits, but I know they are bad
    habits. ? I've started banning install of telnet client to force myself
    out of it.

    The main reason it's bad is that telnet client is designed as an
    interactive login thing and is doing terminal stuff, which you don't
    really want when connecting to random TCP services.

    You can go to some effort to disable those things, but the job should
    really be done with nc or socat or similar.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Stefan Monnier@3:633/10 to All on Wednesday, July 08, 2026 19:50:01
    You can go to some effort to disable those things, but the job should
    really be done with nc or socat or similar.

    FWIW, I tried `nc` for that (because I like `nc` for actual transfers)
    but didn't like it because it doesn't give enough feedback. I just
    tried `socat` and it similarly just "sits there" sometimes, at which
    point I have to use my head to try and guess if it means it successfully connected but the other end doesn't send anything, or if it means it's
    still waiting for the connection to be established, etc...

    I think what I'd want is a UI a bit more like `ping`: I give it
    a hostname and a port, and it tells me when it starts to try and
    establish the connection (showing the IP address used), and then telling
    me whether the connection was successful or not (even better if it can
    show me the first few bytes received from the server, if any, but it
    should disconnect automatically) or whether it timedout.

    Any recommendation?


    === Stefan

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Roy J. Tellason, Sr.@3:633/10 to All on Wednesday, July 08, 2026 20:00:01
    On Wednesday 08 July 2026 06:05:52 am Christian Groessler wrote:
    Think about 68k, VAX, Z80, 6502 machines. No way for the latter two to support ssh. And these are machines sitting in my network which I want
    to access to/from remote.


    You have z80 and 6502 machines on your network? How did you manage to do t hat?

    --
    Member of the toughest, meanest, deadliest, most unrelenting -- and
    ablest -- form of life in this section of space, ÿa critter that can
    be killed but can't be tamed. ÿ--Robert A. Heinlein, "The Puppet Maste
    rs"
    -
    Information is more dangerous than cannon to a society ruled by lies. --Jam
    es
    M Dakin

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nicolas George@3:633/10 to All on Wednesday, July 08, 2026 20:10:02
    Stefan Monnier (HE12026-07-08):
    FWIW, I tried `nc` for that (because I like `nc` for actual transfers)
    but didn't like it because it doesn't give enough feedback. I just
    tried `socat` and it similarly just "sits there" sometimes, at which
    point I have to use my head to try and guess if it means it successfully connected but the other end doesn't send anything, or if it means it's
    still waiting for the connection to be established, etc...

    Could it be that `socat -dd` is more to your liking?

    Regards,

    --
    Nicolas George

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Andy Smith@3:633/10 to All on Wednesday, July 08, 2026 20:10:02
    Hi,

    On Wed, Jul 08, 2026 at 01:47:36PM -0400, Stefan Monnier wrote:
    FWIW, I tried `nc` for that (because I like `nc` for actual transfers)
    but didn't like it because it doesn't give enough feedback. I just
    tried `socat` and it similarly just "sits there" sometimes, at which
    point I have to use my head to try and guess if it means it successfully connected but the other end doesn't send anything, or if it means it's
    still waiting for the connection to be established, etc...

    I've never really had a problem with "nc -zv example.com 25" or
    whatever. Except for remembering to use it. ?

    Some text-based protocols don't send any banner unless you send them
    something first, so then I'd have to omit the -z.

    I think what I'd want is a UI a bit more like `ping`: I give it
    a hostname and a port, and it tells me when it starts to try and
    establish the connection (showing the IP address used), and then telling
    me whether the connection was successful or not (even better if it can
    show me the first few bytes received from the server, if any, but it
    should disconnect automatically) or whether it timedout.

    Any recommendation?

    You can put a timeout on nc, like:

    $ nc -w 1 -v mail.bitfolk.com 25
    Connection to mail.bitfolk.com (85.119.80.223) 25 port [tcp/smtp] succeeded! 220 mail.bitfolk.com ESMTP Exim v4.something Wed, 08 Jul 2026 17:56:31 +0000

    (it closed the connection by itself)

    but again, sometimes services won't say anything unless you talk first,
    so you'd get 1 second of nothing.

    A traceroute using TCP is also sometimes useful to find *where* the
    packets die, in case of possible firewalling.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    <Ging> i stopped taking my medication long ago. the ironey is it was for
    social anxioty disorder and now i daren't go back to the doctor to get
    another perscription

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Greg Wooledge@3:633/10 to All on Wednesday, July 08, 2026 20:30:03
    Someone in this thread mentioned using "socat - tcp:host:port" as a
    replacement for "telnet host port" for manually testing plaintext
    services.

    I just tried this, and learned that the two are not equivalent.
    qpsmtpd is quite insistent that all of its input lines be terminated
    by CR-LF, not by LF.

    ===============================================================
    hobbit:~$ socat - tcp:localhost:25
    220 greg.wooledge.org ESMTP qpsmtpd 1.00 ready; send us your mail, but not your spam.
    HELO WORLD
    250 greg.wooledge.org Hi localhost [127.0.0.1]; I am so happy to meet you.
    MAIL FROM:<greg@wooledge.org>
    250 <greg@wooledge.org>, sender OK - how exciting to get mail from you!
    RCPT TO:<greg@wooledge.org>
    250 <greg@wooledge.org>, recipient ok
    DATA
    354 go ahead
    From: Greg
    To: Greg
    Subject: hi

    hi
    .
    421 See http://smtpd.develooper.com/barelf.html ===============================================================

    telnet does not have that problem.

    So, I searched through the manual a bit more, and it turns out there's
    an option for that:

    ===============================================================
    hobbit:~$ socat - tcp:localhost:25,crnl
    220 greg.wooledge.org ESMTP qpsmtpd 1.00 ready; send us your mail, but not your spam.
    HELO WORLD
    250 greg.wooledge.org Hi localhost [127.0.0.1]; I am so happy to meet you.
    MAIL FROM:<greg@wooledge.org>
    250 <greg@wooledge.org>, sender OK - how exciting to get mail from you!
    RCPT TO:<greg@wooledge.org>
    250 <greg@wooledge.org>, recipient ok
    DATA
    354 go ahead
    From: Greg
    To: Greg
    Subject: hi
    Date: Wed, 08 Jul 2026 13:47:36 -0400

    hi
    .
    250 Queued! 1783534744 qp 143613 <> ===============================================================

    Anyone looking to replace telnet with socat for this purpose will probably
    need to use that option, on some or all services.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From tomas@3:633/10 to All on Wednesday, July 08, 2026 22:50:02
    On Wed, Jul 08, 2026 at 02:24:54PM -0400, Greg Wooledge wrote:
    Someone in this thread mentioned using "socat - tcp:host:port" as a replacement for "telnet host port" for manually testing plaintext
    services.

    I just tried this, and learned that the two are not equivalent.
    qpsmtpd is quite insistent that all of its input lines be terminated
    by CR-LF, not by LF.
    [...]
    So, I searched through the manual a bit more, and it turns out there's
    an option for that:

    ===============================================================
    hobbit:~$ socat - tcp:localhost:25,crnl
    [...]
    Heh. See my other post. Great minds... read the docs :-)
    Cheers
    --
    t


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From tomas@3:633/10 to All on Wednesday, July 08, 2026 22:50:02
    On Wed, Jul 08, 2026 at 03:15:26PM +0200, Nicolas George wrote:
    Chris Green (HE12026-07-08):
    telnet <server> <port number>

    Better use netcat / nc for that: telnet has an escaping character and
    does tty control, that could interfere with your interaction with the
    server.

    And if you can change the syntax a little:

    socat - tcp:server:port

    is extremely more powerful.
    Yesbut.
    If you want to have the equivalent to telnet, you have to tell socat
    to convert newlines to CR + LF, like so:
    tomas@caliban:~$ socat - TCP4:www.tuxteam.de:80,crnl
    GET / HTTP/1.0
    HTTP/1.0 403 Forbidden
    Content-Type: text/html
    Content-Length: 341
    Connection: close
    Date: Wed, 08 Jul 2026 20:38:26 GMT
    Server: lighttpd/1.4.59
    ...
    (Note the ",crnl" option)
    (Otherwise I get a "400 Bad Request" in my case: the web server wants
    CR + LF terminated lines, as it should the "403 Forbidden" is the right response)
    So still telnet is slightly more convenient. No question that socat
    is more powerful, in this case it also can do TLS and things).
    Cheers
    --
    t


    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Max Nikulin@3:633/10 to All on Thursday, July 09, 2026 05:20:01
    Those, who are interested in telnet niche and availability of
    replacement tools (e.g. busybox nc), may have a look into the oss-security/bug-inetutils thread "Telnetd Vulnerability Report". A
    random message from it: <https://www.openwall.com/lists/oss-security/2026/02/26/4>

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Anssi Saari@3:633/10 to All on Thursday, July 09, 2026 13:00:01
    Stefan Monnier <monnier@iro.umontreal.ca> writes:

    AFAICT, for the C64, all the support for networking happens by
    attaching another computer (called "network card") to your C64 and the
    two computers talk over a serial connection.

    No. For sure you can do that serial to ethernet thing but there are real network interfaces and TCP/IP code for the C64. I actually meant to buy
    an rrnet card but never got around to it before it went out of
    production. Looks like they're available again but these days, emulators
    are enough for me.

    --- PyGate Linux v1.5.18
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)