#20443: igmpproxy will not start at boot up
-----------------------+----------------------------------
Reporter: paulc74 | Owner: developers
Type: defect | Status: new
Priority: high | Milestone: Chaos Calmer (trunk)
Component: packages | Version: Trunk
Resolution: | Keywords:
-----------------------+----------------------------------
Comment (by puleglot):
I don't know if it is possible to register triggers without spawning the
daemon. So quick and dirty fix is to just delete the following line:
{{{
[ -n "$has_upstream" ] || return
}}}
The only problem is that procd will keep trying to spawn the daemon while
upstream interface is down and spam the log:
{{{
Fri Sep 25 18:45:32 2015 user.err igmpproxy[6544]: There must be at least
2 Vif's where one is upstream.
Fri Sep 25 18:45:37 2015 user.err igmpproxy[6560]: There must be at least
2 Vif's where one is upstream.
Fri Sep 25 18:45:42 2015 user.err igmpproxy[6561]: There must be at least
2 Vif's where one is upstream.
Fri Sep 25 18:45:47 2015 user.err igmpproxy[6562]: There must be at least
2 Vif's where one is upstream.
Fri Sep 25 18:45:52 2015 user.err igmpproxy[6586]: There must be at least
2 Vif's where one is upstream.
}}}
--
Ticket URL: <https://dev.openwrt.org/ticket/20443#comment:6>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
