May be you want to try tcptraceroute to track the way of the packets through your network.
tcptraceroute -p 80 oaklandweather.ddns.net tcptraceroute -p 80 45-30-89-101.lightspeed.sntcca.sbcglobal.net (tcptraceroute is not installed by default, so may be, you have to install it before.) And may be, there is an internal IP address of your weather server that plays a role in that. It may start with 192.168.... [email protected] schrieb am Mittwoch, 15. Dezember 2021 um 07:01:04 UTC+1: > On Tue, 2021-12-14 at 12:13 -0800, vince wrote: > > On Monday, December 13, 2021 at 11:02:07 PM UTC-8 [email protected] > wrote: > > I have a weather station that's visible on the web as > http://oaklandweather.ddns.net/weewx/index.html . Response from a web > browser is *very* slow, about 25 seconds to refresh. > It's also visible on my local network as > http://oaklandweather/weewx/index.html . Response from a web browser is > *very* fast, less than 250 ms to refresh. > > > From inside your LAN: > > - Try it by ip address: http://45.30.89.101/weewx/index.html and see > if it's still slow > - Alternately try > http://45-30-89-101.lightspeed.sntcca.sbcglobal.net/weewx/index.html > > > Here's what I checked - you might see if you get the same answer from > 'inside' your LAN... > > $ host oaklandweather.ddns.net > oaklandweather.ddns.net has address 45.30.89.101 > > $ host 45.30.89.101 > 101.89.30.45.in-addr.arpa domain name pointer > 45-30-89-101.lightspeed.sntcca.sbcglobal.net. > > $ host 45-30-89-101.lightspeed.sntcca.sbcglobal.net > 45-30-89-101.lightspeed.sntcca.sbcglobal.net has address 45.30.89.101 > > If it's still bad in all the ways above, you'd have to explain how you > punched Internet through back to your webserver on your LAN. > > > Here's what I get when I repeat your host commands. It looks the same as > what you get: > $ host oaklandweather.ddns.net > oaklandweather.ddns.net has address 45.30.89.101 > > $ host 45.30.89.101 > 101.89.30.45.in-addr.arpa domain name pointer > 45-30-89-101.lightspeed.sntcca.sbcglobal.net. > > $ host 45-30-89-101.lightspeed.sntcca.sbcglobal.net > 45-30-89-101.lightspeed.sntcca.sbcglobal.net has address 45.30.89.101 > > I checked the gateway firewall and found a major error. No-ip (see next > paragraph) was open to amito (my main desktop) but not to OaklandWeather > (the weewx/httpd server); it's not clear how no-ip could have worked at > all, maybe some stuff left in no-ip's server. After correcting, the system > behaves even more strangely than before. Using any of the views you propose > available through the web ( > http://oaklandweather.ddns.net/weewx/index.html), > <http://oaklandweather.ddns.net/weewx/index.html> the main web site > (.../weewx/index.html) is slow to start but refreshes nicely. It's slow to > change from the main site to monthly summary > (.../report=NOAA/NOAA-2021-12.txt) or to change back > > I'm using a service called no-ip to give a permanent name to the > OaklandWeather IP address, i.e. to my home network gateway. No-ip has > provided a client running on OaklandWeather that periodically informs the > no-ip server of my gateway's IP address. This seems to be working > correctly, otherwise no-one outside my local network would be able to > access the http server on OaklendWeather. OaklandWeather's own firewall > seems to be configured correctly, using the same reasoning. My network's > gateway to the internet has a firewall configured as follows. > > > -- > > Sincerely Jonathan Ryshpan <[email protected]> > > And God fulfills himself in many ways > Lest one good custom should corrupt the world. > -- Tennyson > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e3a9d5a2-52ff-4310-8fdb-58e21a1b72cbn%40googlegroups.com.
