On Saturday, October 8, 2016 at 7:08:44 AM UTC-7, mwall wrote:
>
> sam,
>
> the ngrep output looks good.  the strings 'mac=xxx&id=90&rid=xxx' is 
> exactly what the interceptor is looking for from a lw30x.
>
> i think that the 'Error response' output you're getting is from nc.  it 
> looks like nc is sending the raw ngrep output, including the T x.x.x.x:p -> 
> y.y.y.y:z [AP].  so the interceptor chokes on that and replies with error 
> code 400.
>
> so first you'll want to eliminate the "T ... -> ... [AP]" strings from the 
> ngrep output (is there an option to ngrep to do this?)  (it might be 
> possible with tcpdump too, but in that case you would be trying to get from 
> binary data back to the ascii name-value cgi pairs)
>
> then you'll want to use curl instead of ncat to send the data on.  that 
> will look something like this:
>
> ngrep ... | curl -s -d @- http://localhost:9999 > /dev/null
>
> sorry this is not yet all documented in the interceptor readme!
>
> m
>

Yes, I thought that it was griping about the first line in the ngrep output. I 
spent some time exploring possibilities of suppressing it somehow, but I don't 
see the option. Can weewx or the interceptor read from a file? I'm guessing 
this can be piped to a file, and the offending line could be removed or ignored 
by weewx. Otherwise I will work on seeing if there is another step that can be 
introduced intermediately that will essentially do the same thing every getting 
sent off to nc.

I guess there aren't too many/any others who are using this 
network-capture-to-interceptor arrangement, eh?

Let me know if you have any ideas on how to remove that offending line from 
ngrep. Once we work this out, we'll have a model to document :) I noticed that 
you have already improved the documentation, so we're headed the right 
direction!

Thanks again! 

-- 
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.

Reply via email to