Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jorisvervuurt

#1
Quote from: doktornotor on August 04, 2024, 10:25:36 AM
Yes - get a managed switch with IGMP snooping feature.

That was not my question, but thanks for your reply anyway. ;-)

There are multiple reasons why I decided to connect the two set-top boxes directly to the OPNsense box:
- The STBs only have 100Mb NICs and only one of them will be on at once which will consume around 14.4Mbps.
- The OPNsense box has enough NICs and is more than capable of running everything without a performance impact
- There's a 10Gb (core) switch connected to the OPNsense box to which I in theory could connect the STBs, but I don't have enough ports left on that switch

So, my question still stands.
Thanks in advance for anybody else to chime in! :)
#2
Is it possible to somehow enable IGMP snooping on a bridge interface?
I use a bridge to connect two (low-bandwidth) IPTV set-top boxes directly to my OPNsense box, but the multicast traffic is always sent to both STBs even if just one is turned on.

While this all works fine and doesn't seem to cause any problems, ideally I would like to have IGMP snooping enabled so the multicast traffic is only sent to the STB that is subscribed to it.

Is this possible?
In my case the bridge interface is opt3, bridge device bridge0.

I found this forum post regarding Proxmox (I know, it's not FreeBSD) and tried a few things but this doesn't seem possible on OPNsense / FreeBSD:
https://forum.proxmox.com/threads/linux-bridge-igmp-snooping-wont-drop-traffic.139322/

Thanks in advance!


#3
Quote from: 0xDEADC0DE on July 29, 2024, 01:19:57 AM
I have a problem with the widget.
It shows one temperature which is okay. But if it shows all, it's not readable. I cannot drag it longer and it doesn't autoexpand.



Yeah, same thing for me (I thought I posted a screenshot above, but apparently forgot).
#4
Quote from: franco on August 01, 2024, 11:34:40 AM
Just for clarity: since _10 is one more than _9 both have the same fixes for IGMP, but _7 doesn't have the two relevant IGMP fixes.

To confirm, everything works fine with _10 as well over here. ;-)
#5
Quote from: furfix on August 01, 2024, 11:51:40 AM
Sorry if I missunderstood you, but you mean this?

That is my WAN IPTV gateway and my IPTV LAN. For giving you a little more context, basically when I switch channels there is around 20m pike traffic for a few seconds, and then it's dead...same moment when the tv freeze. In the graph, basically I switch 3 channels.

That's not the issue this thread was about; it's probably a configuration issue on your side.
Please send a direct message to me so I can try to help you there (we don't have to continue in this thread since its unrelated).
#6
Quote from: furfix on August 01, 2024, 11:38:16 AM
Understood. With 9 the issue remains :(

Probably something totally unrelated, but the freeze it's only happening with channels below 100. From 96 and up, looks like it's working without problems. No freeze

Can you check the traffic graph please? Traffic should only very shortly increase and then drop back to 14.4Mbps (or ~8 for some lower quality channels). If it does drop back then you have another issue.

Also check the logs and filter on 'igmpproxy'.
#7
Quote from: franco on August 01, 2024, 11:34:40 AM
Just for clarity: since _10 is one more than _9 both have the same fixes for IGMP, but _7 doesn't have the two relevant IGMP fixes.


Cheers,
Franco

Alright, good to know that the increment means it includes everything from the earlier version.
I thought it was just a random number. ;-)

Just to be sure, I will test _10 later today as well.
#8
You'll probably have to contact the plugin developer about this since it's not an official plugin.
It could be that the MongoDB version has been updated and major updates cannot be performed without some manual commands.

I would personally not run it on your firewall though.
You could run it in Docker on a Raspberry Pi or a VM for example.

Here's my Docker Compose configuration:
https://gitlab.joris-vervuurt.com/-/snippets/2
#9
Quote from: newsense on July 31, 2024, 04:18:58 AM
Testing has been concluded and there's a known good kernel that fixes your issue, which you can install with

opnsense-update -zkr 24.7_10 && opnsense-shell reboot

Testing was done with _9 though, not _10.
Did you mean to write _9 or is _10 another follow-up?

I only tested with _9 which fixed the issue; haven't tested _10.
#10
Quote from: furfix on August 01, 2024, 11:09:33 AM
Just another KPN user here too. The TV just plays a few seconds and then freeze. I've tried the 24.7_10 kernel but didn't solve the issue.

Haven't tried the _10 kernel, but _9 does fix the issue:

opnsense-update -zkr 24.7_9 && opnsense-shell reboot

Easiest way to check if streams are released is to monitor the traffic graph. Each HD stream is around 14.4 Mbps. If you switch to the next TV channel, you should see the traffic graph shortly increase to 28.8Mbps and then pretty much instantly drop down back to 14.4 Mbps. It shouldn't keep increasing (which was the initial issue that has been fixed in the _9 kernel).
#11
Quote from: i81b4u on July 29, 2024, 05:37:27 PM
Good work!

Last question though ... on both LAN- and WAN-side I see that while one stream is about 14Mbps, when I switch channels the consumed bandwidth on the WAN-side doubles for about 3 minutes (to about 28Mbps) , while on the LAN-side it takes about half a minute before everything is back to normal. Is that expected behaviour? Never looked at it in this detail before, so I hope you don't mind me asking  ::)

Best regards.

In my case, traffic is dropping back pretty much instant (well, maybe a second) on both interfaces. I think something else is causing this in your case, not sure what though. Have you tried connecting the STB directly to the router instead of behind (non-IGMP snooping enabled?) switches to see if that changes anything?
#13
I just made a €50 donation to say thanks for picking this up so fast but also as a way to say thanks for OPNsense in general! Feel free to add me (Joris Vervuurt) to the list if you want to. 😄

Looking forward to the next update.
#14
Oh well, it's fixed now anyway. :P
Thanks again.
#15
Cool! I noticed only the IPv4 file has changes; I haven't checked the IPv6 file, but should that one be changed as well? :)

https://github.com/opnsense/src/blob/stable/24.7/sys/netinet6/in6_mcast.c