Date: Sat, 5 Jun 1999 23:20:20 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Stefan `Sec` Zehl <sec@42.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <199906060620.XAA17657@apollo.backplane.com> References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> <199906042004.NAA09067@apollo.backplane.com> <19990606022955.C17345@matrix.42.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:> wouldn't notice... nobody would notice.
:
:I would. I have several long-lived connections, with a few of them
:are sometimes unreachable for quote some time. I like that they survive,
:and would hate it, if some brain-dead default would ruin my perfectly
:set up connections.
:
:Even more, it would ruin dial-on-demand for a lot of people, i think.
:
:CU,
: Sec
Turn on keepalives and see if you actually notice. I can virtually
guarentee that you will not notice.
As far as dial-on-demand goes, that also makes no real difference.
There are very few two-way dial-on-demand systems. Usually
dial-on-demand is outgoing only. Incoming packets cannot activate them.
There are a few ISDN-based links and ISPs that implement it in both
directions both those are rapidly dying away. This means that incoming
data on the undialed link will cause a disconnect, making holding such
connections over an undialed link so unreliable that depending on the
effect is stupid. If you have an active connection to somewhere,
the link needs to be up for that connection to remain reliable whether
keepalives are turned on or not.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906060620.XAA17657>