Topic: Broke my WRTSL54GS; only safe mode works

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

Page 1 of 1

Post #1

keenerb

14 Aug 2007, 00:29

I've somehow managed to break my router.

It was working fine until I screwed with it.

I did this:

nvram set vlan0ports="0 1 2 3 4 5*"
nvram set vlan1ports="5"
nvram commit

And it broke.

Safe mode works OK.

I subsequently re-installed the factory firmware and did a factory reset, and it works fine.

I then re-installed the whiterussian 0.9 release, and no connectivity to the router, again except when in safe mode.

I downloaded and ran the nvram-clean.sh script (or whatever it's called.)

Here's my nvram dump, any help is appreciated.

Intel_firmware_version=v1.41.8
MS_scan_folder_num=0
MS_scan_max_num=10
MServer=0
NAS_alert=Successfully updated share properties.
aa0=3
access_share=music
ag0=255
all_partitions_share=1
audio_AAC=1
audio_AC3=1
audio_AIF=1
audio_LPCM=1
audio_M3U=1
audio_M4A=1
audio_MP2=1
audio_MP3=1
audio_MPA=1
audio_PCM=1
audio_WAV=1
audio_WMA=1
backup_job10=:::::::::::
backup_job1=:::::::::::
backup_job2=:::::::::::
backup_job3=:::::::::::
backup_job4=:::::::::::
backup_job5=:::::::::::
backup_job6=:::::::::::
backup_job7=:::::::::::
backup_job8=:::::::::::
backup_job9=:::::::::::
bcm4712_firmware_version=v1.50.0
boardflags=0x0018
boardnum=42
boardrev=0x10
boardtype=0x042f
boot_ver=v3.5
boot_wait=on
bootnv_ver=1
ccode=0
cctl=0
clkfreq=264
create_modify_share_part=PUBSHARE
create_or_modify_share=disk_create
create_or_modify_user=create
ddns_enable=0
ddns_interval=60
dhcp_num=50
dhcp_start=100
dl_ram_addr=a0001000
domadmins_gid=42002
domain_WRTSL54GS_sid=S-1-4-0-0-0-0-0-5-15-c7438c2e-db0a231e-b544e77b-0-0-0-0-0-0-0-0-0-0-0
error_pop_up_on_all=enabled
et0macaddr=00:18:39:EE:07:6E
et0mdcport=0
et0phyaddr=30
et1macaddr=00:90:4C:60:00:2B
et1mdcport=1
et1phyaddr=5
flash_type=Intel 28F640J3 4Mx16
ftp_access=0
ftp_all=1
ftp_port=21
ftp_share_access=2:admin:rw:guest:r
ftp_share_folder=/
gid_range=42000-43000
gpio4=ses_button
gpio5=ses_led
gpio7=ses_led2
group_users=admin:1:admin guest:1:guest
guest_uid=35000
il0macaddr=00:18:39:ee:07:70
lan_dhcp_enabled=0
lan_dhcp_num=100
lan_dhcp_start=50
lan_dns= 192.168.5.5
lan_gateway=192.168.5.2
lan_hwaddr=00:18:39:EE:07:6E
lan_ifname=br0
lan_ifnames=eth0 eth2 eth3 eth4
lan_ipaddr=192.168.1.1
lan_netmask=255.255.255.0
lan_proto=static
lan_stp=0
logon_drive=Z:
machine_comment=WRTSL54GS
machine_name=WRTSL54GS
nobody_gid=42001
old_claim_diskname=Blank Disk 1
old_lan_netmask=255.255.255.0
openvpn_cli=0
openvpn_cli_auth=psk
openvpn_cli_port=1194
openvpn_cli_proto=udp
os_date=Sep 14 2006
os_flash_addr=bfc40000
os_ram_addr=80001000
os_version=3.91.38.0
pa0b0=0x170c
pa0b1=0xfa24
pa0b2=0xfe70
pa0itssit=62
pa0itssit=62
pa0maxpwr=0x48
photo_BMP=1
photo_GIF=1
photo_JPG=1
photo_PNG=1
photo_TIF=1
pmon_ver=CFE 3.91.38.0
ppp_demand=0
ppp_idletime=5
ppp_mru=1500
ppp_mtu=1500
ppp_redialperiod=30
pppoe_demand=0
pppoe_idletime=5
pptp_cli=0
private_shares=All_Partitions:*:comment:/foreign_shares
reset_gpio=7
root_passwd=admin
router_name=WRTSL54GS
scratch=a0180000
sdram_config=0x0062
sdram_init=0x000b
sdram_ncdl=0x10204
sdram_refresh=0x0000
shared_info=All_Partitions:1:admin:rw
smb_admin_user=admin
sromrev=2
storage_groups_limit=15
storage_shares_limit=15
storage_users_limit=15
uid_range=35000-40000
users_gid=42000
video_AVI=1
video_DAT=1
video_M4V=1
video_MP4=1
video_MPG=1
video_VOB=1
video_WMV=1
vlan0hwname=et0
vlan0ports=0 1 2 3 5*
vlan1hwname=et0
vlan1ports=4
wan_device=eth1
wan_dhcp_num=50
wan_dhcp_start=100
wan_gateway=0.0.0.0
wan_iface=eth1
wan_ifname=eth1
wan_ifnames=eth1
wan_ipaddr=0.0.0.0
wan_mtu=1500
wan_netmask=0.0.0.0
wan_proto=dhcp
watchdog=5000
wifi_dhcp_num=50
wifi_dhcp_start=100
wl0_afterburner=auto
wl0_antdiv=-1
wl0_ap_isolate=0
wl0_auth=0
wl0_auth_mode=none
wl0_bcn=100
wl0_channel=6
wl0_closed=0
wl0_corerev=9
wl0_country=Worldwide
wl0_country_code=ALL
wl0_crypto=tkip
wl0_dtim=1
wl0_frag=2346
wl0_frameburst=on
wl0_gmode=6
wl0_gmode_protection=off
wl0_hwaddr=00:18:39:EE:07:70
wl0_ifname=eth2
wl0_infra=1
wl0_key=1
wl0_lazywds=1
wl0_macmode=disabled
wl0_maxassoc=128
wl0_mode=ap
wl0_mrate=0
wl0_net_mode=mixed
wl0_net_reauth=36000
wl0_phytype=g
wl0_phytypes=g
wl0_plcphdr=long
wl0_radio=1
wl0_radioids=BCM2050
wl0_radius_port=1812
wl0_rate=0
wl0_rateset=default
wl0_rts=2347
wl0_ssid=linksys
wl0_wds_timeout=1
wl0_wep=disabled
wl0_wep_bit=64
wl0_wme=off
wl0_wme_ap_be=15 63 3 0 0 off
wl0_wme_ap_bk=15 1023 7 0 0 off
wl0_wme_ap_vi=7 15 1 6016 3008 off
wl0_wme_ap_vo=3 7 1 3264 1504 off
wl0_wme_no_ack=off
wl0_wme_sta_be=15 1023 3 0 0 off
wl0_wme_sta_bk=15 1023 7 0 0 off
wl0_wme_sta_vi=7 15 2 6016 3008 off
wl0_wme_sta_vo=3 7 2 3264 1504 off
wl0_wpa_gtk_rekey=3600
wl0gpio2=0
wl0gpio3=0
wl0id=0x4320
wl10_mode=sta
workgroup=Linksys

(Last edited by keenerb on 14 Aug 2007, 00:39)

Post #2

bkloppenborg

15 Aug 2007, 03:34

keenerb,

I can say I've done that a few times trying to get VLANS to work with my two WRTSL54GS boxes. Without looking too deeply into your nvram settings, I'd say try resetting the nvram variables for the VLANS:

nvram set vlan0ports=0 1 2 3 5u
nvram set vlan1ports=4 5
nvram commit

reboot

Since you can get into safe mode, it's worth a shot.

I think since the WRTSL54GS has a separate interface for the WAN, eth1, you need not configure vlan0 with 5*. Instead, it should be untagged (5u). As far as I know, most WRT-series routers use a single switch for the WAN and LAN traffic and separate them using vlans.

(Last edited by bkloppenborg on 15 Aug 2007, 03:36)

Post #3

warrawarra

15 Aug 2007, 06:51

If you can just do a clean factory firmware flash ?? and then redo the current 0.9 you want it should work fine and all should be back to working / default.

Post #4

bkloppenborg

16 Aug 2007, 05:12

In a more dangerous move, I have also reset the nvram and filesystem on both of my WRTSL54GS units. The Wiki details how to do it and also indicates that you could break your router (etc.). Of course, if you do this on your router, you are doing it at your own risk.

If you decide to "reset" your router, you should consider exporting your nvram variables:

nvram show | sort

and saving the output for reference. After that, I reset the router's firmware and nvram by using the following two commands (router automatically reboots):

firstboot
mtd -r erase nvram

After I did this on my second (newer) unit, I noticed that a few of the wireless nvram settings were missing. I manually added them using the following:

nvram set wl0_closed=0
nvram set wl0_channel=2
nvram set wl0_macmode=allow
nvram set wl0_maclist=

In case you need them, I exported the nvram variables after first flashing the router with OpenWRT and after resetting the nvram (before adding the last four variables). Just ask and I'll link to them.

(Last edited by bkloppenborg on 16 Aug 2007, 05:14)

Post #5

fgordts

23 Aug 2007, 09:43

bkloppenborg wrote:

nvram set wl0_closed=0
nvram set wl0_channel=2
nvram set wl0_macmode=allow
nvram set wl0_maclist=
In case you need them, I exported the nvram variables after first flashing the router with OpenWRT and after resetting the nvram (before adding the last four variables). Just ask and I'll link to them.

Do you need to do a commit after these?
Also, what do these 4 do exactly? Are they required? Thanks

Post #6

bkloppenborg

28 Aug 2007, 20:50

Yes, you are correct, you do need the nvram commit statement after them.

The last four settings put some of the wireless configuration parameters back into the unit that are not included after you erase/reset the nvram.

My router worked fine over the wired connection without those four variables set. I did not try the wireless connection without the aforementioned variables set. I guess, I am sure that they are not required to get the wired side of the router to work but they are used to configure the wireless connection so they are most likely needed.

The discussion might have continued from here.

Page 1 of 1