> On Aug 7, 2016, at 6:09 AM, Tim Coote <[email protected]> wrote:
> 
> To Rich’s point wrt tooling. I’m having to construct similar tools, although 
> I tend to run them using ssh from a separate machine so that I’ve got 
> centralised control of the environment. That also has the benefit that I’ve 
> got a more complete toolkit than busybox et al (diff, git, rake, etc), making 
> it easier to create repeatable tests and compare results.

The system you're setting up sounds fascinating. It would be cool to have 
something written up about it on the wiki after you think it's solid. (After 
all, we are creating a system that *by definition* will have multiple routers, 
and it'll be good to have tools for minimizing administrative pain...)

But as we broaden the pool of people who try Homenet, we can't rely on them 
knowing as much as those reading this list. 

My hope is to have a baseline set of tools incorporated into the build. We can 
then say, "Just type this, and report the results back..." and have a hope of 
diagnosing the problem with the first set of results. (I want to avoid multiple 
interchanges, saying, "What does X say?" then get that result and say, "What 
does Y say?" That process is unproductive for developers, frustrating for 
users, and time consuming for all. For troubleshooting, I prefer to have One 
Script to Rule them All that's easy to use, even if it includes information 
that might be irrelevant to the problem at hand.)
 
The getstats.sh script could be the first of these. It collects baseline info 
for any OpenWrt router plus the commands that people mentioned in this "ipv6 
routing" thread. (listed below)

- Thoughts on this strategy?
- Thoughts on the list of commands to include in the script? 

Thanks.

Rich

PS I'm still looking for validation of the commands issued by getstats.sh. 
(http://www.homewrt.org/doku.php?id=getstats_script) They currently are:

cat /etc/banner
date
cat /etc/openwrt_release
uname -a
uptime
top -b | head -n 20
du -sh / ; du -sh /*
ifconfig
logread
dmesg
opkg status ip
opkg status ipset
opkg status hnet-full
ip -6 addr
ip -6 route
ip route show
ip -6 neigh show
[plus any others you include as command line arguments]

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to