What did work for me was using pypcap instead of libpcap. So uninstall the
recommended "python-libcacp" and install "python-pypcap" instead.
lop...@gmail.com schrieb am Donnerstag, 2. Juli 2020 um 01:26:55 UTC+2:
> Solved by uninstalling python3 and installing 2.7.
>
>
> On Wednesday, July 1,
Solved by uninstalling python3 and installing 2.7.
On Wednesday, July 1, 2020 at 12:06:44 PM UTC+12, Zsolt Máté wrote:
>
> Did anyone find a fix for this?
> I'm in the same boat. Fresh raspberry pi image, clean install.
>
> sudo PYTHONPATH=/usr/share/weewx python
>
Did anyone find a fix for this?
I'm in the same boat. Fresh raspberry pi image, clean install.
sudo PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/interceptor.py --device=observer --mode=sniff
--iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
mapped packet: {'barometer':
The issue appears to be with passing of the interface, as changing the
default interface at line 310 of interceptor.py to the correct interface
and not specifying the interface in the weewx.cfg results in it working.
For me this is what I changed it to:
310 DEFAULT_IFACE = 'wlan0'
Calling it
Running the script directly works, so it is something todo with the Weewx -
Interceptor link that isn't quite right.
Example output:
sudo PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=sniff
--iface=wlan0 --filter="src 192.168.4.50 and dst
> scott,
>
> i still have no idea what changes you are making between runs, and which
> log output is associated with each change. it sounds like you are
> modifying the libpcap layer and the python pcap layer - i've seen at least
> two different pypcap versions in the log output (1.1 and
>
> i still have no idea what changes you are making between runs
It's pretty simple when you read...
python-libpcap is a debian package installed via apt. and python-pypcap is
the other package. I posted both outputs from each different ways to
supposedly run you driver and neither work
never mind I have trashed weewx and will go on with something else. It
worked for almost 3 years without a hitch.
On Sunday, January 12, 2020 at 5:15:06 PM UTC-8, mwall wrote:
>
>
>
> On Sunday, January 12, 2020 at 7:45:31 PM UTC-5, Scott Grayban wrote:
>>
>> Just to make sure that this isn't a
On Sunday, January 12, 2020 at 7:45:31 PM UTC-5, Scott Grayban wrote:
>
> Just to make sure that this isn't a error caused by me I installed a fresh
> raspian and weewx with your driver and my Ambient connected to hostapd and
> the same error popped up for both libpcap and pypcap installed.
Just to make sure that this isn't a error caused by me I installed a fresh
raspian and weewx with your driver and my Ambient connected to hostapd and
the same error popped up for both libpcap and pypcap installed. All virgin
here... the only change in that weewx.conf I made was changing the
This error is with python-libpcap installed
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing weewx version
3.9.2
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using Python 2.7.13 (default,
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 13:28:07 weewx-pi weewx[3792]: engine:
Shit wont post right here...
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing weewx version
3.9.2
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using Python 2.7.13 (default,
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Platform
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing weewx version 3.9
.2
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using Python 2.7.13 (default,
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Platform Linux-4.19.66-v7+-
Error with python-libpcap installed
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing weewx version 3.9
.2
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using Python 2.7.13 (default,
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Platform
On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>
>
> [StdWXCalculate]
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible
> values are:
> # hardware- use the value provided by hardware
> # software
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer
# See the file LICENSE.txt for your rights.
##
# This section is for general configuration information.
# Set to 1 for extra debug info, otherwise
On Sunday, January 12, 2020 at 3:29:40 PM UTC-5, Scott Grayban wrote:
>
> Well I can't find it. I have been through it a dozen times and just don't
> see it.
>
no one can help you if you don't post it! try posting your weewx
configuration file (the one that resulted in the 'engine: Loading
Well I can't find it. I have been through it a dozen times and just don't
see it.
On Saturday, January 11, 2020 at 9:30:16 PM UTC-8, mwall wrote:
>
> On Saturday, January 11, 2020 at 9:37:44 PM UTC-5, Scott Grayban wrote:
>>
>>
>> All of this points to the weewx engine but non of it makes any
On Saturday, January 11, 2020 at 9:37:44 PM UTC-5, Scott Grayban wrote:
>
>
> All of this points to the weewx engine but non of it makes any sense
> because I can run interceptor standalone.
>
actually, it points to a problem in your weewx configuration file.
--
You received this message
Doing a strace running weewxd I am getting this
stat64("/usr/share/weewx/swig_runtime_data4", 0x7e9d9ba8) = -1 ENOENT (No
such file or directory)
open("/usr/share/weewx/swig_runtime_data4.arm-linux-gnueabihf.so", O_RDONLY|
O_LARGEFILE) = -1 ENOENT (No such file or directory)
pycap starts to run but then exits causes weewx to fail again.
interceptor: ServerThread: start sniff server
engine: Loading service w
interceptor: MainThread: shutting down server thread
interceptor: MainThread: stop sniff server
interceptor: MainThread: unable to shut down server thread
On Saturday, January 11, 2020 at 4:51:30 PM UTC-5, Scott Grayban wrote:
>
> I tried pycap and that did run for a few seconds.
>
> Jan 11 00:39:13 weewx-pi weewx[3942]: engine: Loading station type
> Interceptor (user.interceptor)
> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread:
I was getting that error BEFORE I did the upgrade though.
On Saturday, January 11, 2020 at 4:54:18 PM UTC-8, mwall wrote:
>
>
>
> On Saturday, January 11, 2020 at 7:45:59 PM UTC-5, Scott Grayban wrote:
>>
>> Honestly I don't remember what version of Interceptor I was running
>> before. I did a
On Saturday, January 11, 2020 at 7:45:59 PM UTC-5, Scott Grayban wrote:
>
> Honestly I don't remember what version of Interceptor I was running
> before. I did a update because like I said I hadn't messed with it since
> last June so it could have been .46
>
> I did a apt upgrade after I
Actually your driver I used was around Mar 8, 2019 because that's when I
wrote the Hostapd doc.
https://github.com/weewx/weewx/wiki/hostapd-WiFi-setup-for-Interceptor-driver
On Saturday, January 11, 2020 at 4:42:13 PM UTC-8, mwall wrote:
>
>
>
> On Saturday, January 11, 2020 at 12:25:35 AM
Honestly I don't remember what version of Interceptor I was running before.
I did a update because like I said I hadn't messed with it since last June
so it could have been .46
I did a apt upgrade after I couldn't get weewx running but non of those
packages involved python.
On Saturday,
On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote:
>
> I did a restart tonight and weewx wouldn't start. Saw this in the logs and
> cannot figure out why this is happening. I checked all my configs and they
> are right, haven't touched then since last June.
>
>
I just disabled that skin also and used a different skin and same error.
On Saturday, January 11, 2020 at 4:19:58 PM UTC-8, mwall wrote:
>
> On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote:
>>
>> I did a restart tonight and weewx wouldn't start. Saw this in the logs
>>
I added a custom page to my skin and that was it. I removed the changes and
attempted a restart and it still wouldn't run.
On Saturday, January 11, 2020 at 4:19:58 PM UTC-8, mwall wrote:
>
> On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote:
>>
>> I did a restart tonight
On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote:
>
> I did a restart tonight and weewx wouldn't start. Saw this in the logs and
> cannot figure out why this is happening. I checked all my configs and they
> are right, haven't touched then since last June.
>
> weewx[5862]:
I tried pycap and that did run for a few seconds.
Jan 11 00:39:13 weewx-pi weewx[3942]: engine: Loading station type
Interceptor (user.interceptor)
Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: driver
version is 0.49
Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor:
No system update. Still running Raspbian 9 on it.
weeWX 3.9.2
Python 2.7.13
DRIVER_NAME = 'Interceptor'
DRIVER_VERSION = '0.49'
[Interceptor]
driver = user.interceptor
device_type = observer
mode = sniff
iface = wlan0
pcap_filter = src 10.3.141.62 and dst port 80
Jan 11 00:06:14 weewx-pi weewx[1417]: engine: Loading station type
Interceptor (user.interceptor)
Jan 11 00:06:14 weewx-pi weewx[1417]: interceptor: MainThread: driver
version is 0.49
Jan 11 00:06:14 weewx-pi weewx[1417]: interceptor: MainThread: device type:
observer
Jan 11 00:06:14
On Saturday, January 11, 2020 at 12:36:15 AM UTC-5, Scott Grayban wrote:
>
> Running the Interceptor manuall works just fine so I know it's not that
>
did you do a system update?
what version of weewx is this, what version of python, and what version of
the weewx-interceptor?
also,
Running the Interceptor manuall works just fine so I know it's not that
PYTHONPATH=/usr/share/weewx python weewx-share/user/interceptor.py
--device=observer --mode=sniff --iface=wlan0 --filter="src 10.3.141.62 and
dst port 80"
mapped packet: {'pressure': 27.741, 'outHumidity': 94.0, 'UV':
35 matches
Mail list logo
