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-interceptor, I used the command:
sudo pip3 install pypcap
tcpdump shows that HTTP GET requests are making it to the Pi:
sudo tcpdump -i eth0|grep HTTP
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
18:19:17.350471 IP 192.168.1.179.4858 > ec2-52-35-193-72.us-west-2.compute.
amazonaws.com.http: Flags [P.], seq 1:530, ack 1, win 5840, length 529: HTTP
: GET /weatherstation/updateweatherstation.php?ID=XXXXXXXXXX&PASSWORD=
XXXXXXXX&indoortempf=75.7&tempf=79.0&dewptf=41.2&windchillf=79.0&
indoorhumidity=31&humidity=26&windspeedmph=2.5&windgustmph=6.9&winddir=353&
absbaromin=23.459&baromin=23.459&rainin=0.000&dailyrainin=0.000&weeklyrainin
=0.110&monthlyrainin=0.000&yearlyrainin=0.220&solarradiation=67.16&UV=0&
dateutc=2020-06-03%2000:19:16&softwaretype=AMBWeatherV4.1.9&action=updateraw
&realtime=1&rtfreq=5 HTTP/1.0
18:19:17.409177 IP ec2-52-35-193-72.us-west-2.compute.amazonaws.com.http >
192.168.1.179.4858: Flags [P.], seq 1:144, ack 530, win 27872, length 143:
HTTP: HTTP/1.1 200 OK
18:19:33.446953 IP 192.168.1.179.22265 > ec2-52-35-193-72.us-west-2.compute.
amazonaws.com.http: Flags [P.], seq 1:530, ack 1, win 5840, length 529: HTTP
: GET /weatherstation/updateweatherstation.php?ID=XXXXXXXXXX&PASSWORD=
XXXXXXXX&indoortempf=75.7&tempf=78.8&dewptf=40.1&windchillf=78.8&
indoorhumidity=31&humidity=25&windspeedmph=1.3&windgustmph=5.8&winddir=353&
absbaromin=23.459&baromin=23.459&rainin=0.000&dailyrainin=0.000&weeklyrainin
=0.110&monthlyrainin=0.000&yearlyrainin=0.220&solarradiation=65.45&UV=0&
dateutc=2020-06-03%2000:19:32&softwaretype=AMBWeatherV4.1.9&action=updateraw
&realtime=1&rtfreq=5 HTTP/1.0
18:19:33.504446 IP ec2-52-35-193-72.us-west-2.compute.amazonaws.com.http >
192.168.1.179.22265: Flags [P.], seq 1:144, ack 530, win 27872, length 143:
HTTP: HTTP/1.1 200 OK
My weewx.conf Interceptor config:
[Interceptor]
driver = user.interceptor
device_type = wu-client
mode = sniff
iface = eth0
pcap_filter = src 192.168.1.179 and dst port 80
promiscuous=True
Running tail -f /var/log/syslog I get the following:
tail -f /var/log/syslog
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: StationRegistry:
Registration not requested.
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: Wunderground:
Posting not enabled.
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: PWSweather: Posting
not enabled.
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: CWOP: Posting not
enabled.
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: WOW: Posting not
enabled.
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.restx: AWEKAS: Posting not
enabled.
Jun 2 18:25:26 weatherpi weewx[2284] INFO __main__: Starting up weewx
version 4.1.1
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.engine: Using binding
'wx_binding' to database 'weewx.sdb'
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.manager: Starting backfill
of daily summaries
Jun 2 18:25:26 weatherpi weewx[2284] INFO weewx.engine: Starting main
packet loop.
And then it just sits there...no packets are captured. Same problem as
documented above, but promiscuous mode doesn't seem to remedy the problem.
Any thoughts/suggestions?
On Saturday, February 24, 2018 at 5:53:43 PM UTC-7, 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
> 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.
>
>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/1f09aed0-3272-4042-ae6c-4207d5f468e1%40googlegroups.com.
