From: Jamie Lokier <ln@tantalophile.demon.co.uk>
To: Andi Kleen <ak@muc.de>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
John Fremlin <vii@altern.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
paulus@linuxcare.com, linux-ppp@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR)
Date: Mon, 29 Jan 2001 19:31:36 +0100 [thread overview]
Message-ID: <20010129193136.A11035@pcep-jamie.cern.ch> (raw)
In-Reply-To: <m2d7d838sj.fsf@boreas.yi.org.> <200101290245.f0T2j2Y438757@saturn.cs.uml.edu> <20010129135905.B1591@fred.local>
In-Reply-To: <20010129135905.B1591@fred.local>; from ak@muc.de on Mon, Jan 29, 2001 at 01:59:05PM +0100
Andi Kleen wrote:
> > I get the same IP about 2/3 of the time, so it is pretty important
> > to avoid killing connections until after the new IP is known.
>
> I prefer it when the IP is killed as soon as possible so that I can see
> when the connection is lost (ssh sessions get killed etc.)
I like it when I get the same IP back and can continue an ssh session.
My line drops regularly in mid session.
Unfortunately getting the same IP is rare now, so I've been toying with
running a PPP tunnel through a fixed host out on the net. The tunnel
would be dropped and recreated with each new connection. My local link
IP would change, but the tunnel IP would not so connections to other
places, ssh etc. would all be from the tunnel IP.
The important thing is that the tunnel is destroyed and recreated (it
has to be, it is over different underlying link addresses). I do not
want that to destroy the connections from the tunnelled address.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 22:54 John Fremlin
2001-01-29 2:45 ` Albert D. Cahalan
2001-01-29 12:59 ` Andi Kleen
2001-01-29 18:31 ` Jamie Lokier [this message]
2001-01-29 21:08 ` Andi Kleen
2001-01-30 0:47 ` John Fremlin
2001-02-01 5:56 ` Ralf Baechle
2001-02-04 22:21 ` Mark Cooke
2001-01-30 0:43 ` John Fremlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010129193136.A11035@pcep-jamie.cern.ch \
--to=ln@tantalophile.demon.co.uk \
--cc=acahalan@cs.uml.edu \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=paulus@linuxcare.com \
--cc=vii@altern.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®