I just set up an open-vpn server and a raspberrypi as the vpn client. The pi will try to reconnect if the connection dropped.
Andy On Tuesday, December 15, 2020 at 11:29:53 AM UTC-8 Sunray wrote: > Correction, the wind direction problem affected only the data archived in > the WLIP logger before Weewx came on line. > > But another issue is that the Weewx traffic seems to block the WLIP logger > from doing its regular uploading of data to Davis Weatherlink.com. Any > advice on this ? > > On Tuesday, 15 December 2020 at 18:39:22 UTC+2 Sunray wrote: > >> Progress report : Success! >> >> I was able to visit the cabin today for two hours (cold!) and installed >> the RPI hardware. After some headscratching due to a security camera on >> the same LAN, I was able to establish a RealVNC Connect session between the >> RPI connected by cable on the cabin's LAN and my laptop running on my >> cellphone's wifi hotspot. This enabled me to find out all necessary IP >> addresses including the Vantage Vue's Weatherlink IP address, which I >> needed for the WeeWx setup. >> >> I then did the reconfiguration of WeeWx from Simulator to Vantage Vue but >> did not manage to get a html update. A reduction of the Vantage's archiving >> interval from 2 hours to 5 minutes did not help. I could, however, using >> the weewxd command see that the LOOP packets now originated from the >> weather station and not simulated. So it looked promising! >> >> Back home, error messages suggested database errors. After some study I >> changed in the config file: >> >> - Driver model_type changed from 2 to 1 >> - Archive record generation from hardware to software. >> >> After these changes the html generation works fine! >> >> >> >> Thank you everyone for your advice and suggestions! I have one immediate >> issue - the wind direction graphs only display on a 16-point scale (22.5 >> degrees intervals). >> >> My next project will be to try to implement a realtime wind display >> (displaying each LOOP packet's data - advice welcome!) and to publish the >> weather data in a safe way. >> >> On Thursday, 10 December 2020 at 21:49:56 UTC+2 vince wrote: >> >>> Indeed. I used to fail2ban ssh attempts from other than my home ip >>> 'one' address. I had over 100 countries hitting me, with the vast majority >>> the usual APT countries we've all read about. That said, geoip fencing is >>> an inexact science and it's not that hard to make it look like a different >>> source address. >>> >>> I only let in US+CA+AU to my website due to too many attacks, by adding >>> geoip fencing to nginx which is pretty easy to set up. I also have a >>> custom fail2ban to ban anybody trying to look for php/wordpress stuff as >>> that's a big attack vector by the bots and script kiddies attacking >>> websites. >>> >>> I've locked myself out of my AWS box a couple times via messing up >>> fail2ban blocks of ssh incoming, requiring me to just nuke+rebuild it, so I >>> probably need another solution there. Thinking of just permitting my LAN >>> ip there once again, if I can come up with a second path in just-in-case. >>> Maybe I'll try WireGuard there and let my home box tunnel into the cloud >>> VM. Maybe. I'll have to think about it some more. >>> >>> It's an arms race and it's tiring even needing to fight it... >>> >>> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e9e9bb13-cefc-43ac-8927-5ddda089e829n%40googlegroups.com.
