I believe I discovered the issue. Well cursor told me the answer. It says the pcap library can't sniff packets with the wlan0 in access point mode. TCPDump has special capabilities that allow it to sniff the packets.
It also rewrote the code to use TCPDump instead of pcap. I will give that a try and see how that works. On Thursday, November 21, 2024 at 10:39:13 AM UTC-5 matthew wall wrote: > robert, > > well, it is not a permissions problem - you used 'sudo' when invoking the > interceptor driver directly. > > i vaguely remember pcap settings for promiscuity coming into play (your > tcpdump might use it by default?). there is a boolean 'promiscuous' option > for interceptor, but it is not mapped through to the direct invocation of > interceptor.py > > can you get any log messages when you run the driver directly? debug is > especially helpful - the sniff server spits out quite a bit of information. > > you might have to make some modifications to interceptor.py > > log messages nominally go to syslog, but systemd might hijack that. and > the interceptor driver is not aware of the newer logging mechanisms in > weewx. (it sets weewx.debug=1, but that probably won't get you full debug > logging - i know, i need to fix this in all of my extensions...) > > sorry i cannot do any testing and debug myself right now! > > m > > > On Nov 21, 2024, at 09:22, Robert Turner <rturn...@gmail.com> wrote: > > > > There isn't any network hardware between the station and where weewx > runs. Essentially weewx is running on the access point. On the pi wlan0 is > setup to be the access point. The station connects to that access point. > The packet sniffing is done directly on wlan0. > > > > I am able to see the traffic using sudo tcpdump -i wlan0. > > > > On Thursday, November 21, 2024 at 8:54:58 AM UTC-5 matthew wall wrote: > > robert, > > > > what is your network hardware? dumb switches isolate traffic, so one > physical port cannot listen to traffic on a different physical port. hubs > (remember those?), on the other hand, let every port see traffic on every > other port. if you have a managed switch, then you can probably use the > switch's management interface to mirror ports, letting one physical port > see the traffic happening on a different physical port. > > > > m > > > > > On Nov 20, 2024, at 19:05, Robert Turner <rturn...@gmail.com> wrote: > > > > > > I have weewx installed and the interceptor driver setup. I have a wifi > station that has built in wunderground updating. On my pi the station is > connected to the wlan0 which is setup as an accesspoint with routing setup > to eth0 which has internet access. > > > > > > The station is connecting and sending data to wunderground. I can see > it constantly updating on the site. With the interceptor driver in sniff it > is not getting the data. > > > > > > I ran the driver directly > > > > > > sudo PYTHONPATH=/usr/share/weewx python3 interceptor.py > --device=wu-client --mode=sniff --iface=wlan0 --filter="src 192.168.5.131 > and dst port 80" > > > > > > The ip address is correct for the station. I let it run for a period > of time and don't see any output. > > > > > > Thanks > > > > -- > > 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 weewx-user+...@googlegroups.com. > > To view this discussion visit > https://groups.google.com/d/msgid/weewx-user/ccb3557d-bf6c-42a3-93ac-3554ef484ab4n%40googlegroups.com > . > > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/45fa9781-d1f9-4e12-9cf9-4edf2eced35bn%40googlegroups.com.
