On Wednesday, March 27, 2019 at 5:51:49 AM UTC-4, mwall wrote:
>
>
>
> On Tuesday, March 26, 2019 at 10:10:31 PM UTC-4, Keith T wrote:
>>
>>
>> Anyone have suggestions on how to deal with either of these issues?
>>
>>
> now that the acu-link.com and myacurite.com servers are no longer
> working, you *must* run weewx-interceptor in listen mode if you want it to
> work with the acurite bridge (aka smarthub). when you run the interceptor
> in listen mode, it is passive - it does not interact with the smarthub.
> but since the acurite servers are no longer running, the smarthub will not
> do anything - it needs a server response before it will report any sensors
> or send their data. so you *must* make the interceptor be that server.
>
> so don't worry about installing pypcap - you don't need it
>
> as for how to make a dns record for acu-link.com and myacurite.com, that
> depends on your network configuration. can you you make the device that is
> doing dhcp for your network *also* be the dns server for your record? it
> can be a simple forwarder configuration.
>
> m
>
Thanks. That makes sense about sniffer mode. I now see that the
interceptor docs do say this, but they do so after showing an example of
how to run sniffer for acurite ('how to run the driver directly" section).
I don't think I can easily change my network to do the dns record by
re-configuring my current devices. Has anyone attempted to use something
like dnsspoof from the dsniff suite to spoof dns requests? I'll try
experimenting with that later.
K
--
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].
For more options, visit https://groups.google.com/d/optout.
