I wasnt trying to suggest hardware failures or anything like that, I was just asking about how things are hooked up on your network.
You second post seems to make it seem like your fedora system is acting as your router? So the bridge traffic is still flowing out into the internet and to the myacurite servers as if weewx wasnt there? On Friday, November 18, 2016 at 7:31:18 PM UTC-6, Radar wrote: > > bridge/smarthub -> netgear EN104 ethernet hub -> linux -> DSL -> web > > On Friday, November 18, 2016 at 7:00:31 PM UTC-6, Radar wrote: >> >> i sniff on a AMD Phenom 9750 Quad-Core 64-bit fedora 19 system to weewx >> 3.5.0 that use tcpdump and a perl script that had no trouble. its been >> running for over 3 years now >> on the same system was checking out the interceptor driver to weewx 3.6.1 >> in sniff mode that was getting the errors >> >> >> >> On Thursday, November 17, 2016 at 10:26:13 PM UTC-6, Jerome Helbert wrote: >>> >>> radar, >>> What exactly is setup? Are you running the driver as a sniffer on a >>> device like your router that is sniffing the traffic as it flows to the >>> myacurite servers, or are you hijacking the traffic to send it somewhere >>> else? >>> >>> If it's the former, I'm not sure the bridge is very happy when it >>> doesn't get responses from the server it is trying to reach, and that might >>> explain your excessive dhcp requests. I used to use a DNS hijack (still >>> running a sniffer, but not running on my router) that sent it to a server >>> running weewx as well as an apache server. When the apache server would be >>> down the bridge would actually ignore my DNS hijack and start talking to >>> the aculink servers directly... >>> >>> Suffice to say, it seems like acurite has some hardcoded defaults built >>> into their software if things on your network aren't functioning 100%... >>> >>> On Thursday, November 17, 2016 at 9:53:38 PM UTC-6, Radar wrote: >>>> >>>> thanks every one for the help and this great software >>>> >>>> >>>> On Wednesday, November 16, 2016 at 9:11:48 PM UTC-6, Jerome Helbert >>>> wrote: >>>>> >>>>> port 80 basically implies http, so that extra bit ought to be pretty >>>>> redundant... >>>>> >>>>> On Wednesday, November 16, 2016 at 8:20:16 PM UTC-6, Radar wrote: >>>>>> >>>>>> looks like its not going to die again, the only things i can find are >>>>>> changed the >>>>>> >>>>>> pcap_filter = "src 192.168.2.14 and dst port 80" >>>>>> to >>>>>> pcap_filter = "src 192.168.2.14 and dst port 80 and http" >>>>>> >>>>>> and don't know if this had any thing to do with but the bridge was >>>>>> asking dhcpd for a new address and it shouldn't have been i found 3 >>>>>> times >>>>>> in a quick glance at the log >>>>>> and i have it set to 1 day lease it was like the bridge was rebooting >>>>>> >>>>>> On Tuesday, November 15, 2016 at 6:21:43 PM UTC-6, Radar wrote: >>>>>>> >>>>>>> interceptor v0.7a it's been running for 23 hours now >>>>>>> >>>>>>> On Monday, November 14, 2016 at 10:47:16 AM UTC-6, mwall wrote: >>>>>>>> >>>>>>>> radar, >>>>>>>> >>>>>>>> could you try interceptor v0.7a (commit 5d0fe66) >>>>>>>> >>>>>>>> this logs more details about what is actually being parsed from the >>>>>>>> pcap sniffs >>>>>>>> >>>>>>>> m >>>>>>>> >>>>>>> -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
