Todo #4672
closed
Update igmpproxy to latest version
Added by Andrew - almost 9 years ago. Updated about 8 years ago.
100%
Description
The currently installed version of igmpproxy is an early beta version from 2005, and has a number of issues. For example, IPTV and other multicast based services do not work correctly.
Upgrading to the latest igmpproxy fixed the issues for me. It would be great if the latest version could be rolled into the next release.
Please note that the command line options are slightly different for version 0.1, so a change is also necessary to the boot up script.
Please see the following thread for more information:
https://forum.pfsense.org/index.php?topic=93293.0
Thank you.
Updated by Tomas Ulicky almost 9 years ago
I support this idea, because it is not difficult to implement and solves many problem.
Currently Im changing binary manually...
Updated by Chris Buechler almost 9 years ago
Tomas: what are you changing the binary to, just the one from stock FreeBSD ports?
Updated by Tomas Ulicky almost 9 years ago
Yes, I have used this steps from forum (credit Andrew)
But I did pkg stuff on another pfsense and extracted only binary, because i dont want to have pkg stuff on production system.
OK, I think I've cracked it. I've posted the instructions to upgrade to igmpproxy 0.1 (no IPTV problems for me after upgrading!), but I can't be held responsible if you brick your pfSense box whilst doing it.
First you need to upgrade igmpproxy in the shell.
pkg
pkg update
pkg install igmpproxyHowever, once you've done this, because the command line options for igmpproxy 0.1 are different to the existing version on pfSense, igmpproxy won't start on boot. You therefore need a custom shell script to do it:
Create a new file called igmpstart.sh in /usr/local/etc/rc.d/
Use the vi editor to put the following line in it:
/usr/sbin/daemon igmpproxy /tmp/igmpproxy.conf
Make the file executable:
chmod +x igmpstart.sh
Then, when you reboot, all should be well.
Updated by Andrew - over 8 years ago
I've updated the post. There's a better way. Rather than creating igmpstart.sh, you can just edit the line in the script in pfSense that launches igmpproxy.
Use the editor in the GUI to open etc/inc/services.inc
Find the line which reads: "/* NOTE: -d4 means everything LOG_WARNING and smaller */"
Edit the line underneath to change -d4 to -v -v:
mwexec("/usr/local/sbin/igmpproxy -v -v {$g['tmp_path']}/igmpproxy.conf");
(n.b. the -v -v enables verbose logging, which might be useful if you're having problems. You can leave that out if you don't want your system logs to record igmpproxy activity.)
This is the way to implement it if igmpproxy 0.1 is being built into the next release of pfSense.
Tomas Ulicky wrote:
Yes, I have used this steps from forum (credit Andrew)
But I did pkg stuff on another pfsense and extracted only binary, because i dont want to have pkg stuff on production system.OK, I think I've cracked it. I've posted the instructions to upgrade to igmpproxy 0.1 (no IPTV problems for me after upgrading!), but I can't be held responsible if you brick your pfSense box whilst doing it.
First you need to upgrade igmpproxy in the shell.
pkg
pkg update
pkg install igmpproxyHowever, once you've done this, because the command line options for igmpproxy 0.1 are different to the existing version on pfSense, igmpproxy won't start on boot. You therefore need a custom shell script to do it:
Create a new file called igmpstart.sh in /usr/local/etc/rc.d/
Use the vi editor to put the following line in it:
/usr/sbin/daemon igmpproxy /tmp/igmpproxy.conf
Make the file executable:
chmod +x igmpstart.sh
Then, when you reboot, all should be well.
Updated by Andrew - over 8 years ago
p.s. just in case it wasn't obvious, you still need to update igmpproxy to version 0.1 - the above just relates to ensuring pfSense launches the new version of the service (as the command line syntax is different in 0.1).
Updated by Kill Bill over 8 years ago
Can this be done for 2.2.5 please? There is a whole galore of people complaining about this... https://forum.pfsense.org/index.php?topic=93293.0
Updated by Rainer Sinsch over 8 years ago
Andrew, your suggested change to /etc/inc/services.inc didn't work here. Strangely, it seems services.inc hangs at the mwexec call and the pfsense menu doesn't appear after booting on the console. It's like igmpproxy got started but didn't detach. I am no expert on FreeBSD/pfsense. I simply also changed mwexec to mwexec_bd and this seems to work here. Or should I use deamon to start igmpproxy?
Updated by Rainer Sinsch over 8 years ago
Ouupps. Of course I ment mwexec_bg and not mwexec_bd
Updated by Andrew - over 8 years ago
I think, as you say, igmpproxy is starting but not detaching. Obviously it needs to run in the background, so if mwexec_bg works across all versions of pfSense, then that seems the way to go.
I didn't make that change on my install of pfSense (from the Live installer CD) but it seemed to work anyway for me.
Updated by Chris Buechler over 8 years ago
- Tracker changed from Bug to Todo
- Subject changed from Please update igmpproxy to latest version (0.1) to Update igmpproxy to latest version
- Category set to IGMP Proxy
- Assignee set to Renato Botelho
- Target version set to 2.3
should be fine to switch to the stock FreeBSD port
Updated by Renato Botelho over 8 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Done, igmpproxy-0.1_2,1 is available on 2.3 repo
Updated by Victor Toni about 8 years ago
igmpproxy has been quite idle for some time at https://sourceforge.net/projects/igmpproxy/
There seems to be a new home for igmpproxy on GitHub, which includes a lot of the patches scattered all over the interwebs (including also some FreeBSD related patches):
https://github.com/pali/igmpproxy/
Is there any chance to get igmpproxy updated to this version?