From 45949ced6ddfcc20baa408b5ecfc79515c7493b1 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 7 Jan 2008 21:25:15 +0000 Subject: network-console: - add information about dropped connections and how to avoid that (thanks to G. Del Merritt for raising the issue) - add footnote with command to remove a host from the known_hosts file --- en/using-d-i/modules/network-console.xml | 35 +++++++++++++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) (limited to 'en/using-d-i/modules') diff --git a/en/using-d-i/modules/network-console.xml b/en/using-d-i/modules/network-console.xml index 9d0bff67c..a16b0c489 100644 --- a/en/using-d-i/modules/network-console.xml +++ b/en/using-d-i/modules/network-console.xml @@ -71,12 +71,45 @@ you will have to confirm that it is correct. +The ssh server in the installer uses a default +configuration that does not send keep-alive packets. In principle, +a connection to the system being installed should be kept open +indefinitely. However, in some situations — depending on your +local network setup — the connection may be lost after some +period of inactivity. One common case where this can happen is when +there is some form of Network Address Translation (NAT) somewhere +between the client and the system being installed. Depending on at +which point of the installation the connection was lost, you may or +may not be able to resume the installation after reconnecting. + + + +You may be able to avoid the connection being dropped by adding the option +-o ServerAliveInterval=value +when starting the ssh connection, or by adding that +option in your ssh configuration file. Note however +that in some cases adding this option may also cause +a connection to be dropped (for example if keep-alive packets are sent +during a brief network outage, from which ssh would +otherwise have recovered), so it should only be used when needed. + + + + + If you install several computers in turn and they happen to have the same IP address or hostname, ssh will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from -~/.ssh/known_hosts and try again. +~/.ssh/known_hosts + + +The following command will remove an existing entry for a host: +ssh-keygen -R <hostname|IP address>. + + + and try again. -- cgit v1.2.3