From: David Miller <davem@davemloft.net>
To: opurdila@ixiacom.com
Cc: mail4ilia@gmail.com, netdev@vger.kernel.org
Subject: Re: multicast routing and multiple interfaces with same IP
Date: Sat, 29 Aug 2009 00:01:54 -0700 (PDT) [thread overview]
Message-ID: <20090829.000154.263733862.davem@davemloft.net> (raw)
In-Reply-To: <200908270253.19132.opurdila@ixiacom.com>
From: Octavian Purdila <opurdila@ixiacom.com>
Date: Thu, 27 Aug 2009 02:53:18 +0300
> I don't have context on multicast routing, but this caught my attention:
>
>>@@ -61,11 +61,13 @@
>> unsigned int vifc_rate_limit; /* Rate limiter values (NI) */
>> struct in_addr vifc_lcl_addr; /* Our address */
>> struct in_addr vifc_rmt_addr; /* IPIP tunnel addr */
>>+ int ifindex; /* Local interface index */
>> };
>>
>
> Wouldn't this break userspace ABI?
>
> Perhaps you could use a union between vifc_lcl_addr and vifc_ifindex, they seem
> to be exclusive.
Indeed, this will need to be fixed up.
next prev parent reply other threads:[~2009-08-29 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 23:26 multicast routing and multiple interfaces with same IP Ilia K.
2009-08-26 23:53 ` Octavian Purdila
2009-08-29 7:01 ` David Miller [this message]
2009-09-07 15:35 ` Ilia K.
2009-09-07 16:25 ` Octavian Purdila
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=20090829.000154.263733862.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mail4ilia@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.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