From: "David S. Miller" <davem@redhat.com>
To: davidsen@tmr.com
Cc: dean-list-linux-kernel@arctic.org, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [BUG?] unwanted proxy arp in 2.4.19-pre10
Date: Sun, 14 Jul 2002 22:45:17 -0700 (PDT) [thread overview]
Message-ID: <20020714.224517.45499035.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020714212910.21185A-100000@gatekeeper.tmr.com>
From: Bill Davidsen <davidsen@tmr.com>
Date: Sun, 14 Jul 2002 21:39:12 -0400 (EDT)
Clearly FAQ means frequently asked, not answered. I can't find the
appropriate patch, clearly some people regard allowing source routing to
be a benefit.
Source routing exists in every single 2.4.x kernel every released.
What are you talking about? There is no patch to speak of, it's
already there.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-07-15 5:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 16:21 Bill Davidsen
2002-07-13 18:28 ` Alan Cox
2002-07-13 19:19 ` Gerhard Mack
2002-07-14 1:52 ` Alan Cox
2002-07-14 3:17 ` Bill Davidsen
2002-07-14 3:59 ` David S. Miller
2002-07-14 17:29 ` dean gaudet
2002-07-15 1:39 ` Bill Davidsen
2002-07-15 5:45 ` David S. Miller [this message]
2002-07-15 10:39 ` Bill Davidsen
2002-07-15 1:46 ` Bill Davidsen
2002-07-14 10:34 Julian Anastasov
2002-07-23 22:06 ` Bill Davidsen
[not found] <20020713.205930.101495830.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0207141026440.4252-100000@twinlark.arctic.org.suse.lists.linux.kernel>
2002-07-14 18:40 ` Andi Kleen
2002-07-15 5:37 ` David S. Miller
2002-07-14 22:35 Julian Anastasov
2002-07-15 5:40 ` David S. Miller
2002-07-16 22:32 Julian Anastasov
2002-07-16 20:04 ` Daniel Gryniewicz
2002-07-16 23:41 ` Julian Anastasov
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=20020714.224517.45499035.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=linux-kernel@vger.kernel.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®