on the pi, is eth0 connected to the lw301 and eth1 connected to your LAN? you should consider using a 192.168.x.x address instead of 169.254.80.x. the 169.254 block is for self-assigned addresses - those are what you get when there is no dhcp server available. you can use the 169 address space, but that is kind of like saying 'pig' when you think you mean 'cow', but really mean 'meat'
your dhcp configuration is a bit odd - you're telling dhcp clients to use a router and dns that are on a different subnet you should have a configuration like this: LAN: 192.168.2.0/24 pi: - eth0 - wired connection to your LAN, 192.168.2.84 - eth1 - wired connection to lw301, 192.168.80.1 - dhcp listening on eth1, serving addresses in 192.168.80.2-254 - bind9 listening on eth1 - lighttpd listening on port 80 on eth0 - weewx-interceptor listening on port 80 on eth1 lw301: - wired connection to pi - 192.168.80.x given by the dhcp server on the pi you can route traffic from the private network to the LAN if you want to, but it is not necessary before you go tcpdumping, do a basic integrity check: 1) plug a computer into the private network port on the pi (instead of the lw301) 2) see what ip address the computer gets 3) do 'nslookup gateway.weather.oregonscientific.com' on the computer and verify that you get the ip address of the pi that is visible on the private network 4) do 'telnet gateway.weather.oregonscientific.com 80' on the computer - you should get a connection to the weewx-interceptor running on the pi if all that is ok, then unplug the computer, plug in the lw301, and everything should work 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.
