search

opnsense / ports

OPNsense ports on top of FreeBSD
https://opnsense.org/
Other
157 stars 114 forks source link

igmp proxy error in log #127

Closed adevoss closed 2 years ago

adevoss commented 3 years ago

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

After igmp proxy configuration there are errors in the log and no pictures on screen connected to the set top box.

To Reproduce

Steps to reproduce the behavior: Install OPNsense Configure interfaces Configure firewall rules Configure igmp upstream and downstream

Expected behavior

Pictures on screen connected to the set top box.

Describe alternatives you considered

Same configuration works on pfSense (also on Proxmox).

Screenshots

If applicable, add screenshots to help explain your problem.

Relevant log files

igmpproxy[xxxx] select() failure; Errno(4): Interrupted system call opnsense[xxxx] plugins_configure newwanip (execute task : igmpproxy_configure_do())

Additional context

Add any other context about the problem here.

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 21.1.5 (amd64, OpenSSL). Protectli 6D/Proxmox 6.4 Passthrough network ports

fichtner commented 3 years ago

Interrupted system calls are normal. Working config elsewhere is circumstantial. Shouldn’t igmpproxy simply retry the operation?

adevoss commented 3 years ago

Working config elsewhere is circumstantial.

Sure. Only providing as much information as possible.

The log file messages are the only thing I could find indicating something is wrong besides having no picture (stream). Are there other things I can check?

fichtner commented 3 years ago

How many CPUs do you assign to the VM showing this issue? And how many on the one where this doesn’t happen.

We are looking at a normal condition in the igmpproxy source code and that is the same for both projects.

adevoss commented 3 years ago

How many CPUs

One CPU on both. They are not maxed out at all. Memory (512MB) not maxed out as well.

fichtner commented 3 years ago

If you can try with 2 CPUs or more the issue is likely worked around. OPNsense may have a higher base load / interrupt frequency due to more frequent use of the background daemon. Concurrency is too high so processes get interrupt signals which are harmless, but need to be gracefully ignored in the upstream software which doesn’t seem the case with igmpproxy.

A patch is probably rather easy to provide, but I am not at the office for another week.

adevoss commented 3 years ago

Tried 4 cores to be sure. No difference in the log messages. Maybe it has something to do with having two downstream subnets instead of only one. I have to test it more.

adevoss commented 3 years ago

Upgraded to 21.1.6 Compared my configuration over and over again with a working pfSense 2.1.5.

Now I got no pictures at all. No traffic from IPTV interface. Do have an IP address on IPTV interface (dhcp) Edit: Also the settop box has an IP.

What I don't understand is, why there are no firewall log lines on the IPTV interface in the 'Live view'.

adevoss commented 3 years ago

Did a factory reset to defaults (option 4). Configured Internet/VPN Client/IPTV. Same result: pfSense 2.5.1: Can watch TV. OPNsense 21.1.6: No TV. (settop box bypasses the VPN connection)

What is the purpose of os-igmp-proxy package in addition to igmpproxy? Their description is similar. Shoud os-igmp-proxy be removed to get it working?

Offtopic: I prefer the WebGUI, the Firewall Live View and random VPN connection of OPNsense so I would like to switch.

adevoss commented 3 years ago

With Wireshark I can see the following packets:

pfSense 2.5.1: From STB: Membership Reports to 224.3.2.6 From ISP: Announcements to 224.3.2.6 From ISP: Stream

OPNsense 21.1.6: Only Membership Reports to 224.3.2.6