Re: UDP multicast packets not seen on listening interface in BETA5

From: Robert Watson (rwatson_at_FreeBSD.org)
Date: 09/29/05

  • Next message: Robert Watson: "Re: UFS_EXTATTR(_AUTOSTART) broken on 6.0-BETA5" 
    Date: Thu, 29 Sep 2005 22:09:42 +0100 (BST)
To: josh.carroll@psualum.com

    On Thu, 29 Sep 2005, Josh Carroll wrote:

    > I suspect maybe I am not properly joining the multicast group, so it's
    > ignoring the packet. But like I said, this worked in BETA3 which is why
    > I'm stumped.

    Normally when you join a multicast group, IGMP messages will be sent on
    the interface where it is joined. Could you confirm that messages are
    sent in BETA3, and whether or not they are sent in BETA5?

    When you subscribe to a multicast address, you do so on a particular
    interface with a particular subscription. The multicast API allows you to
    either use a default interface based on not specifying a particular
    interface IP address, or allows you to specify an interface by IP address.
    Could you tell me whether or not your application attempts to specify what
    interface to use, and if there are other interfaces on the system that
    (potentially) a multicast application might select instead?

    If you use netstat -ia, it will show you all interfaces and current
    multicast address subscriptions. Could you show me the entries for your
    application running in BETA3, and any similar entries you can or cannot
    find in BETA5?

    Thanks,

    Robert N M Watson
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Robert Watson: "Re: UFS_EXTATTR(_AUTOSTART) broken on 6.0-BETA5"

    Relevant Pages

    • Re: Multicast question
      ... Or a method to specify the multicast ... I had expected ntpd would already do so. ... can only go out on exactly one interface. ...
      (comp.protocols.time.ntp)
    • Re: multicast join group error : No such device
      ... > Set imr_address to something other than zero. ... You need to specify the ... > address of the interface on which you want to join this multicast ...
      (comp.os.linux.networking)
    • Re: Bind succeeded but not receiving mulitcast packets
      ... I have a mulitcast server program. ... I have added the interface to the ... programming the multicast filter correctly. ... VxWorks, ...
      (comp.os.vxworks)
    • Re: Bind succeeded but not receiving mulitcast packets
      ... I have a mulitcast server program. ... I have added the interface to the ... programming the multicast filter correctly. ... VxWorks, ...
      (comp.os.vxworks)
    • Re: Multicast question
      ... IT is synchronizing correctly but I cannot get it to multicast on any interface except the systems primary Ethernet interface, ... Multicast routing deamons then run the IGMP and other protocols to ... These packets are replicated to ...
      (comp.protocols.time.ntp)