If one of your quagga daemons is sitting on a segment on the cisco router and you can see the daemons multicast frames on that segment, but not on the token ring segment you are trying to have them reach, I would suspect that you don't have igmp working properly. I assume you are starting something on your token ring based host to listen for these message (another quagga daemon I assume), do you see an IGMP frame go out to subscribe your host to that multicast address? If not, I expect you need to configure your router to send all multicasts to your subnet. This would also be true if you were just snooping the wire, hoping to see multicast frames from another host on a different subnet without driving any IGMP subscriptions.Neil Horman <nhorman@xxxxxxxxxx> writes:
Sorry, I must have been out to lunch when I wrote that. Completely missed the multicast check. New patch attached.
Thanks. I tried the second patch you sent, but unfortunately it didn't make any difference.
One thing strikes me as strange: Why don't I see any of the multicast packets even when the adapter is in promiscous mode? I can only see broadcasts and unicasts to and from my own address.
Neil
Listening on tr1 (with "tcpdump -nevv -s4000 -x -i tr1") when quagga sends multicasts on tr0 gives me nothing. Neither the packets I know quagga must send since they are received by the Cisco router, nor the multicast packets the Cisco router sends, show up on tr1.
Bjørn
-- /*************************************************** *Neil Horman *Software Engineer *Red Hat, Inc. *nhorman@xxxxxxxxxx *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/ - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
