Hi guys,
Thanks for your replies. I have had a bit of a look into Ping Watchdog's source, and it does indeed look elegantly small.
https://github.com/ericpaulbishop/gargo ... g-watchdog
My Gargoyle interface suggests I can install some of the smaller, 'theme' plugins, though I've not tried yet to see if they're 'disabled' somehow.
Looking at the Watchdog code, I can't see anything else that would be needed to install as a dependency - it all looks pretty much like the rest of Gargoyle. So I wonder if something is a little misconfigured somewhere regarding dependencies?
e.g. this all looks reasonable, just depending on gargoyle and libc, with install size of 3242 bytes.
Code: Select all
root@TP-LINK:/tmp/opkg-lists# gpkg info 'plugin-gargoyle-ping-watchdog'
Package: plugin-gargoyle-ping-watchdog
Version: 20131030
Install-Destination: Not Installed
SHA256sum: ffe0b8a11f7142ca1beb990d7bbab68f7101257f690007bb3e9c03b0a4135aff
Source: package/plugin-gargoyle-ping-watchdog
Size: 4191
Maintainer: Cezary Jackiewicz <cezary@eko.one.pl>
Installed-Size: 3242
MD5Sum: 07dab671459dfc9f0204c3a07f31122d
Description: Ping Watchdog
Architecture: all
Source-ID: gargoyle
Section: admin
Filename: plugin-gargoyle-ping-watchdog_20131030_all.ipk
Status: unknown ok not-installed
Depends: libc, gargoyle
But then running this implies the install may need a lot more for some reason? Perhaps more than really required?
Code: Select all
root@TP-LINK:/tmp/opkg-lists# gpkg info -v 'Required-Size,Required-Depends,Will-Fit' plugin-gargoyle-ping-watchdog
Package: plugin-gargoyle-ping-watchdog
Version: 20131030
Required-Depends: ip, tc, libjson-c, kmod-ipt-bandwidth, libxtables, uhttpd, gargoyle-firewall-util, kmod-ebtables, kmod-ipt-iprange, libpolarssl, kmod-ipt-webmon, ebtables, kmod-ipt-weburl, kmod-lib-crc-ccitt, kmod-ipt-nat-extra, iptables-mod-timerange, kmod-ipt-ipopt, kmod-lib-textsearch, kmod-sched-core, iptables-mod-filter, uci, wol, kmod-slhc, kmod-nf-ipt, ddns-gargoyle, kmod-nf-nat, libuci, kmod-bridge, libiptbwctl, iptables-mod-conntrack-extra, iptables-mod-imq, uhttpd-mod-tls, libblobmsg-json, gargoyle, iptables-mod-ipopt, iptables, kmod-nf-conntrack, qos-gargoyle, libnl-tiny, libip4tc, kmod-ipt-timerange, libip6tc, kmod-ipt-conntrack, kmod-nf-nathelper-extra, kmod-ipt-filter, kmod-pppox, kmod-ipt-extra, ewget, bwmon-gargoyle, kmod-pptp, kmod-ipt-core, libericstools, iptables-mod-bandwidth, libjson-script, webmon-gargoyle, iptables-mod-extra, iptables-mod-iprange, iptables-mod-webmon, kmod-iptunnel, iptables-mod-weburl, libc, libustream-polarssl, kmod-gre, iptables-mod-nat-extra, kmod-llc, kmod-ipt-imq, haserl-i18n, kmod-ppp, kmod-ipt-conntrack-extra, kmod-ipt-nat, kmod-stp, kmod-tun, libubox, libbbtargz, gpkg, kmod-sched, kernel (= 3.18.29-1-2cd8e0d6c90de5a5c905cc3193f1fc62), kmod-nf-nathelper
Will-Fit: false
Required-Size: 11862315
I've tried digging into the 'gpkg' code and a bit of hacking, but the data structure etc in load.c's load_package_data is a bit opaque to me without some debug tools etc.
In conclusion, I just wonder if Ping Watchdog's dependencies are a bit 'over the top' and that they might be reduced so as to be installable on smaller devices, and possibly even some other plugins might then work too?
Cheers!
Alex