No WAN IP, error in Weatherlink and seems slow with Meteobridge 5.2 release. **solved**

[robr57]

Since update to SW-versie: Meteobridge 5.2 (Oct 30 2021, build 14621), FW 1.4 I have 2 problems.

1. The information screen no longer shows the WAN IP and it takes very long until this screen appears :

LAN IP: 10.0.0.16 WLAN IP: --
LAN Mask: 255.255.255.0 WLAN Mask: --
Gateway: 10.0.0.138 TX Traffic: 30.7 MB
DNS: 10.0.0.138 RX Traffic: 52.8 MB
WAN IP: Geen internet toegang Provider:

The Meteobridge PRO is hardwired to LAN. There is no strange info in the log page.

The good thing is that I still can get graphs through the remote link admin.meteobridge.com links.

2. The config page of the Networks for Weather Underground shows : Fout: Weather Underground: without further info and 2 red crosses before the Station ID and Key field.
In the Upload Status page shows a red cross with : Weather Underground: 2021-11-02 15:56:07 Error: 2021-11-02 15:55:54 wget: unable to resolve host address 'rtupdate.wunderground.com' (no more tries)
I checked my Weather Underground, it is still updated every few minutes, so the error is strange.

Any clue what is wrong ?

Regards, Rob

[robr57]

I have been looking further into the problem. I opened the Diagnostics, Network - Diagnostics

When I do Nslookup for Openwrt.org, the response is immediate.

Server: 10.0.0.138
Address 1: 10.0.0.138 Vigor.router

Name: openwrt.org
Address 1: 2a03:b0c0:3:d0:1 openwrt.org
Address 2: 139.59.209.225 openwrt.org

When I do Nslookup for wunderground.com, the response is also immediate.

When I do Nslookup for rtupdate.wunderground.com then it takes 42 seconds and I get the following response :

Server: 10.0.0.138
Address 1: 10.0.0.138 Vigor.router

Name: rtupdate.wunderground.com
Address 1: 169.63.130.179 rtupdate.wunderground.com
Address 2: 169.55.126.243 f3.7e.37a9.ip4.static.sl-reverse.com
Address 3: 169.61.113.60 3c.71.3da9.ip4.static.sl-reverse.com
Address 4: 169.63.130.180 b4.82.3fa9.ip4.static.sl-reverse.com
Address 5: 169.61.113.58 3a.71.3da9.ip4.static.sl-reverse.com
Address 6: 169.55.126.244 f4.7e.37a9.ip4.static.sl-reverse.com

When I do the same from a PC connected to the network, NSLookup A-record: rtupdate.wunderground.com is immediate with same result.

So there is appearently some strange thing going on in the Meteobridge sw.

I hope this helps you to fix this.

Regards, Rob

[jpouyaud]

Hi Rob,

like you I'm trying to get support here without success..

cheers

[robr57]

Problem remains, ADMIN where are you ?

The buffer also fills up to 100%. So, how can we fix this ??????

Code: Select all

Systeem
Platform:	Meteobridge PRO *  
RAM:	61500 kB totaal, 12128 kB beschikbaar (80% gebruikt)
Opslag ATP:	Internal 864 MB total, 495 MB free (43% gebruikt, 462.8 yrs)
SW-versie:	Meteobridge 5.2 (Nov 4 2021, build 14623), FW 1.4
Up-time:	7 Dagen, 22 uren, 56 minuten    Buffer: 998 onderdelen (100%)
Energieverbruik:	5.59V 394mA 2.20W

Furthermore, the Display on the Meteobridge PRO is also garbled.

[admin]

When there is no Internet connection that buffer will fill up. This is normal.

Looks like a routing or DNS problem to me. Did you change your router or provider?

Can you please share the remote login link with me, so that I can have a look?
Please mail credentials to "info(at)smartbedded.com"

[robr57]

I just mailed the access link with credentials.

Inseems that the DNS response is different and interpreted in the wrong way.

As written, in openwrt it is reproducable.

My provider is still the same but they have made changes in their backbone.

I tried different DNS servers though, but that didn’t help.

I hope you can find the problem.
Regards

[admin]

Thanks for giving me the chance to login to your Meteobridge.
What I can see is that the wget call to "api.ipify.org" (which is called when going to "System - Info" tab in order to get the WAN IP) takes ages on your Meteobridge while calling other URLs like "www.google.com" give an immediate response.

Code: Select all

root@MeteoBridge:~# time nslookup api.ipify.org
Server:    10.0.0.138
Address 1: 10.0.0.138 Vigor.router

Name:      api.ipify.org
Address 1: 3.232.242.170 ec2-3-232-242-170.compute-1.amazonaws.com
Address 2: 52.20.78.240 ec2-52-20-78-240.compute-1.amazonaws.com
Address 3: 3.220.57.224 ec2-3-220-57-224.compute-1.amazonaws.com
Address 4: 54.91.59.199 ec2-54-91-59-199.compute-1.amazonaws.com
real	0m 40.11s

-------------

root@MeteoBridge:~# time nslookup www.google.de
Server:    10.0.0.138
Address 1: 10.0.0.138 Vigor.router

Name:      www.google.de
Address 1: 2a00:1450:400e:810::2003 www.google.de
Address 2: 142.251.36.35 www.google.de
real	0m 0.02s

Looks to me like the routing of your Vigor router or provider is somehow broken.

[admin]

I just released an update that speeds-up "System - Information" tab by getting the WAN IP outside the web page build process.

[robr57]

Hi, thanks , this solves the Wan IP issue but the Wunderground issue remains.
Netwerk
MAC: xx.xx.xx.xx.xx
LAN IP: 10.0.0.16 WLAN IP: --
LAN Mask: 255.255.255.0 WLAN Mask: --
Gateway: 10.0.0.138 TX Traffic: 479.2 KB
DNS: 10.0.0.138 RX Traffic: 6.2 MB
WAN IP: 94.215.130.165 Provider: Ziggo B.V.

In Upload Status this issue remains :


no Weather Underground: 2021-11-20 17:55:59 Error: 2021-11-20 17:55:45 wget: unable to resolve host address 'weatherstation.wunderground.com' (5 more tries, next in 150 secs)

I also checked the status of my Weather Underground site, and it still shows actual data and is online, despite the reported issue. Strange....

I checked with openwrt NSLookup and it takes very long to get an answer for:

Server: 10.0.0.138
Address 1: 10.0.0.138 Vigor.router

Name: weatherstation.wunderground.com
Address 1: 169.63.130.179 weatherstation.wunderground.com
Address 2: 169.61.113.58 3a.71.3da9.ip4.static.sl-reverse.com
Address 3: 169.61.113.60 3c.71.3da9.ip4.static.sl-reverse.com
Address 4: 169.55.126.244 f4.7e.37a9.ip4.static.sl-reverse.com
Address 5: 169.63.130.180 b4.82.3fa9.ip4.static.sl-reverse.com
Address 6: 169.55.126.243 f3.7e.37a9.ip4.static.sl-reverse.com

All other lookups are within a second.

When I do same on other computer on the network, the response for weatherstation.wunderground.com is immediate.

[admin]

I guess the WU errors are time outs as the routing seems to be delayed/stuck sometimes. When you send at short intervals missing one item will not make any trouble and I also see that you defined 5 retries, so MB will give more than one shot but of course reports about any failed attempt.

Core problem is the routing, that takes very long to certain domains from within your LAN.

[admin]

I took another inspection on your MB PRO and it looks like you did change DNS to opendns. Now response time is totally fine:

Code: Select all

root@MeteoBridge:~# time nslookup api.ipify.org
Server:    208.67.222.222
Address 1: 208.67.222.222 dns.opendns.com

Name:      api.ipify.org
Address 1: 54.91.59.199 ec2-54-91-59-199.compute-1.amazonaws.com
Address 2: 3.220.57.224 ec2-3-220-57-224.compute-1.amazonaws.com
Address 3: 3.232.242.170 ec2-3-232-242-170.compute-1.amazonaws.com
Address 4: 52.20.78.240 ec2-52-20-78-240.compute-1.amazonaws.com
real	0m 0.20s
user	0m 0.00s
sys	0m 0.03s


root@MeteoBridge:~# time nslookup weatherstation.wunderground.com
Server:    208.67.222.222
Address 1: 208.67.222.222 dns.opendns.com

Name:      weatherstation.wunderground.com
Address 1: 169.63.130.180 b4.82.3fa9.ip4.static.sl-reverse.com
Address 2: 169.55.126.243 f3.7e.37a9.ip4.static.sl-reverse.com
Address 3: 169.55.126.244 f4.7e.37a9.ip4.static.sl-reverse.com
Address 4: 169.61.113.58 3a.71.3da9.ip4.static.sl-reverse.com
Address 5: 169.61.113.60 3c.71.3da9.ip4.static.sl-reverse.com
Address 6: 169.63.130.179 b3.82.3fa9.ip4.static.sl-reverse.com
real	0m 0.62s
user	0m 0.01s
sys	0m 0.01s

To be honest, I don't fully understand where these DNS issues come from, but at least there is a work around.