Tcpdump needs permission if not running as root. This link gives info on how to give the permission. https://askubuntu.com/questions/530920/tcpdump-permissions-problem On Monday, December 23, 2024 at 3:26:37 PM UTC-5 Jean-Marie Schneider wrote:
> Thanks you Vince. > > I have an error : déc. 23 17:49:02 stationmeteo weewxd[48084]: ERROR > user.interceptor: tcpdump process died: tcpdump: wlan0: You don't have > permission to perform this capture on that device > (socket: Operation not > permitted) > > So error is located. But how can I solve that ? > Where I have to put that permission ? > > Sorry for this question, I am using Linux rarely ! > Le lundi 23 décembre 2024 à 18:57:42 UTC+1, vince a écrit : > >> What account are you running "python3 /usr/share/weewx/weewxd.py >> /etc/weewx/weewx.conf" under ? >> >> For logs, please read >> https://github.com/weewx/weewx/wiki/view-logs#journalctl and see if "sudo >> journalctl -u weewx" shows your logs. It always helps to set debug=1 in >> your weewx.conf file so please do so if you have not done so already. >> >> On Monday, December 23, 2024 at 9:00:43 AM UTC-8 Jean-Marie Schneider >> wrote: >> >>> Hello, >>> >>> My remark was about weewx, which when running was not pulling, or saving >>> the data's. Even if status message seams OK : >>> >>> 1. sudo systemctl status weewx >>> 2. â— weewx.service - WeeWX >>> 3. Loaded: loaded (/lib/systemd/system/weewx.service; enabled; >>> preset: enabled) >>> 4. Active: active (running) since Mon 2024-12-23 17:49:01 CET; >>> 27s ago >>> 5. Docs: https://weewx.com/docs >>> 6. Main PID: 48084 (python3) >>> 7. Tasks: 1 (limit: 9252) >>> 8. CPU: 156ms >>> 9. CGroup: /system.slice/weewx.service >>> 10. └─48084 python3 /usr/share/weewx/weewxd.py >>> /etc/weewx/weewx.conf >>> 11. >>> 12. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.restx: >>> PWSweather: Posting not enabled. >>> 13. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.restx: >>> CWOP: Posting not enabled. >>> 14. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.restx: >>> WOW: Posting not enabled. >>> 15. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.restx: >>> AWEKAS: Posting not enabled. >>> 16. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.engine: >>> 'pyephem' detected, extended almanac data is available >>> 17. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO __main__: >>> Starting up weewx version 5.1.0 >>> 18. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.engine: >>> Using binding 'wx_binding' to database 'weewx' >>> 19. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO >>> weewx.manager: Starting backfill of daily summaries >>> 20. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO >>> weewx.manager: Daily summaries up to date >>> 21. déc. 23 17:49:02 stationmeteo weewxd[48084]: INFO weewx.engine: >>> Starting main packet loop. >>> 22. >>> >>> I erase the system and install Raspberry Pi OS. From this new point, I >>> install weewx and interceptor following this page : >>> https://github.com/weewx/weewx/wiki/gw1000-recipe. >>> I created access point, and then modify weewx.con accordingly. >>> Again same behavior, with weewxd, data's are recorded. But with the >>> deamon there are not recorded ! >>> >>> Did have some one already see this behavior ? >>> >>> Thanks you for your help >>> Jean-Marie >>> >>> Le vendredi 20 décembre 2024 à 01:06:49 UTC+1, Robert Turner a écrit : >>> >>>> I think it is normal that weewxd is running. When I installed it the >>>> weewxd was automatically setup to run. I believe it would depend on how >>>> you >>>> installed it. Installing with apt it automatically sets up the daemon to >>>> run in the background. >>>> >>>> On Thursday, December 19, 2024 at 3:18:50 PM UTC-5 Jean-Marie Schneider >>>> wrote: >>>> >>>>> Sorry to be unclear, between my English and my explantation, even >>>>> simple situation to explain could come complicated ! >>>>> >>>>> Here is screen capture of the recorded data's from Monday : >>>>> [image: Capture d’écran 2024-12-19 210915.jpg] >>>>> The beginning of the trace correspond to weewxd running. Then I run >>>>> weewx as daemon, no data recorded in the database, and no trace. I did >>>>> this two times (weewxd, weewx, weewxd, weewx) with the same results. Now >>>>> only weewxd is running without interruption from that third run. >>>>> >>>>> I try to find error in the log's, but I see nothing. But perhaps I >>>>> have not open the good file ! >>>>> >>>>> So the driver is capturing data and stored in the database with >>>>> weewxd, but not with weewx... >>>>> >>>>> Le jeudi 19 décembre 2024 à 03:02:33 UTC+1, Robert Turner a écrit : >>>>> >>>>>> Are you saying that the data is not stored in the database? I was >>>>>> thinking that your post was a little unclear. I'm not too sure I can >>>>>> solve >>>>>> that problem which is strange if the driver is running capturing the >>>>>> data. >>>>>> >>>>>> On Monday, December 16, 2024 at 2:02:43 PM UTC-5 Jean-Marie Schneider >>>>>> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I did not found where is coming this issue. And surprisingly when I >>>>>>> run weewxd, data's are correctly save into the database ! >>>>>>> Any help will be appreciated ;) ! >>>>>>> >>>>>>> >>>>>>> >>>>>>> Le dimanche 15 décembre 2024 à 11:49:59 UTC+1, Jean-Marie Schneider >>>>>>> a écrit : >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Robert I use your Interceptor.py file, and your conf set as you. >>>>>>>> it is OK for receiving the data's : >>>>>>>> ~ $ sudo weewxd >>>>>>>> Using configuration file /etc/weewx/weewx.conf >>>>>>>> LOOP: 2024-12-15 11:44:09 CET (1734259449) 'altimeter': 'None', >>>>>>>> 'appTemp': '45.17646502340741', 'barometer': '30.11', 'cloudbase': >>>>>>>> '454.4292200824276', 'dateTime': '1734259449', 'dewpoint': '47.2', >>>>>>>> 'ET': >>>>>>>> 'None', 'heatindex': '46.603', 'humidex': '48.589000630562424', >>>>>>>> 'inDewpoint': 'None', 'maxSolarRad': '248.1637619033187', >>>>>>>> 'outHumidity': >>>>>>>> '99.0', 'outTemp': '47.5', 'pressure': 'None', 'rain': 'None', >>>>>>>> 'rainRate': >>>>>>>> '0.0', 'usUnits': '1', 'UV': '0.0', 'windchill': '47.5', 'windDir': >>>>>>>> '20.0', >>>>>>>> 'windGust': '4.4', 'windrun': 'None', 'windSpeed': '3.0' >>>>>>>> LOOP: 2024-12-15 11:45:14 CET (1734259514) 'altimeter': 'None', >>>>>>>> 'appTemp': '45.90871472340741', 'barometer': '30.11', 'cloudbase': >>>>>>>> '454.4292200824276', 'dateTime': '1734259514', 'dewpoint': '47.2', >>>>>>>> 'ET': >>>>>>>> 'None', 'heatindex': '46.603', 'humidex': '48.589000630562424', >>>>>>>> 'inDewpoint': 'None', 'maxSolarRad': '249.19217896926534', >>>>>>>> 'outHumidity': >>>>>>>> '99.0', 'outTemp': '47.5', 'pressure': 'None', 'rain': '0.0', >>>>>>>> 'rainRate': >>>>>>>> '0.0', 'usUnits': '1', 'UV': '0.0', 'windchill': '47.5', 'windDir': >>>>>>>> '7.0', >>>>>>>> 'windGust': '3.4', 'windrun': 'None', 'windSpeed': '1.7' >>>>>>>> >>>>>>>> Thanks you Robert for this updated file. >>>>>>>> >>>>>>>> Now run the daemon, the database is created but not data's are >>>>>>>> saved. I will search for this issu ! >>>>>>>> >>>>>>>> Had a good end of week end ! >>>>>>>> >>>>>>>> >>>>>>>> Le samedi 14 décembre 2024 à 23:36:16 UTC+1, Jean-Marie Schneider a >>>>>>>> écrit : >>>>>>>> >>>>>>>>> Robert, I will try tomorrow, after a good nigh hopefully ! >>>>>>>>> And I have a doubt about my installation of weewx. Let see >>>>>>>>> tomorrow... >>>>>>>>> >>>>>>>>> Le samedi 14 décembre 2024 à 22:16:40 UTC+1, Robert Turner a >>>>>>>>> écrit : >>>>>>>>> >>>>>>>>>> This is how my conf is set. >>>>>>>>>> [Interceptor] >>>>>>>>>> driver = user.interceptor >>>>>>>>>> device_type = wu-client >>>>>>>>>> mode = sniff >>>>>>>>>> iface = wlan0 >>>>>>>>>> pcap_filter = src 192.168.5.131 and dst port 80 >>>>>>>>>> >>>>>>>>>> Are you using the original interceptor.py or the one I modified? >>>>>>>>>> On Saturday, December 14, 2024 at 4:04:58 PM UTC-5 Jean-Marie >>>>>>>>>> Schneider wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks you Robert. I try it. >>>>>>>>>>> >>>>>>>>>>> I have set an AP, and this time I see the flow of data between >>>>>>>>>>> my station and wunderground.com : >>>>>>>>>>> 37 130.019998 10.42.0.13 34.232.250.77 HTTP 402 GET >>>>>>>>>>> /weatherstation/updateweatherstation.php?ID=ISAINT8047&PASSWORD=abc456&dateutc=2024-12-11+18%3A50%3A3&baromin=29.92&tempf=40.7&humidity=86&dewptf=36.7&rainin=0&dailyrainin=0&winddir=267&windspeedmph=3.2&windgustmph=4.9&UV=0&solarRadiation=0 >>>>>>>>>>> >>>>>>>>>>> HTTP/1.1 >>>>>>>>>>> Frame 5: 403 bytes on wire (3224 bits), 403 bytes captured (3224 >>>>>>>>>>> bits) >>>>>>>>>>> Ethernet II, Src: BouffaloLab_ab:75:d3 (b8:3d:fb:ab:75:d3), Dst: >>>>>>>>>>> RaspberryPi_5d:f0:b2 (2c:cf:67:5d:f0:b2) >>>>>>>>>>> Destination: RaspberryPi_5d:f0:b2 (2c:cf:67:5d:f0:b2) >>>>>>>>>>> Source: BouffaloLab_ab:75:d3 (b8:3d:fb:ab:75:d3) >>>>>>>>>>> Type: IPv4 (0x0800) >>>>>>>>>>> [Stream index: 0] >>>>>>>>>>> Internet Protocol Version 4, Src: 10.42.0.13, Dst: 34.232.250.77 >>>>>>>>>>> Transmission Control Protocol, Src Port: 53970, Dst Port: 80, >>>>>>>>>>> Seq: 1, Ack: 1, Len: 349 >>>>>>>>>>> Source Port: 53970 >>>>>>>>>>> Destination Port: 80 >>>>>>>>>>> >>>>>>>>>>> I perform a first modification with port setting : >>>>>>>>>>> >>>>>>>>>>> [Interceptor] >>>>>>>>>>> driver = user.interceptor >>>>>>>>>>> iface = wlan0 >>>>>>>>>>> port = 53970 >>>>>>>>>>> pcap_filter = src 10.42.0.13 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Weewxd run, as well weewx, but no data are obtained. I discover >>>>>>>>>>> that the port is dynamically set (next connexion, it is 53971, and >>>>>>>>>>> so one. >>>>>>>>>>> But, if a don't set the port, weewx did not start with the >>>>>>>>>>> following error : >>>>>>>>>>> >>>>>>>>>>> ERROR weewx.engine: Import of driver failed: [Errno 13] >>>>>>>>>>> Permission non accordée (<class 'PermissionError'>) >>>>>>>>>>> >>>>>>>>>>> I read the page of permissions >>>>>>>>>>> <https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-network-permissions> >>>>>>>>>>> and >>>>>>>>>>> allowing no method seams easy, especially as the port used by my >>>>>>>>>>> pws is >>>>>>>>>>> upper than 1024, the simpler will be to listen all the port upper >>>>>>>>>>> than >>>>>>>>>>> 1024, or some thing like this. But I have till now not found how to >>>>>>>>>>> set >>>>>>>>>>> that filter. Any help will be welcome ! >>>>>>>>>>> >>>>>>>>>>> Jean-Marie >>>>>>>>>>> Le jeudi 12 décembre 2024 à 00:16:27 UTC+1, Robert Turner a >>>>>>>>>>> écrit : >>>>>>>>>>> >>>>>>>>>>>> This version of the interceptor will be able to sniff the WLAN0 >>>>>>>>>>>> in AP mode. >>>>>>>>>>>> >>>>>>>>>>>> On Tuesday, December 10, 2024 at 4:22:47 PM UTC-5 Jean-Marie >>>>>>>>>>>> Schneider wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Thanks you for yours answer. >>>>>>>>>>>>> @vince : I am such of the IP. As already said, turning of the >>>>>>>>>>>>> WS let the ping without answer. And the four Devolo are recognize >>>>>>>>>>>>> by >>>>>>>>>>>>> Advance IP Scanner. They have a different IP than the WS. >>>>>>>>>>>>> >>>>>>>>>>>>> @Robert : I will learn how to set up an access point, and come >>>>>>>>>>>>> back with the results. >>>>>>>>>>>>> >>>>>>>>>>>>> Le mardi 10 décembre 2024 à 03:10:37 UTC+1, Robert Turner a >>>>>>>>>>>>> écrit : >>>>>>>>>>>>> >>>>>>>>>>>>>> I'm not completely sure of your network layout. I believe you >>>>>>>>>>>>>> can't sniff wifi traffic with just connecting to the same wifi >>>>>>>>>>>>>> network. >>>>>>>>>>>>>> Traffic from a device on wifi going to the internet is not >>>>>>>>>>>>>> rebroadcast to >>>>>>>>>>>>>> all devices on the wifi. If your device is connected to wifi and >>>>>>>>>>>>>> it's >>>>>>>>>>>>>> sending data to the internet it would go through the wifi router >>>>>>>>>>>>>> to the WAN >>>>>>>>>>>>>> port of the router. It wouldn't show up on the Wifi network or >>>>>>>>>>>>>> LAN. You >>>>>>>>>>>>>> possibly could tap it by mirroring the data on the WAN port. >>>>>>>>>>>>>> I did do this a little differently with my wifi weather >>>>>>>>>>>>>> station. I configured the pi to be an access point with its >>>>>>>>>>>>>> wireless >>>>>>>>>>>>>> adapter and the ethernet port connected to my router. I setup >>>>>>>>>>>>>> the access >>>>>>>>>>>>>> point on the pi to route to the ethernet port and connected the >>>>>>>>>>>>>> weather >>>>>>>>>>>>>> station to the pi access point. I modified the interceptor to >>>>>>>>>>>>>> use tcpdump >>>>>>>>>>>>>> to capture data on the pi wlan0. The modification was necessary >>>>>>>>>>>>>> because the >>>>>>>>>>>>>> interceptor was not able to sniff the wlan0 on the pi when it >>>>>>>>>>>>>> was in access >>>>>>>>>>>>>> point mode. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Monday, December 9, 2024 at 3:12:28 PM UTC-5 vince wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Your wireshark sniffer settings have to be incorrect. My >>>>>>>>>>>>>>> wild guess in the absence of a network diagram showing which >>>>>>>>>>>>>>> address is >>>>>>>>>>>>>>> where would be that your Devolo LAN PLC is the source address >>>>>>>>>>>>>>> to WU, not >>>>>>>>>>>>>>> the address of the weather station. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Monday, December 9, 2024 at 11:51:34 AM UTC-8 Jean-Marie >>>>>>>>>>>>>>> Schneider wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have set up a VEVOR 7-in-1 Wi-Fi Weather Station and >>>>>>>>>>>>>>>> would like to connect it to WeeWX. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I believe that the WeeWX-interceptor could be a solution, >>>>>>>>>>>>>>>> or at least worth trying! I installed WeeWX and the >>>>>>>>>>>>>>>> interceptor without any >>>>>>>>>>>>>>>> issues. Before attempting to connect my station, I want to >>>>>>>>>>>>>>>> verify the data >>>>>>>>>>>>>>>> being sent to wunderground.com, where my station transmits >>>>>>>>>>>>>>>> its data, or at least check if I can see them. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> My configuration is as follows: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - The weather station is connected via Wi-Fi to a >>>>>>>>>>>>>>>> Devolo Wi-Fi network (using Powerline Communication, PLC). >>>>>>>>>>>>>>>> - The reception is done by the Devolo LAN (through PLC). >>>>>>>>>>>>>>>> - The Devolo LAN is connected to my router. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> From my computer, which is also connected through the >>>>>>>>>>>>>>>> Devolo Wi-Fi, I determined the station's IP address using >>>>>>>>>>>>>>>> ZeNMAP (confirmed >>>>>>>>>>>>>>>> by powering off the station: when I ping the IP, I get no >>>>>>>>>>>>>>>> response from the >>>>>>>>>>>>>>>> station). Using Wireshark, I monitor the flow on the Wi-Fi >>>>>>>>>>>>>>>> (wlan0), and >>>>>>>>>>>>>>>> there is a lot of traffic. I applied a filter for the >>>>>>>>>>>>>>>> station's IP address, >>>>>>>>>>>>>>>> but then I observe nothing—no traffic!? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I also scanned the LAN, but still no additional data. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Next, I placed an Ethernet Network Tap between the router >>>>>>>>>>>>>>>> and the Devolo LAN. I connected a Raspberry Pi to this tap and >>>>>>>>>>>>>>>> monitored >>>>>>>>>>>>>>>> the LAN activity using tcpdump, but again, there was nothing >>>>>>>>>>>>>>>> related to my >>>>>>>>>>>>>>>> station. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm struggling to understand why! The station's data is >>>>>>>>>>>>>>>> visible on the Wunderground site, updated every minute. It's >>>>>>>>>>>>>>>> not a pigeon >>>>>>>>>>>>>>>> delivering the data... So, my question is: what am I doing >>>>>>>>>>>>>>>> wrong? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- 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/f0217a1a-fc74-4a1d-8e36-3ffdaf2bcbfan%40googlegroups.com.
