You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The result is it seems (seems...) to listen ok although I don't have any gear emitting data that it could hear. At a minimum things seem to run ok and the info above might be worth using when you get around to updating the toplevel readme for v5....
Re: how to get the non-privileged user weewx (or pi etc.) to listen on a privileged port, all I can find is references to set network capabilities on the python binary itself ala sudo setcap cap_net_raw+eip /usr/bin/python3.11 but to me that seems like a bit of a security risk. Quick test without doing that seems to listen ok in a dpkg installation on unprivileged ports such as 8000.
The text was updated successfully, but these errors were encountered:
added dpkg commands for getting the pcap items installed (tested in vagrant deb12) and also how to possibly permit the unprivileged user access to sniff or listen on privileged ports, which seems like a security risk to me. At a minimum it would make things quietly break if you ever updated your python version afterward.
Matthew - here's some documentation tweaks that might help folks on v5 get interceptor running under python3 on a pi....
Install and configure the prerequisites, assuming you have 'pip' available already...
Install the driver and enable it
And edit weewx.conf to fill in the config entry to listen....
The result is it seems (seems...) to listen ok although I don't have any gear emitting data that it could hear. At a minimum things seem to run ok and the info above might be worth using when you get around to updating the toplevel readme for v5....
Re: how to get the non-privileged user weewx (or pi etc.) to listen on a privileged port, all I can find is references to set network capabilities on the python binary itself ala
sudo setcap cap_net_raw+eip /usr/bin/python3.11
but to me that seems like a bit of a security risk. Quick test without doing that seems to listen ok in a dpkg installation on unprivileged ports such as 8000.The text was updated successfully, but these errors were encountered: