Running weewx 4.1.1 on RasPi3 using weewx-interceptor current as of this
post. Weewx was installed using .deb instructions on Weewx install page
(Python3 option). I'm also running through a switch with port mirroring
from WS-2000 (802.11) to RasPi (Ethernet). When I installed
weewx-intercept
Where do you add the "promiscuous=1" to? and what was the syntax for it?
On Saturday, February 24, 2018 at 7:53:43 PM UTC-5, Brian Harvell wrote:
>
> 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
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
On Thursday, August 31, 2017 at 12:28:44 PM UTC-6, Eddie Lent wrote:
>
> I my set up is an acurite smarthub, a raspberry pi 1 running weewx and
> weewx-interceptor in sniff mode, port mirroring using netgear GS105Ev2.
>
> I can't seem to get data into weewx.
> I can run tcpdump on my router an
ok, here is the output, the weewx restart did not get it listening again:
Sep 7 11:56:12 raspberrypiFB systemd[1]: Starting LSB: weewx weather
system...
Sep 7 11:56:16 raspberrypiFB weewx[458]: engine: Initializing weewx
version 3.7.1
Sep 7 11:56:16 raspberrypiFB weewx[458]: engine: Using Py
Here is the syslog from right after a reboot. After waiting 20 min, I do
not see any new data in weewx webpage after the reboot.
Sep 7 09:45:56 raspberrypiFB systemd[1]: Starting LSB: weewx weather
system...
Sep 7 09:46:00 raspberrypiFB weewx[450]: engine: Initializing weewx
version 3.7.1
Se
The log shows that you appear to have multiple copies of weewx running -
with PID of 456, 362 and 559. Although the process with PID of 559 appears
to be running, it is still aborting a report run since it believes another
report process is running.
Can I suggest you ensure only one copy of we
While I was rerunning all those commands for my post, here is my syslog:
It appears that, it all of the sudden started getting packets while I was
running the tests. You can see that weewx started up 5.5 hours before it
started getting data from interceptor.
Aug 31 07:59:45 raspberrypiFB weewx
