> On Apr 8, 2025, at 10:37, Steve Shuff <[email protected]> wrote:
>
> Hi Matthew ,
> Thanks for the reply.
>
> The CR1000 based station is on the home local network , the Raspberry pi
> running Weewx is on the same network.
> Assuming the interceptor is expecting to use two network interfaces I would
> have to remove the CR1000 from the home network and plug it into the
> Raspberry pi
> Alternatively, would the interceptor accept using one interface somehow, or
> is that not doable ?
there are two modes for intercepting wu traffic: (1) listen and (2) sniff.
when you listen, you make your station send data to weewx directly, either by:
- making the station think that the weewx host is weather underground by
spoofing dns
- mirroring network traffic from the station using firewall or network switch
settings
when you sniff, you must ensure that the station and weewx are on the same
network segment, and that any network hardware is not isolating devices. you
can test this using tcpdump on the machine on which weewx is running. just do
something like this:
sudo tcpdump src X.X.X.X and dst port 80
then you should see data from the station. there is no point messing with the
weewx configuration until you can see something using tcpdump.
the example assumes the computer on which weewx is running is a network bridge
- bridging the wifi and wired interfaces. if you are not bridging, and you are
using a wired interface, then it is quite probable that you will not see
anything - most network switches isolate traffic to client nodes, so any client
device will see only the traffic bound for it. some 'smart' switches have an
option to mirror traffic from one port to another. if you are using a wifi
interface, then you might be able to see traffic bound for other devices.
when you sniff, you will probably run into permissions issues. typically root
permissions are required to sniff network traffic. you can see this when you
run tcpdump - if you run as an unprivileged user, you won't see anything, but
if you run as root, you might. so in order to sniff traffic using the pcap
bindings, the weewxd process will probably need escalated permissions. the
simplest and least secure way to do this is to run weewxd as root. that was
the default for v4 installations. v5 installations default to running as a
non-root user, so if you sniff traffic you'll probably need to give the weewx
user permissions to do that.
--
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/B4F4B36B-83E9-4596-9B1F-352537201A95%40gmail.com.
