Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have upgraded a server from RH4 -> RH5.5 and we have an interesting issue with multicast.

  • we have multiple NICS on the server, we want the bond0 to default as the default interface.
  • adding route 224.0.0.0/4 dev bond0 doesn't seem to work.
  • removing multicast from the other interfaces via ifconfig -multicast does not work either.
  • as you can see below, eth0 seems to be the default interface.
  • everything works fine if I down the interfaces in front of bond0 first.
    $ ip route
    146.149.87.248/29 dev eth0  proto kernel  scope link  src 146.149.87.253
    146.149.87.216/29 dev eth5  proto kernel  scope link  src 146.149.87.221
    169.113.218.0/23 dev bond1  proto kernel  scope link  src 169.113.218.62
    169.113.216.0/23 dev bond0  proto kernel  scope link  src 169.113.217.60
    10.11.184.0/21 dev eth6  proto kernel  scope link  src 10.11.184.96
    169.254.0.0/16 dev eth6  scope link
    **224.0.0.0/4 dev bond0  scope link**
    default via 169.113.216.1 dev bond0

    $ netstat -g
    IPv6/IPv4 Group Memberships
    Interface       RefCnt Group
    --------------- ------ ---------------------
    lo              1      ALL-SYSTEMS.MCAST.NET
    eth0            1      224.9.10.11
    eth0            1      224.10.10.21
    **eth0            1      ALL-SYSTEMS.MCAST.NET**
    eth5            1      ALL-SYSTEMS.MCAST.NET
    eth6            1      ALL-SYSTEMS.MCAST.NET
    bond0           1      ALL-SYSTEMS.MCAST.NET
    bond1           1      ALL-SYSTEMS.MCAST.NET


    $ tcpdump -i eth0
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
    00:18:58.093483 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:18:58.231905 IP 146.149.87.249 > PIM-ROUTERS.MCAST.NET: PIMv2, Hello, length: 34
    00:18:58.492444 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:18:58.851423 IP 146.149.87.253.43237 > 224.9.10.11.bullant-rap: UDP, length 24
    00:18:58.891409 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:18:58.902533 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 161
    00:18:59.040125 802.1d unknown version
    00:18:59.291385 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:18:59.690362 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:18:59.851356 IP 146.149.87.253.43237 > 224.9.10.11.bullant-rap: UDP, length 24
    00:18:59.851716 IP 146.149.87.253.43237 > 224.9.10.11.bullant-rap: UDP, length 45
    00:18:59.904441 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 161
    00:19:00.105330 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
    00:19:00.221321 IP 146.149.87.253 > 224.9.10.11: igmp v2 report 224.9.10.11
    00:19:00.504310 IP 146.149.87.253.60830 > 239.255.64.101.22355: UDP, length 24
share|improve this question
1  
This is when you ask RedHat support, it may have been a regression with the particular kernel release installed. –  Steve-o Aug 24 '11 at 9:25

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.