-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[os-igmp-proxy] igmproxy not working since 18.1.3 - There must be at least 1 Vif as upstream #590
Comments
igmpproxy was revived after many years of no updates. Unfortunately, several "forks" existed that did things slightly different. For now you can bring it back with:
The better question: what is your upstream interface setup like? We would like to report this upstream. |
Just verified - same issue with 18.1.4. Installed igmpproxy from 18.1.2 and it works again. The configuration is as follows: a) physical interface - tagged (IEEE 802.1Q) ethernet interface w/ VLAN ID 7 igb2_vlan7: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 b) PPPoE on top of igb2_vlan7 (OUTSIDE_PPPOE) c) igmpproxy configuration (upstream interface): OUTSIDE_PPPOE upstream 224.0.0.0/4, 193.158.0.0/15 |
Just verified with 18.1.5 and included igmpproxy 0.2.1 from https://github.com/pali/igmpproxy/tree/0.2.1 - same issue. |
Same problem with 18.1.8. I haven't tested the workaround yet. |
Any update on this? Not beeing able to use igmpproxy is a huge disadvantage. I run 18.7 and when I try to perform "opnsense-revert -r 18.1.2 igmpproxy" I get, "Fetching igmpproxy.txz: .. failed". |
Yep, somebody is working on it: pali/igmpproxy#38
|
I tried updating and now I get a different error mesage.
My upstream interface should be re0_vlan102 and for my config it seems allright. Probably another thing that is worked on to be fixed or? @fichtner Tried tearing down the config and rebuilding in oposite direction. Now with downstream defined before upstream in my config igmpproxy is starting! So there is some logical faults in the code for checking presence of interfaces. 👍 |
Just for information: Working configuration at the moment: |
@thomasnilsen Did the patch worked in your machine? Could you give me feedback please? @fichtner There is a rollback in config.c, Please take care about it. If you are doing packages, please make another one with the change. |
@ljpaff I found that Things seemed fine to me when I fixed this, but I was unable due to lack of time to fully test this.. |
Note I have the same issue but I'm not using a pppoe interface. I'm a VLAN Tagged interface to Orange France for their IPTV service, the connection is established over VLAN 838 PCP 4 using DHCP. So I believe this isn't just PPPOE related. Regressing to v1.2 of IGMProxy and all is well |
@nivek1612 would you mind trying this version? https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz |
I'm not back in France at the minute and dont want to try over VPN just in case I break something :-) so let me ask one of the other guys to try |
no worries. I'll push this update in 18.7.3. I've harmlessly bumped MAX_IF from 40 to 100 to see if that makes a difference. I don't understand the upstream patch and this seemed the only thing that would imply a difference in parsing... |
For what its worth I have just set up this version of IGMPproxy https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/igmpproxy-0.2.1_1,1.txz on my UK system which uses PPPOE and I can now start the IGMPproxy service where as before I could not. I cant fully test it as I dont have access to the Orange IPTV service here in the UK |
@nivek1612 ok... so far so good. Due to a mistake on my side this update won't make the 18.7.3 cut, but that also gives time for others to comment. I also published the CFT in the relevant forum thread. :) |
Due to a build mixup the proposed fix did not make it into 18.7.3 but will be included in 18.7.4. |
Hello,
i am running OPNsense 18.1.3 with igmpproxy plugin 1.3 together with german telekom IPTV service.
The solution already worked with OPNsense 18.x just fine. After upgrading to 18.1.3 i recognized that the igmpproxy service does not come up.
The error in the log file is:
igmpproxy[20043]: There must be at least 1 Vif as upstream.
The igmpproxy service configuration is not changed, so there is one upstream interface (outside_pppoe) and one downstream interface (inside_untagged).
Maybe there is an issue with VLAN tagging, because the PPPoE interface is a tagged interface within an APU board. I tested to choose an untagged interface for the igmp upstream interface and the service started successfully. As soon as i switch back to my tagged PPPoE interface the service cannot start with the above error message.
Also tried to re-create the igmp configuration, but no change.
Any ideas or things i can check?
The text was updated successfully, but these errors were encountered: