Board index Linux Networking

Multicast using socket bound to IP looback address

Multicast using socket bound to IP looback address

Post by chin.. » Wed, 03 May 2000 04:00:00



Hello:

    I have a question about the sequence of operations I am trying out.

-   A UDP server is started on the local machine listening on address
INADDR_ANY and port 9001.

-   A socket is created and bound on the 'loopback' address (127.0.0.1)
and on port 9002.

-   The server socket has an option set to listen to multicast address.

    The client (bound on loopback address) sends data on the machine's
IP address. This data is received at the server. The client then sends
data on the multicast address to which the server is listening to. The
server does not get the multicast packet.

    If the same program is run on SOLARIS the multicast packet is
received.

    Here are my questions -

1)  Can I send a multicast packet on a socket bound on the IP loopback
address.

2)  If yes, then does LINUX implement this functionality.

3)  If I get the packet on the server, how can I find out if it came on
the multicast address or on the unicast address.

    I know that I am setting the server socket options correctly,
because when I bind the client to the local IP address and send the
multicast packet the packet is received at the server.

Thanks for your answers and time.

Regards,

Chinmay
(I dont speak for my company in this email)

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 
Top

1. multicast socket bind() address in use

I'm having a problem binding to a socket on a multicast addess. I'm
interested
only in reading the multicast address.
Here's what I'm doing:

1. I create a UDP socket
2. I use setsockopt options to set IP_MULTICAST_IF, IP_ADD_MEMBERSHIP,
    and SO_REUSEADDR
3. I bind the socket to the multicast address and port number that I'm
interested in

I'm actually doing this twice, because I am interested in two ports -
they
happen to be 1024 and 1026 (immediately following the last reserved port
-
I don't know if this is significant)

I have two linux boxes, both running RH6.0. On one box, I can bind fine
to port 1026 and get the data from the multicast channel, but when it
tries
to bind to 1024 it returns "address already in use." On the other linux
box,
I get the same behavior, except reversed - port 1024 binds ok, but port
1026 says address already in use. I've found that it doesn't matter what

the address is in the sockaddr_in structure that is passed to bind() -
it
could be INADDR_ANY or the particular multicast address that I'm
interested
in, or any other IP address, it still doesn't bind. If I change the port
number
it will bind, but that doesn't do me any good, because the data that I'm

interested in is on ports 1024 and 1026.

Does anyone know how I can force a socket to bind to a particular
address,
regardless of whether something else is bound to it? (When I run netstat
from
the command line, it doesn't appear that anything is using the port
isn't binding)
SO_REUSEADDR doesn't seem to be enough. Does anyone else understand
this any better than I do?

TIA,
Steve

--
-------------------------------------------------------

Research Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------

2. Physical hookup of ftape unit

3. multicast using tcp/ip sockets

4. httpd Won't start!

5. using bind() to bind socket to device

6. ncpfs exported via NFS mystery

7. Binding a single IP Address to two different MAC addresses

8. ssh-agent and CDE

9. binding IP Address to MAC Address (newbie)

10. calling connect() or bind() for recv. multicast sockets?

11. bind to a multicast address

12. binding to a multicast address with multiple listeners

13. IP-Socket, Buffer, Interface-IP-Address


All times are UTC
Board index