IGMPProxy1.3 is not starting

[franco]

It looks more like an issue with PPP instead of VLAN? At least igmpproxy shouldn't care whether a VLAN is under the PPP or not.


Cheers,
Franco

[micharambou]

You are right.
It appears that i forgot one more step to investigate the issue.

I just changed upstream interface configuration to a non tagged pppoe Interface -> igmpproxy init failed.

However, changing upstream interface to a tagged non pppoe interface (e.g. static configuration) brought igmpproxy back to life.

I will change the failure report on Github...

[frank_p]

This is the same error-pattern i have. PPPOE Upstream interface = not starting, static upstream interface = starting. I confirmed in git.

[franco]

Thanks guys, as promised in the upstream ticket here is an unpatched version of igmpproxy prior to pali's fork:

# pkg add -f https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.1_2,1.txz

It will not work with VLAN, but chances for PPP(oE) are 50-50 so we can see if this is a new bug or still a missing feature that our VLAN patch somehow fixed at the same time.


Cheers,
Franco

[odites999]

I have tried that package and the problem is still there while openvpn server is active so we're in the 'bad' 50...  ;)


Cheers,

[franco]

Can you post your igmpproxy config file for reference?


Thanks,
Franco

[franco]

You posted already, I see. No changes there since that post?

[odites999]

No, no changes. The igmproxy configuration is the same for one year.


Cheers,

[micharambou]

Appears to be fixed in 18.1.8

[franco]

There was no patch to address this yet, not sure what changed for you?


Cheers,
Franco

[micharambou]

Yes I'm somehow confused too.

I just made an upgrade to 18.1.8 on a previous installation and reset to factory defaults to get a clean start.

After setting up the configuration i was suprised, that igmpproxy came up without any issues...

Code Select Expand

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

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

phyint bridge0 downstream ratelimit 0 threshold 1
altnet 192.168.100.0/24

phyint igb0 disabled
phyint igb2 disabled


Code Select Expand


root@OPNsense:~ # igmpproxy -h
Usage: igmpproxy [-h] [-n] [-d] [-v [-v]] <configfile>

   -h   Display this help screen
   -n   Do not run as a daemon
   -d   Run in debug mode. Output all messages on stderr. Implies -n.
   -v   Be verbose. Give twice to see even debug messages.

igmpproxy 0.2.1
root@OPNsense:~ # opnsense-update
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (18 candidates): 100%
Processing candidates (18 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Nothing to do.
Your system is up to date.


Am I missing something?

[odites999]

I have just upgraded to 18.1.8 and the problem is still there. No changes.


Cheers,

[frank_p]

Same here... no changes. IGMPProxy isn't comming up.

best
Frank

[SEi]

Same here, igmpproxy 0.2.1 on a PPPoE upstream is not starting.
After reverting to igmpproxy 0.1, igmpproxy starts, but it only supperts IGMP v2, but for Deutsche Telekom EntertainTV I need IGMP v3, which means igmpproxy 0.2.1.

Best solution would be to fix the problem in the upstream-release of igmpproxy for FreeBSD.

As a dirty workaround, I will try this idea when I am back home today:

1. Setup an virtual IP on the ethernet Interface for the PPPoE-connection.
2. Brigde virtual IP and PPPoE, which should give me a static Interface as upstream for igmpproxy 0.2.1
3. igmpproxy 0.2.1 hopefully starts and provides LAN side IGMP v3


best regards,
Sven

[frank_p]

Hi SEi

has it worked? as workaround?

regards
Frank