Re: Multicast
"Tom Collins tom-lnEA/wrDJtNWk0Htik3J/[email protected] [rabbit-semi]" <[email protected]> Wed, 27 Jul 2016 14:11:17 -0400
| Newsgroups | gmane.comp.hardware.rabbit-semiconductor |
|---|---|
| Message-ID | <[email protected]> |
Steve, Good to know. I recently ran into trouble with Wireshark as well, and was really confused about what I was seeing. I was trying to monitor packets going in/out of an Ubuntu VM. One day, everything was working properly. A few days later, it was only capturing one side of the UDP connections. If I need to capture again, I'll be sure to restart Wireshark after starting everything. I thought I had tried doing that, but maybe I was just trying it after launching the VM. -Tom On Jul 27, 2016, at 12:48 PM, Steve Trigero seecwriter-/[email protected] [rabbit-semi] wrote: > Well, it turns out to be a wireshark issue. This latest version of wireshark is not as user friendly as it used to be. > > So check this out. I have an RM3900 setup to send a UDP datagram every 500ms to either a Multicast IP or to a > Broadcast IP. I send a command to the Rabbit telling it which protocol to use. > > I set the Rabbit to use broadcast then start wireshark. It captures all the broadcast traffic. I tell the Rabbit to switch > to using Multicast and wireshark goes silent. I close wireshark and reopen it. Presto! The multicast datagrams show > up in the capture. Switch back to sending broadcasts. Wireshark goes silent again. Close and reopen, and theystart > showing up again. > > So the Rabbit appears to be working, wireshark not so much. > > Steve