Since my RouterOS upgrade from 7.0.5 to 7.3.1 on my RB5009, my music players can’t play an audio track in it’s full length.
When a track is longer then 3 minutes, the track ends early and skips to the next track. This happens every ~3 minutes.
I’m using MoOde Audio music players on RaspberryPi’s as Digital Media Renderers (DMRs), A Synology 1515+ NAS as a Digital Media Server (DMS) and BubbleDS as a Digital Media Controller (DMC) on Andorid phones and tablets. I only play my local music files (flac’s) form the NAS.
I never had this when using RouterOS 7.0.5.
Any idea what might be the problem?
I’m considering a downgrade to 7.0.5, but I can’t find the package on the Mikrotik downloads page.
I found somthing on a German Mikrotik site: routeros-7.0beta5-arm.npk. Is this the correct package for downgrading to 7.0.5?
I’m not talking about the IGMP Proxy feature, just the IGMP querier that complements IGMP snooping. They’re related, but separate.
It’s part of the bridge configuration. In WinBox, it’s under Bridge → IGMP Snooping → Multicast Querier. In the CLI, “/interface bridge print” will give the info I’m after.
Also, the problem is most severe in the morning. During the day, the skips disappear and during the evening they are gone. My server (DMS) is restarted every night.
I must say, I was mislead by your post headline and the bolded text in your first message claiming it happens “every ~3 minutes”. That’s precisely what an IGMP querier does: cuts off data streams at fixed time limits, when no one steps up to claim they’re still wanted.
Now you say the cutoff time varies. How can you expect people to give useful answers when you don’t describe the symptom properly? Post #8 isn’t the time to be revealing this detail.
Since the problem is correlated with the restart period, what happens if you leave this DMS thingy running overnight? Does the good performance from the night before then continue into the next morning?
As far as I know, the bridge was created that way with protocol RSTP. I was not aware of this setting before printing the bridge settings.
I’m still in the process of finding patterns in this odd behavior. Today in Wireshark, I saw some suspicious packets from 2 devices (a Solar Power Inverter and a Thermostat) around the skips.
At the end of this week, I will further investigate the traffic on my LAN with Wireshark with precise timings of the skips. Then I will get back to you with some results.
Yesterday, I downgraded my RB5009 from 7.3.1 to 7.1.0. So far I had not one skipping problem.
Tried on 2 different streamers: both working perfectly again.
For 7.1.0, I restored the same configuration as used for 7.3.1.
So what causes the skips on 7.3.1?
Can you at least do us the favor of bisecting among the stable releases between? That will give us a single ChangeLog to scan, which may provide an answer.
By the way, I take it that turning off RSTP didn’t help? I didn’t expect that it would.
Try to bypass RB5009 with one switch for link the devices, if the problem persist, probably they have not any to do with RB…
Also seeing only the “bridge” print, instead of a full export, and a diagram how the devices are connected, is indicative of nothing…
And to say “before it didn’t do this with the xxx version”, I wonder why you updated it if it worked, and how do you make sure it’s the only updated software (and hardware) in the rest of the network…
Why update when it worked? That’s obvious (and you know that): new versions ideally should work better I’m a developer and I know that’s not always the case.
I switched to another ISP (KPN Fiber 1Gbps Up/Down) and upgraded RouterOS. Then this problem started.
First I thought it was the ISP, so I switched back to my old ISP (Ziggo, COAX) but the problem remained.
Then I think it’s obvious that the upgrade might caused the problem, because that’s the only change left.
I will try my old TP-link router and see if the problems remains.
ok…
I just start to read and instantly notice this:
the bridge has no admin mac, and no “none” as protocol mode, as already wroten from @erlinden
the DHCP server have the default lease time: 10 min, try to increase that to 1 hour
/ip dhcp-server network
missing netmask=24
this two??? you block your device to use the routerboard dns… despite the comment, block the LAN request, not the WAN…
and you specify /ip dhcp-server network … dns-server=192.168.0.1
these two rules are perfectly useless (also if uselessly block already blocked incoming from WAN) and block your devices
add action=drop chain=input comment=
“filiaal-conf: block DNS UDP-requests from WAN” connection-state=new
dst-port=53 in-interface-list=filiaal-interface-list-lan protocol=udp
add action=drop chain=input comment=
“filiaal-conf: block DNS TCP-requests from WAN” connection-state=new
dst-port=53 in-interface-list=filiaal-interface-list-lan protocol=tcp
I’m a developer and I know that’s not always the case.