Re: [pim] Very simple pimd multicast configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pim] Very simple pimd multicast configuration
Famille_Béasse,ÄúºÃ£¡
Except you try to use mping instead of ping,you should firstly let the server/client can send igmp response message to the router,so the router knows it has a member join the multicast group.
If the source has sent multicast packets,you use "ip mroute show" and should see the mroute table created.
And I think if you use a normal multicast address such as 225.1.1.100 it will be better.
======= 2004-05-09 23:10:49 ÄúÔÚÀ´ÐÅÖÐдµÀ£º=======
>Hi,
>
>Can someone can help-me to make a very simple multicast configuration.
>
>Here is my test configuration (With just one Router):
>
>Server ----------------Multicast Router ----------------------Client
>[192.168.1.1 192.168.1.250] [192.168.0.250 192.168.0.1]
>
>Netmask is 255.255.255.0
>/proc/sys/net/ipv4/ip_forward is set to1
>Router is Linux Fedora Core 1 With Pimd-2.1.0-alpha29-18
>IP_Multicast PIM-SM etc is activate by default in kernel.
>
>My router is ok for unicast. I can communicate from server to client.
>
>But When i want to make Multicast from Server to Client, traffic is not
>forward by the router.When i do a "ping -t 5 224.0.0.1" on Linux Client,
>packets are not forwards to Linux Server and vice-versa.
>
>What tools can i use to see if configuration is OK ?
>What's about pimd.conf configuration file ?
>
>When i do a "ip mroute show" there is nothing to see is it normal ?
>
>Do you have any idea.
>Thanks for your help.
>
>Best regards
>
>Christophe Béasse
>France
>
>
>
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www1.ietf.org/mailman/listinfo/pim
= = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wlq
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wlq_w@hotmail.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2004-05-13
bšf¢–)à–+-¦)¢z×è®m¶›?ÿ0Ö'~Šàþf¢–f§þX¬¶)ߣúb
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.