unix ssh help

After some digging I found that doing
sshxx@x.y.z.z (ip number not name)
FROM my indigo host to any other box in the local network takes 11 secs to get the password prompt.
It is about the same time for ALL destinations ( other mac, raspberry, AND to itself "ssh userid@127.0.0.1" ) ..)
the mac runs at < 5% load, its a mac pro 2012 w 10.13.6 = sierra
Also did a reboot , no change and pointers on the web were related to dns and avahi, none of that applies here - I believe


Fast:
After successful login everything is fine.. = very fast,
ping in both directions is < 0.3 msecs
Doing an ssh from a virtual box running on that indigo mac to the mac itself is very fast (2 different ip numbers)
Reverse ( ssh to the indigo server) is very fast < 1 sec.

Any suggestions?

Karl

What happens when you use the mDNS name (machine.local)?

Do you have a local DNS server on your LAN? What DNS servers is the Indigo server using? And do you have multiple network interfaces active on the Indigo machine?

1. dns : 8.8.8.8 and 192.168.1.1, no other local server

2. ssh uid@machine.local stopped after 3 minutes

3. changed dns to 192.168.1.1 only
no change


and with ssh uid@127.0.0.1 > 10Secs, that should not involve anything external the machine



switches off indigo, postgres, virtual box, ... load < 0.5%.. same results

the ifconfig output, if that gives any hint ..

Code: Select all

ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
   options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
   inet 127.0.0.1 netmask 0xff000000
   inet6 ::1 prefixlen 128
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
   nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
UHC26: flags=0<> mtu 0
UHC61: flags=0<> mtu 0
UHC93: flags=0<> mtu 0
EHC250: flags=0<> mtu 0
UHC58: flags=0<> mtu 0
UHC29: flags=0<> mtu 0
UHC90: flags=0<> mtu 0
XHC0: flags=0<> mtu 0
EHC253: flags=0<> mtu 0
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
   lladdr 70:cd:60:ff:fe:9a:4d:b0
   nd6 options=201<PERFORMNUD,DAD>
   media: autoselect <full-duplex>
   status: inactive
en2: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
   ether a8:fa:d8:8d:c5:6c
   nd6 options=201<PERFORMNUD,DAD>
   media: autoselect (<unknown type>)
   status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
   ether 0a:fa:d8:8d:c5:6c
   media: autoselect
   status: inactive
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
   options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
   ether 40:6c:8f:bc:19:ed
   inet6 fe80::c5:50cb:1cc0:75a2%en0 prefixlen 64 secured scopeid 0x10
   inet 192.168.1.xx netmask 0xffffff00 broadcast 192.168.1.255
   nd6 options=201<PERFORMNUD,DAD>
   media: autoselect (1000baseT <full-duplex,flow-control>)
   status: active


again any advice is welcome ..

Karl

Did you edit that en0 entry? Because 'inet 192.168.1.xx' is not valid.

Have you rebooted your router lately?

Try running 'arp -an' in Terminal, and see if it gives entries for the devices you're trying to connect to?

fixed:

cd ~/.ssh
rm *

removed files:
authorized_keys id_rsa id_rsa.pub known_hosts

I got to it by doing ssh -v ....
there you cans see all the ways it tries to authenticate .. and the timeouts
.... MANY lines ..

Karl

ps and thanks for listening

i masked my ip number in 'inet 192.168.1.xx' ..

Ah. Should have thought of the ssh keys.