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
ROUTE(8)						      System Manager's Manual							  ROUTE(8)

NAME
route - manually manipulate the routing tables SYNOPSIS
/sbin/route [ -f ] [ -n ] [ command args ] DESCRIPTION
Route is a program used to manually manipulate the network routing tables. It normally is not needed, as the system routing table manage- ment daemon, routed(8), should tend to this task. Route accepts two commands: add, to add a route, and delete, to delete a route. All commands have the following syntax: /sbin/route command [ net | host ] destination gateway [ metric ] where destination is the destination host or network, gateway is the next-hop gateway to which packets should be addressed, and metric is a count indicating the number of hops to the destination. The metric is required for add commands; it must be zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways. If adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used for transmission. Routes to a particular host are dis- tinguished from those to a network by interpreting the Internet address associated with destination. The optional keywords net and host force the destination to be interpreted as a network or a host, respectively. Otherwise, if the destination has a ``local address part'' of INADDR_ANY, or if the destination is the symbolic name of a network, then the route is assumed to be to a network; otherwise, it is pre- sumed to be a route to a host. If the route is to a destination connected via a gateway, the metric should be greater than 0. All sym- bolic names specified for a destination or gateway are looked up first as a host name using gethostbyname(3N). If this lookup fails, get- netbyname(3N) is then used to interpret the name as that of a network. Route uses a raw socket and the SIOCADDRT and SIOCDELRT ioctl's to do its work. As such, only the super-user may modify the routing tables. If the -f option is specified, route will ``flush'' the routing tables of all gateway entries. If this is used in conjunction with one of the commands described above, the tables are flushed prior to the command's application. The -n option prevents attempts to print host and network names symbolically when reporting actions. DIAGNOSTICS
``add [ host | network ] %s: gateway %s flags %x'' The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl call. If the gateway address used was not the primary address of the gateway (the first one returned by gethostbyname), the gateway address is printed numerically as well as symbolically. ``delete [ host | network ] %s: gateway %s flags %x'' As above, but when deleting an entry. ``%s %s done'' When the -f flag is specified, each routing table entry deleted is indicated with a message of this form. ``Network is unreachable'' An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given. ``not in table'' A delete operation was attempted for an entry which wasn't present in the tables. ``routing table overflow'' An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry. SEE ALSO
intro(4N), routed(8), XNSrouted(8) 4.2 Berkeley Distribution November 16, 1996 ROUTE(8)