netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Teräs" <timo.teras@iki.fi>
To: netdev@vger.kernel.org
Subject: Re: multicast for v2.6.29
Date: Tue, 23 Jun 2009 17:41:19 +0300	[thread overview]
Message-ID: <4A40E98F.5050903@iki.fi> (raw)
In-Reply-To: <4A40E151.10007@iki.fi>

Whoops. This was not supposed be sent on the list as-is.

This is more of an RFC, for what I want to do in future. Multicast routing
for NBMA destinations.

The patch is quick hack, and breaks ABI, and not intended for inclusion.
I suppose the multicast routing would need to be updated to Netlink era
before doing this kind of thing. And remove the hard coded limits such
as amount of MFC destinations and that you can have only one multicast
router user space process.

If you have any comments on the patch, they are appreciated.

Thanks,
  Timo


      reply	other threads:[~2009-06-23 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 14:06 multicast for v2.6.29 Timo Teräs
2009-06-23 14:41 ` Timo Teräs [this message]

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=4A40E98F.5050903@iki.fi \
    --to=timo.teras@iki.fi \
    --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).