Sure thing. I didn't use wireshark. I used tcpdump. I was able to capture
the traffic from the station
12:29:05.092789 IP 192.168.5.131.57414 >
ec2-54-159-105-134.compute-1.amazonaws.com.http: Flags [.], ack 1, win 68,
length 0
12:29:05.101042 IP 192.168.5.131.57414 >
ec2-54-159-105-134.compute-1.amazonaws.com.http: Flags [P.], seq 1:523, ack
1, win 68, length 522: HTTP: GET
/weatherstation/updateweatherstation.php?ID=xxxxxxxx&PASSWORD=xxxxxxxx&indoortempf=66.9&tempf=32.5&dewptf=13.1&windchillf=32.5&indoorhumidity=65&humidity=44&windspeedmph=0.0&windgustmph=0.0&winddir=118&absbaromin=29.10&baromin=29.88&rainin=0.
00&dailyrainin=0.00&weeklyrainin=0.25&monthlyrainin=2.60&yearlyrainin=40.94&solarradiation=4.69&UV=0&dateutc=2024-11-21%2012:29:5&softwaretype=WS-1001%20V2.2.9&action=updateraw&realtime=1&rtfreq=5
HTTP/1.0
On Wednesday, November 20, 2024 at 9:01:47 PM UTC-5 vince wrote:
> Just do what I asked please. See what interface and src address it hears
> port 80 traffic hyou’re expecting on. It might even be loopback.
>
> On Wednesday, November 20, 2024 at 5:58:22 PM UTC-8 Robert Turner wrote:
>
>> Thanks for the help. I am sure the ip is correct. If I use arp -a I can
>> see the device
>>
>> (192.168.5.131) at 8c:18:d9:72:e1:43 [ether] on wlan0
>>
>> The weather station is the only device connect to the AP.
>>
>> I also know that is the DHCP lease given to the station
>> /var/lib/misc/dnsmasq.leases
>>
>> 732239204 8c:18:d9:72:e1:43 192.168.5.131 192 01:8c:18:d9:72:e1:43
>>
>> I also went ahead and made that lease in dnsmasq.conf so the ip would not
>> change
>>
>> dhcp-host=8c:18:d9:72:e1:43,192.168.5.131/24
>>
>> My station is the WS-1001 WIFI from ambient weather. I am starting to
>> think I may not get it to work.
>>
>>
>> On Wednesday, November 20, 2024 at 7:42:42 PM UTC-5 vince wrote:
>>
>>> I would take weewx out of the picture temporarily and try running
>>> wireshark and see what it hears, potentially fiddling with those options a
>>> bit. In the absence of info on what interface/where has which address,
>>> my wild guess is your src address might be wrong perhaps…
>>>
>>> On Wednesday, November 20, 2024 at 4:13:27 PM UTC-8 Robert Turner 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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/7ffa65f0-c71a-4193-aa40-23aee45389cfn%40googlegroups.com.
