ASUS WL-330N3G Not Loading **solved**

[oturn]

Hi,

After several years of use, as of last night my ASUS WL-330N3G will not load the application stack from the Internet.

I have tried waiting, pressing the button to set defaults, setting defaults in OpenWrt, reflashing meteobridge-wl-330n3g-v1.2.sys using TFTP, then finally loading a configuration file from the cloud simulator. Of course all the while the WL-330N3G is actually online and pingable. I’ve run out of troubleshooting steps.

Any help would be appreciated!

[Mattk]

I wouldn't have attacked the defaults, OpenWrt, reflashing or any major surgery until the simple and common things have been exhausted.

Is the Internet connection all good? When was the last time the unit was rebooted, has any network/router changes been made since? When you say "the WL-330N3G is actually online and pingable" is this on the LAN side or WAN?

[tjones]

Having the same issue - just rebooted a few minutes ago to pickup the new code. Running same Asus HW as well.

Seeing lots of dropped packets as well.

IFCONFIG:
eth0 Link encap:Ethernet HWaddr 10:BF:48:B5:63:98
inet addr:192.168.99.5 Bcast:192.168.99.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6564 errors:0 dropped:722 overruns:0 frame:0
TX packets:1423 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5069723 (4.8 MiB) TX bytes:248038 (242.2 KiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


RESOLV.CONF:
# Interface lan
nameserver 8.8.8.8

ROUTE:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.99.1 0.0.0.0 UG 0 0 0 eth0
192.168.99.0 * 255.255.255.0 U 0 0 0 eth0

NSLOOKUP:
Server: 8.8.8.8
Address 1: 8.8.8.8 google-public-dns-a.google.com

Name: connect.meteobridge.com
Address 1: 2a01:4f8:10a:f98::4711 tau.meteobridge.com
Address 2: 88.99.105.253 tau.meteobridge.com

[oturn]

I wouldn't have attacked the defaults, OpenWrt, reflashing or any major surgery until the simple and common things have been exhausted.

Is the Internet connection all good? When was the last time the unit was rebooted, has any network/router changes been made since? When you say "the WL-330N3G is actually online and pingable" is this on the LAN side or WAN?

No changes. Internal and external Internet access is all normal. The unit was last rebooted about a week ago. It was still functioning normally on my WiFi when the problem began. After moving to Ethernet and reflashing, Meteobridge is still pingable. It just won't load the application stack from the Internet.

Apparently Meteobridge version 3.8 was released on 12/20, which seems more than coincidental. Considering tjones is having the same problem, I suspect this latest release was pushed to our barely supported WL-330N3G's and killed them.

[wvdkuil]

Earlier this year, after 3+ years service, my two ASUS WL-330 "died"as they lost memory / did not boot , within a few months after each other.
I do think that the manufacturer would be proud that they functioned 24/7 for multiple years. As these devices were not meant to be used that intensively. So I replaced them with new inexpensive boxes which, I assume, will also last for a few years.

I am not sure that the long use is also the cause in your case, but it was in my case for sure, as I always use either an USB-stick or "stick to version 3.x" s elected and not "get newest on boot".

Wim

[tjones]

Mine is still loading - over 12 hours. Going to let it run until it reboots or fully loads the new code.......

[Mattk]

.... Apparently Meteobridge version 3.8 was released on 12/20, which seems more than coincidental. Considering tjones is having the same problem, I suspect this latest release was pushed to our barely supported WL-330N3G's and killed them.

There is nothing "pushed" out (as such) version wise unless the user MB settings allow. "Stick to version xx" and "get newest on boot" should always be used to control updates.

[oturn]

.... Apparently Meteobridge version 3.8 was released on 12/20, which seems more than coincidental. Considering tjones is having the same problem, I suspect this latest release was pushed to our barely supported WL-330N3G's and killed them.

There is nothing "pushed" out (as such) version wise unless the user MB settings allow. "Stick to version xx" and "get newest on boot" should always be used to control updates.

If "Get newest on boot" was inadvertently selected, could an incompatible version get loaded on boot and cause this behavior? New firmware doesn't have a hardware check to prevent this?

If this is what happened, why didn't reflashing with a supported version (1.2 in the case of the WL-330N3G) bring the unit back to life? The landing page clearly shows I'm running 1.2. Why won't it load the application stack from the Internet?

[tjones]

I can confirm it's not a hardware issue on my end - network is fine, can ping the tau server and not dropping packets there on all packet sizes.

Something's up with the new code it's trying to download - dropping around 12% of received packets per the landing page and they are not CRC or local errors - something inside the packets is corrupt.

[admin]

It was an error in the build chain. Please try again, just released image should have this fixed again.

[oturn]

It was an error in the build chain. Please try again, just released image should have this fixed again.

I am operational again. Thank you!

[tjones]

I'm kind of operational - it loads but gets stuck on the License Page.....can't get past that.

System Message
Error: Open file for write failed (/root/meteobridge.conf): No space left on device
Error: Open file for write failed (/root/meteobridge.conf): No space left on device

[oturn]

I'm kind of operational - it loads but gets stuck on the License Page.....can't get past that.

System Message
Error: Open file for write failed (/root/meteobridge.conf): No space left on device
Error: Open file for write failed (/root/meteobridge.conf): No space left on device

I had the exact same error. Reflashing with meteobridge-wl-330n3g-v1.2.sys got me right back to normal. I did have to setup Meteobridge again, but that only took a few minutes.

[tjones]

Yup - reflash, reconfiguration. All good now.

[admin]

Sorry for the hassle.