[lkml]   [2002]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Multicast fails when interface changed
* Christopher James ( wrote:

> It was our expectation that the switch from the first to second
> interface should work without any involvement from the application
> because the second interface is configured exactly the same as the
> first interface. After the switch, everything seems to work with the
> exception of multicasting: the multicast membership information is not
> propagated to the second interface, it stays with the first interface.

i don't think this is a valid expectation. joining a multicast group
is a device specific action. when you join, you either specify an
interface to join on (imr_interface=dev_ip_addr) or let the kernel choose
(imr_interface=INADDR_ANY). in either case, you are telling some hardware
to adjust its multicast filter and identifying that hardware by a unique
device index. as alexey mentioned, it sounds like your app has never told
the second interface that is should even care about multicast packets.
did you try joining on both interfaces? (you may find using a unique
service ip addr on each interface, and failing over an application ip
addr using aliases will help)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:18    [W:0.071 / U:2.920 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site