Netduma Kacper

Hi @MuRF, It would be great to know the exact packet that causes the issue but, unless its a broadcast or in some cases multicast packet, it will be only between Google speaker and the modem meaning your PC won't see it so tldr unfortunately Wireshark'ing on your PC won't cut it. At the moment we don't have a google speaker in the office. We ordered one and as soon as it arrives we will set it up. We could have a session in AEST daytime at the time of your choosing. However, It might be best to wait until we setup the speaker ourselves locally, since we will have full access of the unit it should be very easy to diagnose and fix. Thanks

Salut, désolé pour le retard, j'ai raté la notification Cela ressemble à un bug, je vais créer un ticket pour cela. En attendant, pourriez-vous s'il vous plaît fournir des étapes de reproduction et la description exacte du bogue ? Veuillez décrire votre configuration (comment tout est connecté, etc.) quand cela fonctionne et quand cela ne fonctionne pas, quels outils utilisez-vous, etc. ? Afin que nous puissions demander à quelqu'un de se pencher dessus.

Salut @Nofear La hiérarchisation du trafic place le trafic avant la file d'attente afin qu'il se déplace toujours aussi vite que possible. Nous permettons également à l'utilisateur de définir le "Wireless type" qui peut améliorer votre expérience si vous êtes en WiFi - cette option définira également la balise DSCP. En dehors de ce qui est décrit ci-dessus, nous ne modifions pas la balise DSCP. Si vous le voyez supprimé, il pourrait s'agir d'un bogue. J'espère que cela répond à votre question

Hi @mb94x@LagFix I'm a core dev and I"ve been working on this issue last weeks with a lot of help from @LagFix. Admittedly, it the bug is quite bizarre hasn't been fixed yet. We were are able to get Samsung TV working with QoS on, however, the root of the problem hasn't been fully pin pointed down yet. FYI @LagFix, I wasn't able to reproduce the problem without a TV as I speculated. Would you be available for another session tomorrow same time? I'd like try out a few other leads....

Yeah, 9:00AM is perfect

Hi @LagFix, I've prepared some potential fixes. Would you have time for another session same time tomorrow to test them out?

Hi @ddrive01, Weird, to my best guess sounds like the router confused your TV with the console and the wrong (or none) traffic was prioritised. QoS likely picked up the change only after your reset. This of course shouldn't happen. Let us know if it happens again, however, I do not think it is related to the issue at hand so please start a new thread in that case. Meanwhile, how many devices do you have on your network? Thanks

Hi @LagFix, Thanks for the Friday session, we narrowed the problem down significantly. I have a followup question: when you experience the problems with Samsung TV, does it only affect normal TV channels or apps like Netflix or Twitch alike?

Hi @LagFix, looking forward to our remote session today, let me know when you're ready.

Okay, great. I think sometime between 8-10 AM Colorado time tomorrow or Friday would be ideal. Let me know if that works for you.

Hi @LagFix. Sorry for the delay first of all, I saw the log but unfortunately there wasn't anything helpful in there. A remote session is definitely the way to debug this as we don't have a Samsung TV in the office. Could you please re-enable remote access to tech support and disable IPv6 if applicable? I will look around and see where the packets get lost. Ideally the setup would be just Modem -> R2 -> Samsung TV with minimal other traffic going through the R2 while you're reproducing the issue. Let me know if that's alright and when would work best for you.