The Acurite Bridge is running it own web server on port 80. It basically just shows you the MAC address of the Bridge along with the firmware and hardware versions. Since my TCPflow command is sniffing any traffic and trying to parse it from that IP address on port 80 it grabs the traffic and kills weewx. For most uses its not a big deal. I have no need to see the firmware version or the hardware version.
Blocking the port 80 at the router would not work in my circumstance. I have a raspberry pi running wth 2 ethernet cards acting in bridge mode. It is between the accurate bridge and the router. It sniffs all traffic being sent from the acurite bride on port 80 that is headed to myacurite and parses that information, along with sending it off to Myacurite so I can still access that interface. Thanks, Brad On Saturday, November 12, 2016 at 10:17:47 PM UTC-8, Liz wrote: > > On Sat, 12 Nov 2016 21:55:45 -0800 (PST) > Brad Tucker <[email protected] <javascript:>> wrote: > > > Hello Matt, > > > > I starting thinking about the time stamp on the log I just sent, and > > that was right around the time I typed in the IP address to find the > > boot version and firmware version of the Acurite Bridge for RADAR. > > That got me thinking... So I went in and viewed that website again > > and sure enough thats whats killing interceptor/weewx... If you log > > onto the http server of the Acurite Bride it takes it down... > > > > Guess it makes since when you think about it... Not sure what could > > be done about it, but at least I know what not to do anymore ;) > > > > Take Care, > > Brad > > What port does the bridge use to communicate with their server? > Is there a possibility to block that port at your router? > > Liz > -- 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.
