IGMPProxy1.3 is not starting

[frank_p]

Update to V18.1.4 went great. Thanks for that big job !!
FW run without any issue.

BUT

After Update to V18.1.4 (it run), i updated some hours later one of my firewall alias. After reload, the rules, the IGMPProxy (V1.3) is not longer starting (message in logfile: igmpproxy[62733]: There must be at least 1 Vif as upstream.

Config of IGMPProxy is not changed.

Can't find the issue.

Does anybody knows that issue?

[bringha]

Hi,

how does your config file look like?

can you check whether your /usr/local/etc/igmpproxy.conf has a valid upstream config?

Br br

[frank_p]

The config is not changed since months. So i guess, this should work under updated conditions also.

Please find attached the upstream parameter in ipgmproxy.conf.

quickleave
phyint pppoe0 upstream ratelimit 0 threshold 1
altnet 232.0.0.0/8
altnet 239.0.0.0/8
altnet 217.0.119.194/16
altnet 193.158.35.0/24


Just to add:
This runs in Telekom-Germany enviroment:
Connection via Draytec modem.
Networktype = BNG.
Modem is not making any manipulation.
pppoe session is opened from opensense
VLAN Tagging makes opensense.

br
frank

[nivok]

Hi frank,

That would relates to another thread I had responded... Since 18.1.4, igmpproxy is not working anymore while on VLAN... VLAN is by me set on the interface of the VM and not in OPNSense. That was working on 18.1.3.

I've here temporarily disabled the VLAN and it seems to be working again

Cheers,
Nick

[franco]

So OPNsense-terminated VLAN is not working in the 0.2 imgpproxy version? It's a bit of a surprise because I asked several testers with a use case to try this...

In any case, we can report this upstream, but I need a tester who is willing to work with the author.

https://github.com/pali/igmpproxy/issues

Also, it should work if you do this:

# opnsense-revert -r 18.1.2 igmpproxy


Cheers,
Franco

[frank_p]

Thanks Nivok.
Same effect with Tagging in OpnSense or Tagging in Modem.
IGMPProxy is coming with the error"There must be at least 1 Vif as upstream."

@Franco:
Not sure what the root cause is. But no difference where i do the tagging.
Interessting that it stopped working after i updated a firewall rule (this rule has nothing to do with IPTV)

I have no testing platform, but probably i can support somehow....

br
Frank

** Update**
reverted to V1.2 -> Igmpproxy is coming up and running

[frank_p]

Hi Nivok,

does your upstream- interface is a pppoe-interface ?
I changed the upstream-interface to an interface which is not pppoe, and igmpproxy started.
It seems to me, that igmpproxy is not starting when the upstream-interface is linked to an pppoe-interface.

br
frank

[nivok]

does your upstream- interface is a pppoe-interface ?

Hi Frank,

Nope, the IPTV is not on a pppoe upstream, but my second WAN is, maybe it is causing the issue... I haven't tested yet the downgrade of igmpproxy, will do it over the weekend... Also these days (since 18.1.4) I have loads of weird phenonemals with opnsense which almost always means I've to reboot... That's something else, but if I for instance re-tag my if with VLAN, then opnsense "somehow" looses the gateway untill restart (even though tagging is done on the switch/hypervisor side)

Cheers,
Nick

[odites999]

Same problem here. My igmpproxy.conf:

quickleave
phyint igb0 downstream ratelimit 0 threshold 1
altnet 192.168.1.0/24

phyint igb1_vlan2 upstream ratelimit 0 threshold 1
altnet 172.0.0.0/8

phyint pppoe0 disabled
phyint igb1_vlan3 disabled


Cheers!

[franco]

Would someone with the ability to test open a ticket with the author? https://github.com/pali/igmpproxy/issues

We do have an older patch set where this works as intended, maybe pali will spot the required change?

https://github.com/opnsense/ports/commit/1c9e9c2850670cdc2cd34c4a3bfa2b3faa981e17#diff-1261a7dfce4c25aa9003f5bf9d836136

I will provide test builds...


Cheers,
Franco

[frank_p]

Franco, all tester,

apologize that i am not able to test, or to provide test enviroment.

Not sure how some testing activities run.
Is the new fork V0.2 supporting IGMPV3 and VLAN ?

regards, Frank

[odites999]

If I disable the OpenVPN server, igmpproxy can be started manually (or rebooting) with no problem so, maybe, it's not VLAN related.


Cheers,

[gliddie]

Yep, same for me.

[frank_p]

same here....

[micharambou]

I can confirm the issue.

Upstream Interface pppoe on a vlan tagged interface. Downgrading igmpproxy resolves the issue. However - igmpproxy.conf remains unchanged since prior update.

Code: [Select]

root@OPNsense:~ # cat /usr/local/etc/igmpproxy.conf

##------------------------------------------------------
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint pppoe0 upstream ratelimit 0 threshold 1
altnet 224.0.0.0/24
altnet 87.141.215.0/24

phyint igb0 downstream ratelimit 0 threshold 1
altnet 192.168.100.0/24

System Log:

Code: [Select]

Apr 17 01:15:51 igmpproxy[41961]: There must be at least 1 Vif as upstream.
Apr 17 01:15:51 igmpproxy[74057]: select() failure; Errno(4): Interrupted system call
Apr 17 01:15:42 pkg-static: igmpproxy upgraded: 0.1_2,1 -> 0.2.1,1