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
ESIS(4) 						   BSD Kernel Interfaces Manual 						   ESIS(4)

NAME
esis -- End System to Intermediate System Routing Protocol SYNOPSIS
#include <sys/types.h> #include <netiso/esis.h> DESCRIPTION
The ES-IS routing protocol is used to dynamically map between ISO NSAP addresses and ISO SNPA addresses; to permit End Systems (ES) and Intermediate Systems (IS) to learn of each other's existence; and to allow Intermediate Systems to inform End Systems of (potentially) better routes to use when forwarding Network Protocol Data Units (NPDUs) to a particular destination. The mapping between NSAP addresses and SNPA addresses is accomplished by transmitting "hello" Protocol Data Units (PDUs) between the cooper- ating Systems. These PDUs are transmitted whenever the configuration timer expires. When a "hello" PDU is received, the SNPA address that it conveys is stored in the routing table for as long as the holding time in the PDU suggests. The default holding time (120 seconds) placed in the "hello" PDU, the configuration timer value, and the system type (End System or Intermediate System) may be changed by issuing an SIOCSSTYPE ioctl(2), which is defined in <sys/netiso/iso_snpac.h>. The protocol behaves differently depending on whether the System is configured as an End System or an Intermediate System. END SYSTEM OPERATION
When an interface requests a mapping for an address not in the cache, the SNPA of any known Intermediate System is returned. If an Interme- diate System is not known, then the all end systems multicast address is returned. It is assumed that the intended recipient of the NPDU will immediately transmit a "hello" PDU back to the originator of the NPDU. If an NPDU is forwarded by the End System, a redirect PDU will not be generated. However, redirect PDUs received will be processed. This processing consists of adding an entry in the routing table. If the redirect is towards an Intermediate System, then an entry is made in the routing table as well. The entry in the routing table will mark the NSAP address contained in the redirect PDU as the gateway for the desti- nation system (if an NET is supplied), or will create a route with the NSAP address as the destination and the SNPA address (embodied as a link-level struct sockaddr) as the gateway. If the System is configured as an End System, it will report all the NSAPs that have been configured using the ifconfig(8) command, and no others. It is possible to have more than one NSAP assigned to a given interface, and it is also possible to have the same NSAP assigned to multiple interfaces. However, any NSAP containing an NSEL that is consistent with the nsellength option (default one) of any interface will be accepted as an NSAP for this System. INTERMEDIATE SYSTEM OPERATION
When an interface requests a mapping for an address not in the routing table, an error is returned. When an NPDU is forwarded out on the same interface that the NPDU arrived upon, a redirect PDU is generated. MANUAL ROUTING TABLE MODIFICATION
To facilitate communications with systems which do not use ES-IS, one may add a route whose destination is a struct sockaddr_iso containing the NSAP in question, and the gateway being a link-level struct sockaddr, either by writing a special purpose program, or using the route(8) command e.g.: route add -iface -osi 49.0.4.8.0.2b.b.83.bf -link qe0:8.0.2b.b.83.bf If the System is configured as an End System and has a single network interface which does not support multicast reception, it is necessary to manually configure the location of an IS, using the route command in a similar way. There, the destination address should be ``default'' (spelled out literally as 7 ASCII characters), and the gateway should be once again be a link-level struct sockaddr specifying the SNPA of the IS. SEE ALSO
iso(4), ifconfig(8), route(8) End system to Intermediate system routing exchange protocol for use in conjunction with the Protocol for providing the connectionless-mode network service, ISO, 9542. BUGS
Redirect PDUs do not contain options from the forwarded NPDU which generated the redirect. The multicast address used on the IEEE 802.3 (Ethernet) network is taken from the National Bureau of Standards (NBS) December 1987 agreements. This multicast address is not compatible with the IEEE 802.5 (Token Ring) multicast addresses format. Therefore, broadcast addresses are used on the IEEE 802.5 subnetwork. Researchers at the University of Wisconsin are constructing an implementation of the IS-IS routing protocol. NBS is now known as the National Institute for Standards and Technology (NIST). BSD
November 30, 1993 BSD