From: James Chapman <jchapman@katalix.com>
To: Florian Zumbiehl <florz@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/5 2.6.21-rc4] l2tp: pppol2tp core
Date: Sat, 24 Mar 2007 17:37:39 +0000 [thread overview]
Message-ID: <460561E3.9020502@katalix.com> (raw)
In-Reply-To: <20070324002242.GA26017@florz.florz.dyndns.org>
Florian Zumbiehl wrote:
> Hi,
>
>> + * 251003 : Copied from pppoe.c version 0.6.9.
>
> you might want to have a look at the patches to the PPPoE code that were
> posted to netdev recently, as some of them seem to apply to code that's
> left over from pppoe.c.
Do you mean this change?
* 070228 : Fix to allow multiple sessions with same remote MAC and same
* session id by including the local device ifindex in the
* tuple identifying a session. This also ensures packets can't
* be injected into a session from interfaces other than the
* one specified by userspace. Florian Zumbiehl <florz@gmx.de>
The pppoe session hash table isn't used in the pppol2tp code so the
above change doesn't affect pppol2tp. I rechecked the latest pppoe.c and
I don't see other changes that haven't already been incorporated in
pppol2tp. Which specific code in pppol2tp do you think needs to be updated?
Thanks
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
next prev parent reply other threads:[~2007-03-24 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 23:07 [PATCH 1/5 2.6.21-rc4] l2tp: pppol2tp core James Chapman
2007-03-24 0:22 ` Florian Zumbiehl
2007-03-24 17:37 ` James Chapman [this message]
2007-03-24 18:07 ` Florian Zumbiehl
2007-03-24 14:03 ` Patrick McHardy
2007-03-24 19:01 ` James Chapman
2007-03-24 19:26 ` David Miller
2007-03-24 20:56 ` Patrick McHardy
2007-03-25 16:00 ` James Chapman
2007-03-27 14:37 ` Patrick McHardy
2007-03-24 21:58 ` Patrick McHardy
2007-03-25 16:12 ` James Chapman
2007-03-27 11:32 ` Ingo Oeser
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=460561E3.9020502@katalix.com \
--to=jchapman@katalix.com \
--cc=florz@gmx.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).