OpenWrt Forum Archive

Topic: Asus WL-500gP Stability Problem

The content of this topic has been archived on 25 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I got an Asus WL-500gP and installed Whiterussian RC5 on it.  I've applied the various nvram fixes for hardware differences on this router, and other than installing a few things from ipkg, this is still a pretty virgin openwrt install.

I'm posting because I'm having a stability problem.  It seems that if I leave wifi on, as a plain old access point, the router will eventually reboot itself.  It doesn't seem directly related to load.. it will happen under lots of wifi activity or just a bit of ssh'ing into the router from a laptop while watching television.  If I `ifconfig eth2 down`, eth2 being the wireless, then it is rock solid.

I configured remote syslogging, but nothing indicative of the problem shows up in my logs.  I've searched the forums a bit, but have not found any thread about a similar problem.  My apologies if this is a redundant thread -- has anyone else had this problem?

Thanks.





My nvram contents, for reference:

acc_num=0
app_running=0
apps_dl=1
apps_dl_seed=24
apps_dl_share=0
apps_dl_share_port_from=10000
apps_dl_share_port_to=10050
apps_dms=1
apps_dms_usb_port=1
apps_pool=harddisk/part0
apps_share=share
apps_ver=
autofw_desc_x=
autofw_enable_x=0
autofw_inport_x=
autofw_inproto_x=
autofw_num_x=0
autofw_outport_x=
autofw_outproto_x=
autofw_port0=
boardflags=0x0110
boardnum=45
boardrev=0x10
boardtype=0x042f
boot_wait=on
bridge_disable=0
cfe_wait_led_gpio=1
cfe_wait_on_restore=0
clkfreq=264
computer_name=WL500g.Premium
console_loglevel=7
custom_shutdown_command=stoprcasus
ddns_enable_x=0
ddns_hostname_x=
ddns_passwd_x=
ddns_server_x=
ddns_status_t=
ddns_username_x=
ddns_wildcard_x=0
default_boardflags=0x0110
default_http_passwd=
default_http_username=
default_lan_proto=dhcp_server
default_new_disk_action=no_action
default_physical_authentication_enable=disabled
default_primary_pool_name=
default_primary_share_name=
default_router_disable=0
default_start_page=start_system.asp
default_workgroup=WORKGROUP
dhcp1_enable_x=1
dhcp_dns1_x=
dhcp_domain=wan
dhcp_enable_x=1
dhcp_end=192.168.1.254
dhcp_gateway_x=
dhcp_lease=86400
dhcp_start=192.168.1.2
dhcp_static_x=0
dhcp_staticip_x=
dhcp_staticmac_x=
dhcp_staticnum_x=0
dhcp_wins=wan
dhcp_wins_x=
dl_ram_addr=a0001000
dmz_ip=
dmz_ipaddr=
dr_default_x=1
dr_static_matric_x=1
dr_static_rip_x=0
dr_staticgateway_x=
dr_staticipaddr_x=
dr_staticnetmask_x=0
dr_staticnum_x=0
early_startup_command=convertasus
eject_from_web=0
et0macaddr=00:17:31:ED:CE:D7
et0mdcport=0
et0phyaddr=30
et1macaddr=40:10:18:00:00:2d
et1mdcport=1
et1phyaddr=31
ezc_enable=1
ezc_version=2
filter_client0=
filter_lw_date_x=1111111
filter_lw_default_x=ACCEPT
filter_lw_dstip_x=
filter_lw_dstport_x=
filter_lw_icmp_x=
filter_lw_num_x=0
filter_lw_proto_x=
filter_lw_srcip_x=
filter_lw_srcport_x=
filter_lw_time_x=00002359
filter_maclist=
filter_macmode=deny
filter_wl_date_x=1111111
filter_wl_default_x=ACCEPT
filter_wl_dstip_x=
filter_wl_dstport_x=
filter_wl_icmp_x=
filter_wl_num_x=0
filter_wl_proto_x=
filter_wl_srcip_x=
filter_wl_srcport_x=
filter_wl_time_x=00002359
firmver=1.9.6.9
forward_port0=
ftp_running=0
fw_disable=0
fw_enable_x=1
fw_log_x=none
fw_lw_enable_x=0
fw_wl_enable_x=0
gpio6=robo_reset
gpio_0_name=soft_power_switch
gpio_3_name=power_enable
hardware_version=WL500gp-01-01-00-00
http_lanport=80
http_passwd=admin
http_username=admin
http_wanport=
httpd_die_reboot=
is_default=1
is_modified=0
kernel_gpio_init_out_3=1
kernel_gpio_init_out_6=1
lan1_lease=86400
lan1_netmask=255.255.255.0
lan_dhcp=0
lan_domain=
lan_gateway=
lan_gateway_t=
lan_hostname=
lan_hwaddr=
lan_hwnames=
lan_ifname=br0
lan_ifnames=vlan0 eth2
lan_ifnames_t=vlan0 eth1
lan_ipaddr=192.168.1.1
lan_ipaddr_t=
lan_lease=86400
lan_netmask=255.255.255.0
lan_netmask_t=
lan_proto=static
lan_proto_x=1
lan_route=
lan_stp=1
lan_wins=
landevs=vlan0 wl0
language=en
log_ipaddr=192.168.1.35
log_level=0
macfilter_enable_x=disabled
macfilter_list_x=
macfilter_num_x=0
machine_name=WL500gP
misc_conntrack_x=4096
misc_http_x=0
misc_httpport_x=8080
misc_io_mode=bcmgpio
misc_lpr_x=0
misc_natlog_x=0
misc_ping_x=0
no_br=0
ntp_server0=time.nist.gov
ntp_server1=
ntp_server=time.windows.com
ntp_servers=
os_date=May 31 2006
os_flash_addr=bfc40000
os_name=linux
os_ram_addr=80001000
os_server=
os_version=3.131.20.0
pmon_ver=CFE 3.91.23.0
preferred_lang=EN
primary_ifname=eth0
productid=WL500g.Premium
qos_enable_x=0
qos_ipaddr_x=
qos_maxbw_x=
qos_minbw_x=
qos_port_x=
qos_rulenum_x=0
qos_umaxbw_x=
qos_uminbw_x=
qos_uport_x=
qos_urulenum_x=0
reboot=
regulation_domain=0X10US
rescue_gpio=4
reset_gpio=7
restore_defaults=0
router_disable=0
scratch=a0180000
sdram_config=0x0062
sdram_init=0x0009
sdram_ncdl=0x408
sdram_refresh=0x0000
ses_enable=0
sh_num=0
sp_battle_ips=1
sr_enable_x=0
sr_gateway_x=
sr_if_x=
sr_ipaddr_x=
sr_matric_x=
sr_netmask_x=
sr_num_x=0
sr_rip_x=0
st_ftp_mode=1
st_max_user=6
st_samba_mode=1
st_samba_workgroup=WORKGROUP
startup_command=rcasus
stats_server=
swap_on=0
temp_lang=
time_interval=20
time_zone=GMT0
time_zone_x=
timer_interval=3600
upnp_enable=1
ure_disable=1
url_date_x=1111111
url_enable_x=0
url_keyword_x=
url_num_x=0
url_time_x=00002359
usb_audio_device=
usb_bannum_x=0
usb_device=
usb_disc0_dev=
usb_disc0_fs_path0=
usb_disc0_fs_path1=
usb_disc0_fs_path2=
usb_disc0_fs_path3=
usb_disc0_fs_path4=
usb_disc0_fs_path5=
usb_disc0_fs_path6=
usb_disc0_index=0
usb_disc0_path0=
usb_disc0_path1=
usb_disc0_path2=
usb_disc0_path3=
usb_disc0_path4=
usb_disc0_path5=
usb_disc0_path6=
usb_disc0_port=0
usb_disc1_dev=
usb_disc1_fs_path0=
usb_disc1_fs_path1=
usb_disc1_fs_path2=
usb_disc1_fs_path3=
usb_disc1_fs_path4=
usb_disc1_fs_path5=
usb_disc1_fs_path6=
usb_disc1_index=0
usb_disc1_path0=
usb_disc1_path1=
usb_disc1_path2=
usb_disc1_path3=
usb_disc1_path4=
usb_disc1_path5=
usb_disc1_path6=
usb_disc1_port=0
usb_ftpanonymous_x=1
usb_ftpbanip_x=
usb_ftpenable_x=1
usb_ftpmax_x=12
usb_ftpmaxuser_x=
usb_ftpnum_x=0
usb_ftppasswd_x=
usb_ftpport_x=21
usb_ftprights_x=
usb_ftpscript_x=
usb_ftpstaytimeout_x=240
usb_ftpsuper_x=0
usb_ftptimeout_x=120
usb_ftpusername_x=
usb_storage_device=
usb_web_device=
usb_web_flag=
usb_webactivex_x=7777
usb_webattach_x=1
usb_webcaption_x=Web Camera Live Demo!!!
usb_webdriver_x=0
usb_webenable_x=1
usb_webfresh_x=1
usb_webhttpcheck_x=0
usb_webhttpport_x=7776
usb_webimage_x=1
usb_webmode_x=1
usb_webmserver_x=
usb_webrectime_x=0
usb_webremote1_x=
usb_webremote2_x=
usb_webremote3_x=
usb_webremote4_x=
usb_webremote5_x=
usb_webremote6_x=
usb_webremote_x=LAN Only
usb_websecurity_date_x=1111111
usb_websecurity_time_x=00002359
usb_websecurity_x=0
usb_websendto_x=
usb_websense_x=1
usb_websubject_x=Motion detection alert!!!
vlan0hwname=et0
vlan0ports=1 2 3 4 5*
vlan1hwname=et0
vlan1ports=0 5*
vlan_enable=1
vts_desc_x=
vts_enable_x=1
vts_ipaddr_x=
vts_lport_x=
vts_num_x=0
vts_port_x=
vts_proto_x=
vts_protono_x=
wait_time=1
wan_desc=
wan_device=vlan1
wan_dns1_x=
wan_dns2_x=
wan_dns=
wan_dns_t=
wan_dnsenable_x=1
wan_domain=
wan_etherspeed_x=auto
wan_gateway=
wan_gateway_t=
wan_heartbeat_x=
wan_hostname=hobotrap
wan_hwaddr=
wan_hwaddr_x=
wan_hwname=
wan_ifname=vlan1
wan_ifnames=eth0 
wan_ipaddr=
wan_ipaddr_t=
wan_lease=86400
wan_mode_x=2
wan_nat_x=1
wan_netmask=
wan_netmask_t=
wan_pppoe_ac=
wan_pppoe_demand=0
wan_pppoe_idletime=1800
wan_pppoe_ifname=
wan_pppoe_keepalive=0
wan_pppoe_mru=1492
wan_pppoe_mtu=1492
wan_pppoe_passwd=
wan_pppoe_relay_x=0
wan_pppoe_service=
wan_pppoe_txonly_x=0
wan_pppoe_username=
wan_primary=0
wan_proto=none
wan_proto_t=
wan_route=
wan_route_x=IP_Routed
wan_status_t=
wan_unit=0
wan_vport=4
wan_wins=
wandevs=et0
watchdog=5000
web_hook_libraries=corewebhooks netwebhooks diskwebhooks winnet printwebhooks netregistration samplenetregistration samplehooks
wl0_akm=none
wl0_channel=11
wl0_closed=0
wl0_crypto=tkip
wl0_ifname=eth2
wl0_infra=1
wl0_mode=ap
wl0_radio=1
wl0_ssid=cruznet
wl0_wep=disabled
wl0id=0x4320
wl_afterburner=off
wl_akm=
wl_antdiv=-1
wl_ap_isolate=0
wl_auth=0
wl_auth_mode=open
wl_bcn=100
wl_chan_list=1 2 3 4 5 6 7 8 9 10 11
wl_channel=0
wl_closed=0
wl_corerev=
wl_country=
wl_country_code=
wl_crypto=0
wl_dfs_postism=60
wl_dfs_preism=60
wl_dtim=1
wl_frag=2346
wl_frameburst=0
wl_gmode=1
wl_gmode_protection=auto
wl_gmode_protection_x=0
wl_guest_auth_mode_1=open
wl_guest_crypto_1=0
wl_guest_enable=0
wl_guest_key1_1=
wl_guest_key2_1=
wl_guest_key3_1=
wl_guest_key4_1=
wl_guest_key_1=1
wl_guest_phrase_x_1=
wl_guest_ssid_1=guest
wl_guest_wep_x_1=0
wl_guest_wpa_gtk_rekey_1=0
wl_guest_wpa_psk_1=
wl_hwaddr=
wl_ifname=
wl_infra=1
wl_key1=
wl_key2=
wl_key3=
wl_key4=
wl_key=1
wl_lazywds=0
wl_macapply_x=Both
wl_maclist=
wl_maclist_x=
wl_macmode=disabled
wl_macnum_x=0
wl_maxassoc=128
wl_mode=ap
wl_mode_ex=ap
wl_mode_x=0
wl_mrate=0
wl_net_reauth=36000
wl_phrase_x=
wl_phytype=b
wl_phytypes=
wl_plcphdr=long
wl_preauth=1
wl_radio=1
wl_radio_date_x=1111111
wl_radio_power_x=19
wl_radio_time_x=00002359
wl_radio_x=1
wl_radioids=
wl_radius_ipaddr=
wl_radius_key=
wl_radius_port=1812
wl_rate=0
wl_rateset=default
wl_reg_mode=off
wl_rts=2347
wl_ssid=default
wl_unit=0
wl_wds=
wl_wds_timeout=1
wl_wdsapply_x=0
wl_wdslist_x=
wl_wdsnum_x=0
wl_wep=disabled
wl_wep_x=0
wl_wme=off
wl_wme_ap_be=15 63 3 0 0 off
wl_wme_ap_bk=15 1023 7 0 0 off
wl_wme_ap_vi=7 15 1 6016 3008 off
wl_wme_ap_vo=3 7 1 3264 1504 off
wl_wme_no_ack=off
wl_wme_sta_be=15 1023 3 0 0 off
wl_wme_sta_bk=15 1023 7 0 0 off
wl_wme_sta_vi=7 15 2 6016 3008 off
wl_wme_sta_vo=3 7 2 3264 1504 off
wl_wpa_gtk_rekey=0
wl_wpa_psk=
wlan_hardware_present=yes
wlan_ifname=eth1
wlan_netmask=255.255.255.0

I just turned off watchdog, so far it hasn't crashed.

Please keep up posted on this :-)

Side question -- if the watchdog doesn't turn out to be it, could turning down the clockspeed help?  Or is that generally bad?  I've seen some posts in other threads or wikis where it sounds like underclocking can be just as unstable as overclocking, on some routers.

Since we don't know the cause, I don't know if it would help or not. Probably not. The only cases of changing the clock speed improving stability I've seen are on some versioins of the WRT54G (v2?), in which you RAISE the clock speed to 216mhz to fix a problem with corrupt memory (iirc) seen during large file transfers.

I doubt lowering the clock speed would make the device LESS stable, but I suppose it is remotely possible since the device is most well tested at its default clock speed. In general, a marginal underclock or overclock should be totally acceptable for BCM47xx devices like those we are discussing here. Myself, I've been running my WRT54Gv4 overclocked 25% for several months.

Just a side-question.

For what reason do you run your WRT54Gv4 overclocked? Just "to see" the clockspeed beeing higher, or is there any noticable performance differences? :-)

And back to the thread:

Is everyone experiencing the stability issues that gleam is writing about, or does anyone actuatelly run the the Premium stable ?

macsat

Overclocking:

I run my WRT54Gv4 overclocked because I can wink. I did add a heatsink. Yes, I do believe that in some cases the CPU or backplane speed is a bottleneck. Keep in mind that even if your load average is constantly near zero, overclocking may still help in brief bursts where your CPU is used (i.e. some set of instructions or data move completes in 10ms instead of 11ms). The RAM on these units is often underclocked even. So, I personally believe it does help in performance, perceptible or not. If a device runs stable at a certain speed (proven), I see no reason not to run it at that speed (except for mayyybe possibly reducing life of the hardware, but who cares in the case of these routers).

It still hasn't crashed yet with wifi on.  I literally have to just wait it out right now.  I'll try and induce some heavy wifi traffic later today.

macsat wrote:

Is everyone experiencing the stability issues that gleam is writing about, or does anyone actuatelly run the the Premium stable ?

macsat

I encounter similar problem as gleam with Premium and RC5. Going to migrate to RC6 in a couple of days and look if it helps.

BTW, gleam, what do you mean by 'turning off watchdog'? Setting zero value to 'watchdog' nvram variable or simply unsetting it? I can't find anything about that in the OpenWRT Wiki. It seems to me (I've read this somewhere in the forum), that OpenWRT doesn't use watchdog at all. Thank you for your answer.

(Last edited by ega2002 on 27 Nov 2006, 22:12)

nbd, thank you very much for answering, but could you be more specific about this image and what should I expect after flashing it to my router

macsat wrote:

Is everyone experiencing the stability issues that gleam is writing about, or does anyone actuatelly run the the Premium stable ?

macsat

I started with RC5 on Premium at the beginning of November, the RC6 was released after I "finished" with the box and I decided to move to RC6 "because it was new" and installed exactly what I need based on the micro version. It seems stable so far with the settings in nvram from RC5. The problems I had were with wifi - I decided to 'ipkg upgrade' and that upgraded the lib and wireless-tools and that was a bad combination. I downgraded it back to the 28pre7 version and now I can forget about the problems. I had no time to do a research why the latest version could not work properly (the eth2 was not able to work in the infrastructure mode - insisted on ad-hoc and I couldn't change it even with iwconfig).

Have had lots of stability problems with the WL-500gP. We have 5-6 of them. Same problems running DD-WRT, OpenWRT rc6 and original Asus firmware.

- the signals are weak
- the connection is suddenly lost
- sometimes, the device reverts automatically from the configured IP address 192.168.50.30 to the factory default IP address 192.168.1.1.

Especially have problems when running the devices as WDS bridges. The connections will typically drop after a day or so. The problems are typically not so pronounced when running the device as a simple AP.

I also notice that the problems are more pronounced when the device is hanging on networks with high traffic. Our network is very hetereogenous with about 50 users running all sorts of windows, linux, freeBSD, printservers, webservers, etc.

When running the Asus firmware after having DD-WRT installed on it before, it seems there are some values are hanging in NVRAM (when logging into the Asus firmware, we connect to the device on IP 192.168.50.30, but the setup page still indicates IP being 192.168.1.1, also the channel is actually 11 while the setup says it is channel 1).

My friend says the wifi cards used inside WL-500gP are garbage. He has seen them around a lot of laptops and are the first things he replaces when the laptops (under Windows) have stability problems with the wireless network. Could this be related to poorly developed drivers on Broadcoms part? Or are we using a community driver. I believe there is a community driver available (and maybe used in OpenWRT), but that the driver has power issues last time I checked...

So far, OpenWRT has worked best for us, but there are definately stability issues.

I have been running WL-500gP with WhiteRussian 0.9 since it was released as my main router - it have been rock stable.

I am using it as router with wireless and lighttpd, php5, samba with shared external usb drive and some cron-jobs doing some dyndns updating and so on.

It has been 100% stable. Can't remember a crash!

Its pretty much the same here like macsat said.

Running torrents transfrerring GB of data etc 84 days online.
It never crashed by itself.

Tho I havent changed any nvram settings or anything I just flashed it with xwrt since I already had the 32mb thing from olegs firmware.

We have about 200 ASUS WL500GP running without any Problems (RC6).

The discussion might have continued from here.