public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Fremlin" <vii@altern.org>
To: "Jamie Lokier" <ln@tantalophile.demon.co.uk>
Cc: "Andi Kleen" <ak@muc.de>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	<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: 30 Jan 2001 00:47:04 +0000	[thread overview]
Message-ID: <m2zog9sw6v.fsf@boreas.yi.org.> (raw)
In-Reply-To: <m2d7d838sj.fsf@boreas.yi.org.> <200101290245.f0T2j2Y438757@saturn.cs.uml.edu> <20010129135905.B1591@fred.local> <20010129193136.A11035@pcep-jamie.cern.ch>
In-Reply-To: Jamie Lokier's message of "Mon, 29 Jan 2001 19:31:36 +0100"

Jamie Lokier <ln@tantalophile.demon.co.uk> writes:

[...]

> 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.

No connections at all will be destroyed by my patch unless you enable
the new killoldaddr pppd option.

-- 

	http://www.penguinpowered.com/~vii
-
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/

  parent reply	other threads:[~2001-01-30  0:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-27 22:54 [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) John Fremlin
2001-01-29  2:45 ` Albert D. Cahalan
2001-01-29 12:59   ` Andi Kleen
2001-01-29 18:31     ` Jamie Lokier
2001-01-29 21:08       ` Andi Kleen
2001-01-30  0:47       ` John Fremlin [this message]
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=m2zog9sw6v.fsf@boreas.yi.org. \
    --to=vii@altern.org \
    --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=ln@tantalophile.demon.co.uk \
    --cc=netdev@oss.sgi.com \
    --cc=paulus@linuxcare.com \
    /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