From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: RFC: Patch to add support for multiple multicast routing tables.
Date: Tue, 24 Jun 2008 22:28:07 -0700 [thread overview]
Message-ID: <20080624222807.3a9918d1@speedy> (raw)
In-Reply-To: <4861966B.5090208@candelatech.com>
On Tue, 24 Jun 2008 17:50:51 -0700
Ben Greear <greearb@candelatech.com> wrote:
> In order to run multiple Xorp instances and treat different groups of
> interfaces as being in their own virtual router, I had to update the
> ipv4/ipmr.c logic to support multiple routing tables.
>
> I will be attempting to push the cooresponding xorp changes to it's
> maintainers if this is accepted into the kernel. It should be fully
> backwards compatible with existing xorp and other multicast
> routing tools. It does change the procfs output slightly, adding
> a TableId column.
>
> The original patch was written by me, and then Patrick McHardy
> fixed up my cruft and made it much smaller and with better locking.
> I then fixed a few bugs I found while testing with my modified xorp.
>
> The attached patch is against 2.6.25.4 + hacks. It has a few rejects
> against 2.6.26.rc7,
> but I will fix those sooner rather than later if the patch is otherwise
> deemed
> worthy.
>
> Please let me know if this stands a chance of inclusion.
>
> Thanks,
> Ben
Ben private ioctl's make it hard to handle 32bit/64bit compatiablity,
and routing is better managed through rtnetlink. Doesn't XORP do
netlink?
next prev parent reply other threads:[~2008-06-25 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 0:50 RFC: Patch to add support for multiple multicast routing tables Ben Greear
2008-06-25 5:28 ` Stephen Hemminger [this message]
2008-06-25 5:52 ` Ben Greear
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=20080624222807.3a9918d1@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=greearb@candelatech.com \
--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).