I'm using a raspberry pi 3 and I noticed the interceptor was only able to sniff traffic while I was running tcpdump. If it stopped tcpdump then interceptor wouldn't see any more traffic. I noticed in the log it said promiscuous = 0 and once I added promiscuous = 1 to my config and it seems to work fine now, even after a reboot.
Brian On Sunday, September 10, 2017 at 2:37:01 PM UTC-4, mwall wrote: > > On Thursday, September 7, 2017 at 3:12:15 PM UTC-4, Eddie Lent wrote: >> >> ok, here is the output, the weewx restart did not get it listening again: >> > > very strange. i wonder if this is specific to the raspberry pi? > > if running tcpdump reliably makes the sniffing work, you could add a > single tcpdump invocation after you start weewx in the /etc/init.d/weewx > script. just invoke tcpdump for a few packets with the --count option. > > its a hack, but it might give you a reliable system until you can figure > out the root cause. > > is there any way you could try running the interceptor on a non-pi > machine? i've been running the interceptor in listen mode for acurite > packets on x86_64 and ppc hardware with no problems. it will be at least a > month before i could get a pi onto one of those networks to see if i can > duplicate what you're seeing. > > 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.
