Just a note for those who come after me: There are no notes in the documentation at this moment regarding changing the interceptor default port, but to change it, you just need to add 'port = NNNN' so the driver stanzat of weewx.conf.
-Sam On Tuesday, October 4, 2016 at 11:28:57 PM UTC-7, Sam Roza wrote: > > > > On Thursday, September 29, 2016 at 8:00:39 PM UTC-7, mwall wrote: >> >> On Thursday, September 29, 2016 at 22:44:13 PM UTC-4, Sam Roza wrote: >>> >>> Yeah, you're right about switches, of course. Well, I guess it's time to >>> break down and buy a Pi... >>> >>> A Pi3, and some bridge work, and I should be up and running. >>> >>> Matt, would you suggest the DNS methods over the other capture and >>> scrape methods (like the tcpdump captures and whatnot)? If so, I'm >>> wondering how to get a Pi to do DNS resolution just for this one >>> device-though if I'm bridging the ethernet port to the wifi driver, I'm >>> guessing that it would pass through and not be possible. So then I'd be >>> back to the tcpdump methods, which everyone here seems to be quite familiar >>> with (and therefore, support might be a bit easier). >>> >> >> sam, >> >> the dns approach is easiest, but of course that is possible only if you >> control the dns on your network, or if you can configure the weather >> station to use a machine you control for its dns queries. is there any way >> to configure the os internet gateway? can you tell it which dns server(s) >> to use? if so, then install bind on the pi and bob's your uncle. >> >> if you have to use the pi3 to bridge, then you'll have to plug the os >> internet bridge into the pi ethernet port and connect the pi to your >> network via wifi. >> >> alternatively, add a usb-ethernet dongle to the pi and bridge from wired >> to wired. >> >> technically you do not even have to bridge - you just need to make the os >> internet bridge think that the pi is the os weather server. >> >> m >> > > Matt, > > I've got the hub in place, and the rPi set up. I have weewx installed, as > well as the interceptor driver. Unfortunately, it looks like the > interceptor's internal web server is causing issues with getting weewx > successfully up and running. > > I''m working off of your 'Example 4': > > ~~~ > > Example 4: weewx is running on host 'pi', which has a web server on port 80 > to display weewx reports. Configure the driver to listen on port 9999. Add a > reverse proxy to the web server configuration to direct traffic on port 80 > from > the device to port 9999. Add a DNS entry so that traffic from the device is > > sent to 'pi' instead of the cloud. > ~~~ > > Where my pi has weewx running on it, and I would like to run a web server > on 80 (I've installed lighttpd). I can't figure out where to set the > alternate port in the interceptor driver, though-the only place I could > find where this was even mentioned was in the interceptor.py file , where I > set 'DEFAULT_PORT = 9999' and then ran 'wee_config --reconfigure' again and > restarted everything, but that didn't open up the socket to 9999 like I had > been hoping it would. > > So now that I've got the hardware portion of this all figured out and in > place, I would sincerely appreciate if I could get a little bit of > direction as to getting interceptor and weewx working, if you don't mind. > I'm feeling a wee bit dense after grinding on this with no results this > evening. > > Thanks. >
