netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mr. Berkley Shands" <bshands@exegy.com>
To: Net Dev <netdev@vger.kernel.org>
Subject: 2.6.32 and Multicast group membership
Date: Tue, 01 Jun 2010 16:39:00 -0500	[thread overview]
Message-ID: <4C057DF4.3000305@exegy.com> (raw)

starting in 2.6.32, my multicast connections stop getting data after 
60-100 seconds.
The identical user code works fine under 2.6.22 through 2.6.31.

The NIC (an intel 82586) has two ports on the same subnet
(eth0 at 172.16.21.55/24 and eth1 at 172.16.21.56/24)

      if (setsockopt(sock, IPPROTO_IP, IP_ADD_MEMBERSHIP, (char*)&req, 
sizeof(req)))
      {
         perror("setsockopt IP_ADD_MEMBERSHIP failed");
         ::exit(-1);
      }

If I do ADD_MEMBERSHIP on just one of these interfaces, the sockets 
still get data.
But if I join on both interfaces, one or both will stop getting packets
after 60-100 seconds. Sniffing with tcpdump shows the Cisco layer 3 switch
is not getting its responses back to keep the multicast group open.
The HP layer 2 switch does not seem to care, it keeps the data flowing 
regardless
of which physical port the join is executed on.

Changing IP_MULTICAST_ALL has no effect :-(
Did I miss something? New code that I have to specify to keep the Cisco 
happy?

tia

Berkley


-- 

// E. F. Berkley Shands, MSc//

** Exegy Inc.**

349 Marshall Road, Suite 100

St. Louis , MO  63119

Direct:  (314) 218-3600 X450

Cell:  (314) 303-2546

Office:  (314) 218-3600

Fax:  (314) 218-3601

 

The Usual Disclaimer follows...

 



             reply	other threads:[~2010-06-01 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 21:39 Mr. Berkley Shands [this message]
2010-06-05 11:33 ` 2.6.32 and Multicast group membership Mark Smith

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=4C057DF4.3000305@exegy.com \
    --to=bshands@exegy.com \
    --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).