Closed TheIncredibleMulk closed 3 years ago
What is the source of sACN in this test? How many active interfaces do you have? Could you check using wireshark that you arn't infact receiving the same sACN from multiple interfaces? Ideally could you post a wireshark capture using the interface "any" and a capture filter of "port 5568"
Tried two sources, home office is a MosaicTPC and sACN view running on other machines, yesterday I had an Elation Onyx NX2 (old version of the hardware) with the same issue.
See two attached wireshark captures,
Thanks for these, if we look at the MTPC capture (with the 'any' interface filter) we do see that packets arrive twice. For a demonstration of this select the first packet in the list with the filter "acn.dmx.seq_number == 140" We see that both times sequence 140 comes around it's received twice, thus triggering the SeqErr.
Now unfortunately what the 'any' interface capture doesn't show is the originating interface!
SeqErr and Jumps on Linux
sACNview v2.1.2 running on Ubuntu 20.04.1. x64
If the
listen on all interfaces
option is chosen, then the SeqErr and Jumps start stacking up. If a specific interface is chosen, things function as usual. I've cross tested with Windows10 and cannot replicate the issue. What other info can help provide?