On Mon, Jan 07, 2008 at 12:12:21AM +0100, Frans Pop wrote:
However, the fact remains that _we_ have so far not been able to reproduce
the issue. As I've said earlier, I've had an SSH install sitting unused for
over 4 hours without the connection being lost, with basically default SSH
Processing commands for [EMAIL PROTECTED]:
reassign 458154 installation-guide
Bug#458154: [NSLU2] ssh connection should not time out
Bug reassigned from package `network-console' to `installation-guide'.
retitle 458154 Document how to avoid dropped network-console connections
Bug#458154:
On Mon, Jan 07, 2008 at 02:58:11PM +0100, Frans Pop wrote:
reassign 458154 installation-guide
retitle 458154 Document how to avoid dropped network-console connections
thanks
On Monday 07 January 2008, Colin Watson wrote:
I agree that documenting this is the best approach.
Thanks for the
Frans Pop [EMAIL PROTECTED] writes:
reassign 458154 installation-guide
retitle 458154 Document how to avoid dropped network-console connections
thanks
On Monday 07 January 2008, Colin Watson wrote:
I agree that documenting this is the best approach.
Thanks for the info Colin.
Would the
On Mon, Jan 07, 2008 at 02:58:11PM +0100, Frans Pop wrote:
On Monday 07 January 2008, Colin Watson wrote:
I agree that documenting this is the best approach.
Thanks for the info Colin.
Would the following text be OK for the installation guide (to be added as a
note in the
On Monday 07 January 2008, Wouter Verhelst wrote:
Would the following text be OK for the installation guide (to be added
as a note in the network-console section)?
snip
The commandssh/command server in the installer uses a default
configuration that does not have a timeout set.
Colin Watson wrote:
On Mon, Jan 07, 2008 at 12:12:21AM +0100, Frans Pop wrote:
However, the fact remains that _we_ have so far not been able to reproduce
the issue. As I've said earlier, I've had an SSH install sitting unused for
over 4 hours without the connection being lost, with
Frans Pop [EMAIL PROTECTED] writes:
The commandssh/command 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 mdash; depending on
Frans Pop wrote:
So the question still is _why_ ssh drops the connection in your case.
Some crappy routers and firewalls do this to TCP connections that pass
through them.
Also, the solution you propose is on the _client_ side, so is not something
we can fix in the installer. The only thing
Processing commands for [EMAIL PROTECTED]:
tags 458154 pending
Bug#458154: Document how to avoid dropped network-console connections
Tags were: moreinfo
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 458154 pending
thanks
On Monday 07 January 2008, Otavio Salvador wrote:
I think that the text talking about NAT could be used in place of the
depending on your local network setup like one common case where
this may happen is when there is some form of Network Address
Translation (NAT)
retitle 458154 [NSLU2] ssh connection should not time out
tags 458154 + moreinfo
thanks
On Friday 04 January 2008, G. Del Merritt wrote:
Please note: I was not able to recover gracefully from the timeout.
That is expected. As the installation process itself runs almost entirely in
memory and
Processing commands for [EMAIL PROTECTED]:
retitle 458154 [NSLU2] ssh connection should not time out
Bug#458154: network-console: long time-out time during install
Changed Bug title to `[NSLU2] ssh connection should not time out' from
`network-console: long time-out time during install'.
tags
appropriate: during an
install, the ssh connection should not time out.
tags 458154 -unreproducible
Bug#458154: network-console: long time-out time during install
Tags were: unreproducible
Tags removed: unreproducible
No, this was completely reproducible. It happened to me - identically
#Op 02-01-2008 om 02:17 schreef Rick Thomas:
#
# Maybe this could be set for installations? It's not a good idea to set it
# for the installed config file, for just the kind of security reasons Del
# alludes to above. But it could save some long-running installations on
# difficult to access
time-out time during install
Bug#458154: [NSLU2] ssh connection should not time out
Changed Bug title to `network-console: long time-out time during install' from
`[NSLU2] ssh connection should not time out'.
tags 458154 -unreproducible
Bug#458154: network-console: long time-out time during install
16 matches
Mail list logo
