Hi All,<br><br>Unfortunately, the current developer for freifunk-watchdog stated there isn't any documentation for that tool, and probably will never be. This means changes could be silently pushed into these tools, with end users not discover them until after their configuration breaks after OS upgrade. Possibly, this problem applies for the other freifunk tools packaged into OpenWRT, too.<br>
<br>Here is the source repo for the various freifunk tools presently packaged into AA, including the freifunk-watchdog package.<br><a href="http://svn.luci.subsignal.org/luci/tags/0.11.1/contrib/package/">http://svn.luci.subsignal.org/luci/tags/0.11.1/contrib/package/</a><br>
<a href="http://svn.luci.subsignal.org/luci/tags/0.11.1/contrib/package/freifunk-watchdog/src/">http://svn.luci.subsignal.org/luci/tags/0.11.1/contrib/package/freifunk-watchdog/src/</a><br><br>From the source for freifunk-watching, it looks like modification to support additional UCI options in /etc/config/freifunk-watchdog that enables/disables whether the watchdog monitor's wireless interfaces should be straightforward.<br>
<br>Kludging Commotion tools to accommodate ffwatchd's eccentricities isn't an appealing option in the long time, especially if the original dev decides later to silently push more changes that subsequently break Commotion's kludges, or that beget even uglier kludges.<br>
<br>Could I recommend one of these alternatives?<br><ol><li>Propose patches to the luci.subsignal to add UCI config options allowing the user to enable/disable whether watchdog touches any wireless interfaces. Hopefully, the original developer would welcome the increased attention.</li>
<li>If <a href="http://luci.subsignal.org">luci.subsignal.org</a> doesn't accept patches, fork the freifunk tools into a git repo managed by OTI, with the patches described in #1.</li><li>Don't use the Freifunk tools all. This options is unappealing, but it does at least avoid having to make possibly unsustainable kludges.<br>
</li></ol><br><div class="gmail_quote">On Tue, Apr 30, 2013 at 11:18 AM, Dan Staples <span dir="ltr"><<a href="mailto:danstaples@opentechinstitute.org" target="_blank">danstaples@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Also, Freifunk-watchdog is really controlling when it comes to the
wireless interfaces. When commotiond is in the middle of setting
everything up, ffwatchd will intervene and shut down the wireless
interfaces because the BSSID or channel doesn't match what's in
/etc/config/wireless at that particular moment. And that's a pain in
the ass.<br>
<br>
So while ffwatchd is good at keeping processes alive, we need to
figure out how to prevent it from messing up the networking. I
propose modifying /etc/init.d/network to include this start function
(changes in bold):<br>
<br>
start() {<br>
stop<br>
[ -e /proc/sys/kernel/core_pattern ] && {<br>
ulimit -c unlimited<br>
echo '/tmp/%e.%p.%s.%t.core' >
/proc/sys/kernel/core_pattern<br>
}<br>
service_start /sbin/netifd<br>
<br>
setup_switch() { return 0; }<br>
<br>
include /lib/network<br>
setup_switch<br>
<br>
sleep 5<br>
<br>
<b>cp /etc/crontabs/root</b><b> /etc/crontabs/root.backup</b><b><br>
</b><b> sed -i -e '/ffwatchd running/d' /etc/crontabs/root</b><b><br>
</b><b> /etc/init.d/freifunk-watchdog stop</b><br>
<br>
/sbin/wifi down<br>
/sbin/wifi up<br>
<br>
<b>mv /etc/crontabs/root.backup /etc/crontabs/root</b><b><br>
</b><b> /etc/init.d/freifunk-watchdog start</b><br>
}<br>
<br>
Would this be sufficient for keeping ffwatchd from meddling with the
wireless interfaces as commotiond configured everything and/or when
networking was (re)started?<span class="HOEnZb"><font color="#888888"><br>
<br>
-Dan</font></span><div><div class="h5"><br>
<br>
<div>On 04/30/2013 09:44 AM, Dan Staples
wrote:<br>
</div>
<blockquote type="cite">
<pre>So although Freifunk-watchdog is installed on Commotion-openwrt, we
don't really take advantage of it. It currently only watches dropbear
and cron. Is there any reason we shouldn't add entries for the core
Commotion components? Since we've been having problems with olsrd
inexplicably shutting down, I think the watchdog could help. Here's a
/etc/config/freifunk-watchdog I'd like to add by default to DR1:
config process
option process 'dropbear'
option initscript '/etc/init.d/dropbear'
config process
option process 'crond'
option initscript '/etc/init.d/cron'
config process
option process 'commotiond'
option initscript '/etc/init.d/commotiond'
config process
option process 'servald'
option initscript '/etc/init.d/serval-dna'
config process
option process 'avahi-daemon'
option initscript '/etc/init.d/avahi-daemon'
config process
option process 'olsrd'
option initscript '/etc/init.d/olsrd'
config process
option process 'dnsmasq'
option initscript '/etc/init.d/dnsmasq'
I didn't add firewall, in case folks want to turn that off. Is there
anything I'm missing? Any reason not to do this?
-Dan
</pre>
</blockquote>
<br>
<pre cols="72">--
Dan Staples
Open Technology Institute
<a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a></pre>
</div></div></div>
<br>_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br>
</div>