Bug #8935
closed
IGMP Proxy not starting with PPPoE IF
0%
Description
After upgrade from 2.4.3 to 2.4.4 IGMP Proxy will not start anymore.
Stops with following Error:
igmpproxy[65102]: There must be at least 1 Vif as upstream.
It seems the new version cannot handle PPPoE Interfaces.
My Config:
##------------------------------------------------------
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint pppoe0 upstream ratelimit 0 threshold 1
altnet xxx.xxx.xxx.xxx/dd
altnet xxx.xxx.xxx.xxx/dd
altnet xxx.xxx.xxx.xxx/dd
phyint re1.200 downstream ratelimit 0 threshold 1
altnet yyy.yyy.yyy.yyy/dd
phyint re0.400 disabled
phyint re2 disabled
phyint re0.50 disabled
IGMP Proxy binary from pfSense 2.4.3 works fine with this configuration. (Copied from a 2.4.3 ISO, to my 2.4.4 installation)
Updated by
Updated by Tim Balmer over 5 years ago
Not sure this is the same issue as I reported in #8950, because in that bug IGMPProxy is not crashing (it runs untill I kill it myself), but it is not processing the incoming IGMP packets. While in this bug it look like IGMPProxy is not starting at all because it is not recognizing the PPPoE interface as an upstream.
Updated by Alexandre Paradis over 5 years ago
Vlan/sub-interface are also affected.
I had to use a physical interface to make igmp proxy to work.
do we have a comeback of bug https://redmine.pfsense.org/issues/6099 ?
Updated by benoit moreau over 5 years ago
Alexandre Paradis wrote:
Vlan/sub-interface are also affected.
Same issue with "bridge" interface.
Updated by Tim Balmer over 5 years ago
I now replaced the default igmpproxy binary on pfSense 2.4.4 by this version https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz, that for me resolves all issues, including those reported in #8950. OpnSense users apparently experienced similar issues after a recent IGMPProxy upgrade, found this thread while searching for a solution https://github.com/opnsense/plugins/issues/590
Updated by Johannes Wanink over 5 years ago
Tim Balmer wrote:
I now replaced the default igmpproxy binary on pfSense 2.4.4 by this version https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz, that for me resolves all issues, including those reported in #8950.
Thx!
Tried the binary, and looks good! Seems to be working.
(Binary is much bigger than the original: 159K -> this 39K -> 2.4.4 31K -> 2.4.3)
Updated by Tim Balmer over 5 years ago
Johannes Wanink wrote:
Thx!
Tried the binary, and looks good! Seems to be working.
(Binary is much bigger than the original: 159K -> this 39K -> 2.4.4 31K -> 2.4.3)
Good to hear your issues are also resolved with this newer version.
The reason that it is bigger is probably because pfSense 2.4.4 contains the igmpproxy 2.1.1 release while 2.4.3 still contained the 0.1_5 release, so that was a major igmpproxy upgrade. The version from the OpnSense repo is basically the same version as was orginally in pfSense 2.4.4 but now including the required bugfixes that are the result of the OpnSense bug report i mentioned in my previous post.
Updated by Patrick Monfette over 5 years ago
Tim Balmer wrote:
I now replaced the default igmpproxy binary on pfSense 2.4.4 by this version https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz, that for me resolves all issues, including those reported in #8950. OpnSense users apparently experienced similar issues after a recent IGMPProxy upgrade, found this thread while searching for a solution https://github.com/opnsense/plugins/issues/590
Fixed for me too by running this command (for anyone landing here, simply run this command to install a fixed version)
pkg add -f https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz
Thanks a lot for the infos @Tim !
Updated by Renato Botelho over 5 years ago
- Status changed from New to In Progress
Updated by Renato Botelho over 5 years ago
- Status changed from In Progress to Feedback
I've cherry-picked recent changes from FreeBSD ports tree. 0.2.1_1,1 will be available in the next round of 2.4.5-DEVELOPMENT snapshots for evaluation and cherry-picked to 2.4.4-p1 after confirmed fix
Updated by Alexandre Paradis over 5 years ago
I can say that the vlans are working again.
Thanks !
Updated by Anonymous over 5 years ago
- Target version changed from 2.4.4-GS to 2.4.4-p1
Updated by Anonymous over 5 years ago
- Target version changed from 2.4.4-p1 to 2.4.4-GS
Updated by Luiz Souza over 5 years ago
- Target version changed from 2.4.4-GS to 2.4.4-p1