multicast

To receive a multicast on my not default NIC (dvb) I do the following: open a socket (AF_INET, SOCK_DGRAM) join the multicast address with IP_ADD_MEMBERSHIP on the dvb interface bind the multicast address (note that a common error is to bind "0.0.0.0" and then receive on that socket even multicast you are not interested in) and the port at this point the only way to receive the needed multicast packets is to add in the routing table a rule to reach the network where the sender is (another network) trough the dvb, as if the dvb needs to reply to the multicast sender; let say a sort of source

Hi I have questions about WebRTC. I would like create one-to-many (1:N) connection with MCU server (because stream from source is too big (CPU,bandwidth...)), but I don't know how can I do that, exists some project for this? I found only EasyRTC, Licode etc. but I guess that is just for videoconferencing (many-to-many). Thank you very much Try WebRTC one-way broadcasting and one-to-many broadcasting experiments. Source codes are available as well. In peer-to-peer scenario; max limit for peer connections per single chrome instance (tab/window) is 256 . Obviously, there will be huge bandwidth

I have a prototype Android app that is listening for multicast packets to 'discover' clients to communicate with. The socket set up is similar to this: InetAddress group = InetAddress.getByName("228.1.2.3"); MulticastSocket s = new MulticastSocket(4000); s.joinGroup(group); This works very well when all the devices are connected via WiFi. I would like to support this with the phone acting as a portable hotspot. However, while all my devices appear to connect to the hotspot correctly I no longer receive multicast data. I'm wondering if there are restrictions that disallow this type of

Is there any advantage to using a multicast group to send messages rather than just broadcasting them to a specific port? I understand that when broadcasting, other computers that don't want the messages receive them too, but how much does it affect performance/traffic? Don't the computers that don't care just dump the message immediately? As a side question, does multicast outside the LAN work at all? I will assume you're talking about IP traffic. When you say LAN, I will assume you mean an ethernet topology inside an office building (I will be more specific about topologies below). Multicast

Using the Wireshark "Filter" field in the Wireshark GUI, I would like to filter capture results so that only multicast packets are shown. I've seen this post but that doesn't work for the GUI filter field. This Wireshark page shows how to filter out multicast, but not how to filter everything but multicast. Does anyone know of a simple statement that will do this? Thank you in advance! Just use this (eth.dst[0] & 1) . Multicast traffic is recognized by the least significant bit of the most significant byte of the MAC address. If 1, multicast, if 0, not. mojjj (eth.dst[0]&1) will filter both

We have a dockerized server application that is doing auto-discovery of physical appliances on the network by listening for multicast packets on port 6969. So we need our docker container to be able to receive these packets from devices outside the host, through the host, and in to the container. I've seen some similar issues and done a lot of reading but I'm still unable to get the server to respond to these multicast packets. I'm sitting on Wireshark watching network traffic, but I'm not a specialist. I know Docker creates a MASQUERADE address to make the traffic all look like it's coming

I'm trying to send a UDP Multicast Packet to: 230.185.192.108 so everyone subscribed will receive. A bit stuck. I believe it's broadcasting correctly, but can't seem to pick anything up with any client. Server: var news = [ "Borussia Dortmund wins German championship", "Tornado warning for the Bay Area", "More rain for the weekend", "Android tablets take over the world", "iPad2 sold out", "Nation's rappers down to last two samples" ]; var dgram = require('dgram'); var server = dgram.createSocket("udp4"); server.bind(); server.setBroadcast(true) server.setMulticastTTL(128); server.addMembership

Getting java.net.SocketException when trying to start a multicast provider: 2013-09-11 11:45:44,204 [main] ERROR net.sf.ehcache.distribution.MulticastRMICacheManagerPeerProvider: Error starting heartbeat. Error was: Can't assign requested address java.net.SocketException: Can't assign requested address at java.net.PlainDatagramSocketImpl.join(Native Method) at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) at java.net.MulticastSocket.joinGroup(MulticastSocket.java:319) at net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatReceiver.init

I'm trying to execute a simple example of Multicast sockets on Java. MulticastSocket s = new MulticastSocket(6789); InetAddress group = InetAddress.getByName("230.1.1.1"); s.joinGroup(group); This code generates the error: IP_ADD_MEMBERSHIP failed (out of hardware filters?) Any idea? Some Windows machines can experience this when the DHCP Media Sense feature is enabled (it is by default). To address this you may need to disable HDHCP media sensing as described here: http://support.microsoft.com/kb/239924 . It may also happen if the network interface does not support multicast. VPN interfaces