On Saturday, November 12, 2016 at 9:27:33 AM UTC-5, Radar wrote:
>
> i don't send to WU and thought that maybe something in the http get might
> be messing it up so was running tcpflow because of this in the stack trace
> logdbg("SNIFF: %s" % _obfuscate_passwords(data))
>>
>>
>>>>
there are two modes of operation:
1) listen. in this mode, you must run tcpflow, tcpdump, or some other
packet-sniffing then feed that output to the driver.
2) sniff. in this mode, the driver does the sniffing itself, so you do not
have to run tcpflow, tcpdump, or anything else.
if you run the driver in sniff mode, what you do with tcpflow does not
matter, because the driver is not listening for input from tcpflow.
fwiw, your tcpflow command/configuration is dodgey - it is combining
multiple http GET requests into a single line.
the exception you posted is due to parsing of non-ascii characters in the
data stream from packet sniffing.
we always obfuscate passwords before sending any data to logs, just to be
safe.
m
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
