Kev, MAYBE you need a good old fashioned hub in the middle.
A switch does jack to jack / port to port optimizations such that not every packet is seen on every jack. Also, if WiFi is involved and you have more than one access point, and the weather station and your weewx host are not connected via the same access point (or one is wired and the other is WiFi and there is a switch in the middle), then they too will be subject to the jack to jack / port to port optimizations at the switch. I say this because your weather station is sending to the server and your weewx interceptor is a "third-party" and your switch has no reason to think the conversation between the weather station and the server should be "shared" with your weewx host. Regards, Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On Apr 24, 2019, at 3:54 PM, Kev D <[email protected]> wrote: > > Another update: To eliminate any possible interference, I spun up an Ubuntu > VM to continue testing. This is the current setup: > > Weather station: 192.168.0.7 > Unbuntu/WeeWx/Interceptor: 192.168.0.8 > > I can confirm the router is sending data from the weather station to the > server as I when I run TCDUMP, you can see the data coming from 192.168.0.7 > > However, when I call the interceptor driver directly it does not capture any > of this data. This is both in sniff and listen modes. Does anyone know what I > missing? > > <Capture.JPG> > > > > Thanks in advance, > > Kev > >> On Tuesday, April 23, 2019 at 9:56:12 AM UTC-4, Kev D wrote: >> One thing I am confused on, the Weewx logs appear to be seeing data but the >> interceptor is not. I assume since I routed all data coming from the weather >> station IP to weewx this would have to be data from the WS right? When I >> disable this routing it will just return "empty queue". I feel like I am >> missing something here. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>> On Tuesday, April 23, 2019 at 9:30:23 AM UTC-4, Kevin De Lucca wrote: >>> The goal is to continue to send to wu while sniffing from weewx. I had the >>> router configured to the point where anything from the weather station IP >>> was sent to the observer and still would not sniff (WU site even had it >>> showing offline because of this). Maybe I should go the DNS hijack route >>> then just have weewx send the data to wu. Would this mean I need to change >>> the observer to listen mode rather than sniff? >>> >>> Thanks, >>> >>> Kev >>> >>>> On Tuesday, April 23, 2019 at 9:24:17 AM UTC-4, mwall wrote: >>>> >>>> >>>>> On Monday, April 22, 2019 at 3:09:22 PM UTC-4, Kev D wrote: >>>>> I am confident that the router is configured properly, but no matter what >>>>> I try I simply cannot get the interceptor driver to capture any data. On >>>>> a side note, I am also running PIHole on this device, but I had changed >>>>> the admin console listening port away from port 80. Does anyone have any >>>>> ideas for me? >>>> >>>> do you want the observer to send directly to wu, with weewx just sniffing? >>>> >>>> or do you want the observer to send directly to weewx? >>>> >>>> if you want the former, then the interceptor should be in sniff mode, and >>>> you need to configure the router so that weewx can see the traffic from >>>> the observer. >>>> >>>> if you want the latter, then you need to hijack dns so that queries for >>>> the weather underground servers resolve to the machine running weewx. >>>> >>>> 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > <Capture.JPG> -- 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.
