[Feature Request] A way to troubleshoot rules

[laduke]

The rules engine is a little bit of a black box. You write some rules, then try to ping or netcat and see if it does what you intend.

If it was just printfs behind a compiler flag to start that'd be good for me!

Something like: matched {incoming,outgoing} packet to <ztaddress> because <rule x> - <packet headers>:?

I'm not too sure yet. We can iterate on it.

There is a little bit of code in already in Network.cpp, but it fizzles out in the future remote tracing system.

This would greatly speed up writing docs and doing support.