Bug #8935
closed
IGMP Proxy not starting with PPPoE IF
Added by Johannes Wanink about 6 years ago.
Updated almost 6 years ago.
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)
See also: #8950 (has more logs)
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.
Alexandre Paradis wrote:
Vlan/sub-interface are also affected.
Same issue with "bridge" interface.
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.
- Status changed from New to In Progress
- 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
I can say that the vlans are working again.
Thanks !
New version merged to 2.4.4 branch
- Target version changed from 2.4.4-GS to 2.4.4-p1
- Target version changed from 2.4.4-p1 to 2.4.4-GS
- Target version changed from 2.4.4-GS to 2.4.4-p1
- Status changed from Feedback to Resolved
Also available in: Atom
PDF