Re: Interface index hack in IP_ADD_MEMBERSHIP



On Mon, Mar 19, 2007 at 10:28:37PM +0700, Eugene Grosbein wrote:
On Mon, Mar 19, 2007 at 02:28:52PM +0000, Bruce M Simpson wrote:

I plan to get rid of the ugly little ip_multicast_if() hack in the IP
stack.=
Before I do, is anyone actually using this?

RFC 3678 specifies a protocol independent API for socket group
memberships which allow joins on interfaces referenced by index. This is
intended to support IGMPv3 and MLDv2.

I recall that routed and ripd used to utilize something similar
long time ago. I'm not sure if they have switched to another API.

Quagga still uses it, too, if its configure script detects FreeBSD
or NetBSD. I'm afraid it was me who submitted the patch to the
Quagga folks when I'd found that Quagga's ospfd couldn't handle
unnumbered P2P interfaces in FreeBSD because their local IPs weren't
unique. Unfortunately, Quagga doesn't seem to use the protocol
independent part of the RFC 3678 API yet.

--
Yar
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Query a DNS in C
    ... |> Can anyone point any explicit doc, or the ... in RFC 1035) and lets the caller use a simple API to send queries and read ... Whether that API would simply be a "build and breakdown" API ... for DNS datagrams, or a more sophisticated system that waits for multiple ...
    (comp.unix.programmer)
  • Re: AES_128 in RFC 4493
    ... I find that there is an API called as AES_128. ... used in the RFC 4493. ... i am unable to find the source code for AES_128 in the RFC 4493. ... The call AES_128(k, in, out) is pseudo code for AES - if you want to use the ...
    (sci.crypt)
  • Re: IGMPv3 (was Re: pim6sd)
    ... the api draft was published as rfc 3678. ... I know MSF API has been published as an RFC, but I have to wait until ... the IPR issue raised by Apple has been closed, ... IGMPv3/MLDv2, but I think it's dangerous to MFC IGMPv3/MLDv2 without ...
    (freebsd-net)
  • Re: AES_128 in RFC 4493
    ... > In the RFC 4493, i find the source code in C language for AEC CMAC ... > I find that there is an API called as AES_128. ... The call AES_128(k, in, out) is pseudo code for AES - if you want to use the RFC code you will have to find an AES implementation and build an API around it to match the RFC 4493. ...
    (sci.crypt)