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?
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.
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.
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.
'host isbd.biz' returns the correct IP address for isbd.biz so whyDo you have some custom ssh client config on the machines connecting
does ssh not work using the name rather than the IP address?
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?
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.
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:That does not make sense (to me). Isn't that like saying you connect
I have a VPS called isbd.biz and I access it using ssh. My userYour domain also has an AAAA record, could it be that ssh is trying to
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.
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.
to one host using IPv4, and another host using IPv6, under the same
DNS name. Why would someone do that???
Jeff'host isbd.biz' returns the correct IP address for isbd.biz so whyDo you have some custom ssh client config on the machines connecting
does ssh not work using the name rather than the IP address?
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?
[-- 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
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?
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.
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.
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.
Alexander V. Makartsev<avbetev@gmail.com> wrote:
[-- text/plain, size 1.3K, charset UTF-8, 43 lines, encoding 8bit --]But that's all default settings. Sites work without entries in
On 7/6/26 00:19, Chris Green wrote:
...Check your ssh client config file (should be at /home/chris/.ssh/config)
'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?
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
~/.ssh/config if the configuration is as you've shown above.
ÿ
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.
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.
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'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.
Port xxxxNot relevant for the OP, since it was working when using the IP (v4)
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
you need to
ssh-copy-id -i ~/.ssh/keyname user@host
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
Like quite a few people nowadays I find it more of a nusiance than a
help.
the issue is caused by isbd.biz having an IPV6 address as well as an
IPV4 one.
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.
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.
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.
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.
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
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:
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.
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.
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.
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
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.
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!
This isn't a problem as such but I don't understand why it's happening
and I'd like to understand.
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.
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?
CloudFlare is doing domain registrations at cost, which is hard to
beat. $18.20
It looks like a *.biz domain is $23 USD per year. Confer, <https://opensrs.com/tld-price-changes/>.
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...
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
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
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.
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
[-- 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.
telnet <server> <port number>
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 occasionally use telnet to test if a port has a server listening on
it.
You can go to some effort to disable those things, but the job should
really be done with nc or socat or similar.
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.
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...
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?
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
Chris Green (HE12026-07-08):Yesbut.
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.
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.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:21:22 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |