Skip to end of metadata
Go to start of metadata

In case your connection hangs have a look at the connections that are still active on your hung SSH session by typing ~# in your hung SSH terminal

[centos@foreman ~]$ ps -ef
~#
The following connections are open:
  #0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1)


openssh escape sequences:

Supported escape sequences:
  ~.  - terminate connection (and any multiplexed sessions)
  ~B  - send a BREAK to the remote system
  ~C  - open a command line
  ~R  - Request rekey (SSH protocol 2 only)
  ~^Z - suspend ssh
  ~#  - list forwarded connections
  ~&  - background ssh (when waiting for connections to terminate)
  ~?  - this message
  ~~  - send the escape character by typing it twice
(Note that escapes are only recognized immediately after newline.)


MTU mismatch could be one of the reasons. Cloud instances MTU is set to 1450 to compensate the VXLAN overhead if jumbo frames are not enabled.

For tenant with DHCP disabled in a cloud, the interface should be configured something like:


cat /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
BOOTPROTO=static
NM_CONTROLLED=no
NAME=eth0
DEVICE=eth0
ONBOOT=yes
MTU=1450
IPADDR=10.52.0.13
NETMASK=255.255.255.0
GATEWAY=10.52.0.1


  • No labels