IGMPPROXY stops working

[snotty77]

Hi,

I´m using pfsense in th e latest snapshot version on an alix-board. My IGMPPROXY stops working on every WAN IP change an also randomly while on heavy load (we have 2 receivers). the problem seems to be here araound since last year and I have hoped that ist would be solved with some of the updates. Now I have seen that this problem does not seem of bigger interrest so I ask if someone is into it. A similar problem is the using of the dhcp-client script in sbin. I always upgrade this file manually after every snapshot update because the problems with the slow channelswitching on IP-TV still are not solved.

Regards
Snotty

[cegner]

Same problem here with igmpproxy.

What is the recommended way to monitor and restart a service in pfSense?

Regards
Christof

[eri--]

Test new snapshots or try the change yourself https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/f206afb57e34ea30c43477deea3dfabfe10ad565

[cegner]

Hi,

I tried the 2.0-RC1 (i386) Mon Apr 4 06:38:40 EDT 2011 built, it still keeps crashing. Is there a way to monitor and automatically restart a service?

Regards
Christof

[eri--]

What do you mean by crashing!?
Logs, core dump?!

[cegner]

Hi,

during the last two days I did not see igmpproxy service stopping randomly any more. But the periodic reset of the PPPoE WAN interface still seems to be causing problems.

The periodic reset is set to 04:15. Here is an an excerpt of the system log:

Apr 7 04:15:59 	igmpproxy: ERRO: setsockopt IP_MULTICAST_IF 87.157.211.246; Errno(49): Can't assign requested address
Apr 7 04:15:59 	kernel: arpresolve: can't allocate llinfo for 255.255.255.255
Apr 7 04:15:44 	kernel: arpresolve: can't allocate llinfo for 255.255.255.255
Apr 7 02:15:33 	check_reload_status: reloading filter
Apr 7 04:15:29 	kernel: arpresolve: can't allocate llinfo for 255.255.255.255
Apr 7 04:15:23 	apinger: ALARM: IPTV(255.255.255.255) *** down ***
Apr 7 04:15:23 	apinger: ALARM: WAN(217.0.119.30) *** down ***
Apr 7 04:15:22 	php: : Resyncing OpenVPN instances for interface WAN.
Apr 7 04:15:20 	php: : Forcefully reloading IPsec racoon daemon
Apr 7 04:15:17 	igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 7 04:15:17 	igmpproxy: Note: RECV V3 member report from 93.231.23.69 to 224.0.0.22 (ip_hl 24, data 16)
Apr 7 04:15:15 	igmpproxy: Note: RECV Membership query from 93.231.63.254 to 224.0.0.1 (ip_hl 24, data 12)
Apr 7 04:15:14 	php: : phpDynDNS: (Success) IP Address Changed Successfully! (79.240.203.30)
Apr 7 04:15:14 	php: : phpDynDNS: updating cache file /conf/dyndns_wandyndns'csda1.ath.cx'.cache: 79.240.203.30
Apr 7 04:15:14 	php: : DynDns debug information: 79.240.203.30 extracted from local system.
Apr 7 04:15:14 	php: : DynDns: _checkIP() starting.
Apr 7 04:15:14 	php: : DynDns: Current Service: dyndns
Apr 7 04:15:14 	kernel: arpresolve: can't allocate llinfo for 255.255.255.255
Apr 7 04:15:14 	php: : DynDns: DynDns _checkStatus() starting.
Apr 7 04:15:13 	php: : DynDns: DynDns _update() starting.
Apr 7 04:15:13 	php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 87.157.211.246 WAN IP: 79.240.203.30
Apr 7 04:15:13 	php: : DynDns: Cached IP: 87.157.211.246
Apr 7 04:15:13 	php: : DynDns: Current WAN IP: 79.240.203.30
Apr 7 04:15:13 	php: : DynDns debug information: 79.240.203.30 extracted from local system.
Apr 7 04:15:13 	php: : DynDns: _checkIP() starting.
Apr 7 04:15:13 	php: : DynDns: _detectChange() starting.
Apr 7 04:15:13 	php: : DynDns: updatedns() starting
Apr 7 04:15:13 	php: : DynDns: Running updatedns()
Apr 7 04:15:13 	apinger: Starting Alarm Pinger, apinger(58425)
Apr 7 02:15:13 	check_reload_status: reloading filter
Apr 7 04:15:12 	apinger: Exiting on signal 15.
Apr 7 04:15:12 	php: : ROUTING: change default route to 217.0.119.30
Apr 7 02:15:08 	check_reload_status: Rewriting resolv.conf
Apr 7 02:15:01 	check_reload_status: Rewriting resolv.conf
Apr 7 02:15:00 	check_reload_status: configuring interface wan

Regards
Christof

[cegner]

Hi,

I just noticed that igmpproxy is not running on my box. There was no PPPoE reset, no log messages, no coredump.
How can I help you to track this issue?

Regards
Christof