[SOLVED] ssh and shell slow

[jeejee]

When I connect to ssh or shell and type stuff it seems to have big delay or lag.

 

[Chris]

Hi,
how are you connected to the PVE host? Are you working remote and/or trough a VPN? It might be that your latency is high, try to check via ping <hostname-or-ip> -c 100

 

[jeejee]

Im hosting it on other pc on same network but im trying to ping it sometimes it pings and sometimes it disconnects.

Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.

 

[Chris]

Im hosting it on other pc on same network but im trying to ping it sometimes it pings and sometimes it disconnects.

Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Request timed out.

In that case you have a network issue. Check hardware such as cables, switches ecc as well as messages in the journal which might be related to driver issues or the like. Are you using Wifi? If so, try to connect via cable to see if this solves you instabilities.

 

[jeejee]

Im using ethernet cable to connect to ethernet and I see pveproxy detected empty handle if that means something on journal.

 

[B.Otto]

Hmm, bad network configuration? Maybe a duplicate IP in your network or faulty routing (different routes for the response packets)?

 

[jeejee]

I change the /etc/network/interfaces address from 192.168.1.2 to 192.168.1.5 and seems to work now and from my modem settings chose to reserve that private ip to that device. It seems to work fine now.

 

[Chris]

I change the /etc/network/interfaces address from 192.168.1.2 to 192.168.1.5 and seems to work now and from my modem settings chose to reserve that private ip to that device. It seems to work fine now.

Don't forget to also change the IP in /etc/hosts in order to avoid issues in the future.

If this is soved, please mark the thread as solved for others to find solutions more easily, thx.

 

[Maximiliano]

Hello, I am glad you figured out your issue. Could you please mark it as solved? Also could you please share the contents of /etc/network/interfaces and /etc/hosts? The underlying issue might still be present.