How to multicast on different IP network


 
Thread Tools Search this Thread
Operating Systems Linux How to multicast on different IP network
# 1  
Old 09-03-2007
How to multicast on different IP network

On Linux, I have configured two different IP address for two network device eth0 ,eth1 , in my program, I want to multicast differently on these two network, I know it must add route for single network and I try to config another route for second network,but it can not work correctly, how to config multicast for dual network ? (Same question been asked on HP-UX parts of forum)
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. IP Networking

Multicast IP address

Hi please help, theoretically I',m interested in starting a streaming service using multicast IP service. I'd like to know how do I get an IP address that I can send my data too? (please don't just point me too Internet Assigned Numbers Authority as ive been there and it just seem to state... (1 Reply)
Discussion started by: fishman2001
1 Replies

2. Red Hat

Iptables/Firewall rules for multicast IP.

Hi Gurus, I need to add Multicast Port = xyz Multicast Address = 123.134.143 ( example) to my firewall rules. Can you please guide me with the lines I need to update my iptables files with. (0 Replies)
Discussion started by: rama krishna
0 Replies

3. Programming

Ubuntu 10.04 + Multicast Receiver c++

Hello all, I have created a UDP multicast transmitter and receiver, first using windows. But now I need the receiver to run on Ubuntu 10.04. The code is the following: /************************** Receiver *************************/ // Module Name: Receiver.c // // Description: // ... (0 Replies)
Discussion started by: tiny05
0 Replies

4. UNIX for Advanced & Expert Users

multicast protocole in unix

hi, i'm using fedora. and i want to install mospf and pim sm services. i read that there is mgated daemon for mospf but i cant find it. can u tell me where to find it? and how to install it? (0 Replies)
Discussion started by: jalil smail
0 Replies

5. Solaris

multicast config

On SUN Solaris 10, if I want to multicast packets between nodes, whether it must config the multicast IP from OS, if yes, how to do it? (0 Replies)
Discussion started by: Frank2004
0 Replies

6. HP-UX

How to multicast on different IP network

Hi, there On HP-UX, I want to multicast packets on two different IP network repectively. The two NIC are configured with two different IP. The routes are added with one default and one net for each IP . The multisender programs bind their own local IP, multireceiver programs add the... (0 Replies)
Discussion started by: Frank2004
0 Replies

7. HP-UX

multicast data can not receive

On HP-UX, we want to exchange data via multicast, there happen to meet a problem: sometimes the receiver that has joined the group can not receive the multicast data, but the recvfrom call returned no error. We have reconfig the network and added the default the route, but still can not fixed it,... (0 Replies)
Discussion started by: Frank2004
0 Replies

8. Solaris

How to assign multicast IP address

How can I assign multicast ip address to my Sun server. I need this configuration to set up weblogic in cluster mode. This setup needs a multicast IP address where the managed servers can broadcast their heartbeats. Thanks (0 Replies)
Discussion started by: krishan
0 Replies

9. UNIX for Dummies Questions & Answers

how to capture multicast packets using snoop

How do I use snoop command to capture multicast packets in the network? (1 Reply)
Discussion started by: caden312
1 Replies
Login or Register to Ask a Question
smcroute(8)						      System Manager's Manual						       smcroute(8)

NAME
SMCRoute - Static Multicast Router (-Interface) - Version 0.95 SYNOPSIS
smcroute < options > < commands > options -d - start daemon -v - verbose output -D - enable debug logging commands - common -h - print help -k - kill daemon commands - multicast routing related -a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... - add route -r <InputIntf> <OriginIpAdr> <McGroupAdr> - remove route commands - multicast signaling related -j <InputIntf> <McGroupAdr> - join MC group -l <InputIntf> <McGroupAdr> - leave MC group DESCRIPTION
SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. It supports both IPv4 and IPv6 multicast routing. SMCRoute can be used as an alternative to dynamic multicast routers like 'mrouted' in situations where static multicast routes should be maintained and/or no proper IGMP or MLD signaling exists. Generally multicast routes exists in the kernel only as long as smcroute or another multicast routing daemon is running. Only one multicast routing daemon can be active at a time, so it's impossible to run smcroute and e.g. 'mrouted' at the same time. The -d option smcroute is used to start the smcroute daemon. Otherwise, smcroute searches for an already running smcroute daemon and passes the commands to it. The -k option will terminate a running daemon. Multicast routes can be added with the -a command and removed with the -r command. A multicast route is defined by an input interface (<IntputIntf>), a unicast IP origin address (<OriginIpAdr>), a multicast group (<McGroupAdr>) and a list of output interfaces (<OutputIntf> ...). The origin and multicast group addresses must both be IPv4 addresses or IPv6 addresses. If IPv4 addresses are specified then SMCRoute will operate on the IPv4 multicast routes. If IPv6 addresses are specified then SMCRoute will operate on the IPv6 multicast routes. The output interfaces must not be given with the -r as the first three parameter are sufficient to identify the route to remove. The intention of SMCRoute is to help in situation where dynamic multicast routing does not work properly, but dynamic multicast routing is in nearly all cases the preferred solution. SMCRoute supports dynamic multicast routing with the multicast group 'join' -j and 'leave' -l commands. For both commands the input interface on which the multicast sessions should be received (<InputIntf>) and the multicast group address <McGroupAdr> must be given. The <McGroupAdr> may be an IPv4 or IPv6 address. Superuser rights are necessary to start the smcroute daemon or to communicate with the daemon. OPTIONS
-d Starts the smcroute daemon before any of the optional following commands are executed. -v Gives verbose output in some error situations (don't expect too much, check syslog instead). -D Gives additional debug messages in normal use (don't expect too much, see syslog instead). COMMANDS
-a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... The command is passed to the daemon that adds the given multicast route to the kernel's routing table. <InputIntf> can be any net- work interface as listed by 'ifconfig' or 'ip link list' (incl. tunnel interfaces), but not the loopback interface. <OriginIpAdr> is the source IP address of the multicast packets that will be routed by this entry. It is a unicast IPv4 or IPv6 address and not a multicast IP address. <McGroupAdr> is the IPv4 or IPv6 address of the multicast group that will be forwarded. <OutputIntf> [<Out- putIntf>] ... is a list of one or more network interfaces to which the multicast packets will be forwarded. The same rules for the selection of output interfaces applies as for the input interface. Warning, by using multiple output interfaces (traffic multiplication), using the input interface also as output interface (direct loop) or constructing some other forms of indirect loop you can flood you network. -r <InputIntf> <OriginIpAdr> <McGroupAdr> The command is passed to the daemon that removes a multicast route previously added with the -a command. The parameters are identi- cal except to the omitted list of <OutputIntf>. -j <InputIntf> <McGroupAdr> The command is passed to the daemon that passes it to the kernel. The kernel then tries to join the multicast group <McGroupAdr> on interface <InputIntf> by starting IGMP (or MLD if <McGroupAdr> is an IPv6 address) signaling on <InputIntf>. This signaling may be received by routers connected to <InputIntf>'s network that support IGMP/MLD multicast signaling and then hopfuly start forwarding of the requested multicast session to <InputIntf>'s network. With this command smcroute allows the integration of nodes that needs static multicast routing into dynamic multicast routing net- works. -l <InputIntf> <McGroupAdr> The command is passed via the daemon to the kernel that initiate a 'leave' for a previously 'joined' multicast group. LIMITS
The current version compiles and runs fine with the Linux kernel version 2.4. The known limits are: Multicast routes: more then 200 Multicast group membership: max. 20 FILES
/proc/net/ip_mr_cache - contains the active IPv4 multicast routes /proc/net/ip_mr_vif - contains the IPv4 'virtual' interfaces used by the active multicast routing daemon /proc/net/ip6_mr_cache - contains the active IPv6 multicast routes /proc/net/ip6_mr_vif - contains the IPv6 'virtual' interfaces used by the active multicast routing daemon /var/run/smcroute - IPC socket created by the smcroute daemon SEE ALSO
mrouted BUGS
The English wording of this man page. AUTHORS
smcroute was originally written by Carsten Schill <carsten@cschill.de>, support for IPv6 was added by Todd Hayton <todd.hayton@gmail.com>, support for FreeBSD was added by Micha Lenk <micha@debian.org>. The source code is now maintained by Todd Hayton <todd.hayton@gmail.com>, Micha Lenk <micha@debian.org> and Julien BLACHE <jblache@debian.org>. The current version is available at: http://alioth.debian.org/projects/smcroute TIPS
A lot of extra information is sent under the daemon facility and the debug priority to the syslog daemon. August 08, 2011 smcroute(8)