so many options, so little time. dns option 1: dns on your router.
instead of putting a dns server on the pi, do it on your router. many routers provide a way to override dns entries before they relay/forward the queries. if your router can do this, then put an entry for gateway.weather.oregonscientific.com that maps to 192.168.2.84. then be sure that the lw30x is using the router as its dns server (if it is configured with dhcp, and the router is listed as the dns server in the dhcp configuration, then it should work). to test this, do: nslookup gateway.weather.oregonscientific.com on any computer on your network. if you configured dns correctly, you should get 192.168.2.84 dns option 2: dns on the pi configure bind as you have done on the pi. test it by doing this: nslookup gateway.weather.oregonscientific.com 192.168.2.84 that tells nslookup to use the pi as the dns server in the query. if that works, then your dns configuration is correct. if not, then diagnose the dns configuration separately. then you must make the lw30x use the pi as the dns server. the easiest way to do that is to route, not bridge, the interfaces on the pi. that way you can make one port on the pi a private network, make the pi a dhcp server for that, and in the dhcp configuration make the pi the preferred dns server. but what about the port 80, you ask? since the pi has multiple interfaces, you could run lighttpd on the LAN interface only. then you can run weewx-interceptor on port 80 of the private interface (the one to which the lw30x is connected). otherwise you must set up a reverse proxy in lighttpd that directs selected traffic to port 8080 (or whatever other port you choose for weewx-interceptor). 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.
