listing multicast sockets

linux sockets multicast netstat
Sreeram Ravinoothala picture Sreeram Ravinoothala · Apr 9, 2013 · Viewed 33.2k times · Source

I am trying to list all opened multicast sockets on a linux system? netstat -g lists the groups joined though. Is there any other utility that I can use for this sake?

Thanks a lot for the help.

Answer

Johannes Overmann picture Johannes Overmann · Feb 27, 2014

In addition to netstat -g you can use this to see all sockets which are bound to a multicast address:

netstat -anu|sort -nk4

This is a list of all UDP sockets (whether multicast or not). Look for all addresses in the range 224.0.0.0 to 239.255.255.255. These are sockets bound to multicast addresses, regardless whether they joined the multicast group or not. These will only receive traffic for this multicast group.

But:

In practice UDP sockets which are used to receive multicast traffic are usually bound to address 0.0.0.0. These can receive UDP packets for all unicast and multicast addresses, and the server usually does some additional filtering based on the source-IP-address.

So in that list above you may want to look also at UDP sockets bound to 0.0.0.0, for example 0.0.0.0:5353 which is most likely the mDNS (avahi, zeroconf) server.

Related questions

Receiving multiple multicast feeds on the same port - C, Linux

I have an application that is receiving data from multiple multicast sources on the same port. I am able to receive the data. However, I am trying to account for statistics of each group (i.e. msgs received, bytes received) …

Read More
Do I need a PORT when joining a multicast group or just the IP?

I would like to learn that once and for all. What is the procedure to connect a multicast socket? I know you have to bind to a local interface (do you need IP and port for that?) then I know …

Read More
How do I remove a CLOSE_WAIT socket connection

I have written a small program that interacts with a server on a specific port. The program works fine, but: Once the program terminated unexpectedly, and ever since that socket connection is shown in CLOSE_WAIT state. If I try …

Read More