<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Disable SSH timeouts</title>
	<atom:link href="http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/feed/" rel="self" type="application/rss+xml" />
	<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/</link>
	<description>Words of wisdom from a server administrator</description>
	<lastBuildDate>Wed, 16 May 2012 12:56:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: todd kaufmann</title>
		<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15746</link>
		<dc:creator>todd kaufmann</dc:creator>
		<pubDate>Fri, 15 Jan 2010 22:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15746</guid>
		<description>I think you only want keep-alive set iff you have network address translations that expire in a short time (like an hour), which many firewalls will do.

Otherwise, WITHOUT keepalive, I&#039;ve gone to work with my laptop, come back to my home network, hit enter and have my ssh connection still be there.  With keepalive on, it will die as soon as it tries to send a packet and the network isn&#039;t there (like as soon as you bring it out of standby/hibernate and the time expires and the network connection isn&#039;t up yet).

If you are ssh-ing through a VPN tunnel you should NOT use this.  If the VPN goes down, your ssh connection will die when a keepalive packet is sent.  Otherwise, it can be down indefinitely, then brought back and have ssh be okay.

If your firewall expires idle connections, then go ahead and use.  Otherwise, it will just ensure that your connection dies sooner.


In either case, be sure to run screen on the remote server--then you can resume your login connection from anywhere and not worry about it.</description>
		<content:encoded><![CDATA[<p>I think you only want keep-alive set iff you have network address translations that expire in a short time (like an hour), which many firewalls will do.</p>
<p>Otherwise, WITHOUT keepalive, I've gone to work with my laptop, come back to my home network, hit enter and have my ssh connection still be there.  With keepalive on, it will die as soon as it tries to send a packet and the network isn't there (like as soon as you bring it out of standby/hibernate and the time expires and the network connection isn't up yet).</p>
<p>If you are ssh-ing through a VPN tunnel you should NOT use this.  If the VPN goes down, your ssh connection will die when a keepalive packet is sent.  Otherwise, it can be down indefinitely, then brought back and have ssh be okay.</p>
<p>If your firewall expires idle connections, then go ahead and use.  Otherwise, it will just ensure that your connection dies sooner.</p>
<p>In either case, be sure to run screen on the remote server--then you can resume your login connection from anywhere and not worry about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian R. Hickey</title>
		<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15743</link>
		<dc:creator>Brian R. Hickey</dc:creator>
		<pubDate>Thu, 14 Jan 2010 14:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15743</guid>
		<description>It makes me crazy when things like this aren&#039;t included in the config files... at least commented out.  Thanks for the info.</description>
		<content:encoded><![CDATA[<p>It makes me crazy when things like this aren't included in the config files... at least commented out.  Thanks for the info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15652</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 18 Dec 2009 02:40:54 +0000</pubDate>
		<guid isPermaLink="false">http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15652</guid>
		<description>Thanks,
This is perfect...just what I needed for the mother of all XSL translations!</description>
		<content:encoded><![CDATA[<p>Thanks,<br />
This is perfect...just what I needed for the mother of all XSL translations!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: major</title>
		<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15651</link>
		<dc:creator>major</dc:creator>
		<pubDate>Fri, 18 Dec 2009 00:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15651</guid>
		<description>Good point, Kyle. That certainly would be helpful. ;-)</description>
		<content:encoded><![CDATA[<p>Good point, Kyle. That certainly would be helpful. <img src='http://rackerhacker.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Gato</title>
		<link>http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15650</link>
		<dc:creator>Kyle Gato</dc:creator>
		<pubDate>Fri, 18 Dec 2009 00:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://rackerhacker.com/2007/04/12/disable-ssh-timeouts/#comment-15650</guid>
		<description>Then restart SSHD?</description>
		<content:encoded><![CDATA[<p>Then restart SSHD?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

