WRTSL54GS *EXPOSED*

I thought to poke around on the WRTSL54GS filesytems, since my SL has not arrived yet. Very unwieldy product name, think I will use SL.

Not too bad establishing what's in the firmware file, if you spend a little time on it.

hexdump -C WRTSL54GS_2.00.0_US_code.bin|more

This will let you page through the contents in a somewhat readable form.

First clue is the "piggy" near the top. This marks the compressed kernel file.

But what we are really digging for is the filesystem. For that we look for the "magic" that tags a squashfs filesystem, which happens to be "hsqs". In old Linksys firmware they used cramfs format, but recent Linksys linux firmware seems to use squashfs.

# hexdump -C WRTSL54GS_2.00.0_US_code.bin|grep hsqs
0012cd90 03 39 31 00 e0 2a 00 00 68 73 71 73 e1 01 00 00 |.91..*..hsqs....|

So now we have the point in the file where the filesystem begins. You need to know a little hex to help out here. The address on the left is in hex, but it's the address of the beginning of that line. What we want is hsqs and everything past that.

So, 0012cd98 would be where we want to start. Even the Windows calculator in SCI-mode will let you convert this to 1232280. Because now we need decimal for splitting the file up. Now convert this to a larger block for easier dd work, 1232280 / 8 = 154035

# dd bs=8 skip=154035 if=WRTSL54GS_2.00.0_US_code.bin of=fs.img

So now we have a file fs.img that should be what we want, let's check:

# file fs.img
fs.img: Squashfs filesystem, little endian, version 2.0, 5634537 bytes, 481 inodes, blocksize: 65536 bytes, created: Tue Oct 25 10:34:50 2005

Yep, so down to business, assuming you have recompiled kernel on linux to include the squashfs filesystem type

# mount -o loop -t squashfs ./fs.img /mnt
# df -k /mnt
Filesystem 1K-blocks Used Available Use% Mounted on
/root/fs.img 5504 5504 0 100% /mnt

So now let's have a look around, quite a lot of stuff here in this expanded firmware. I'll just do some listings though so you can see:

[root@localhost mnt]# ls -la
total 9
drwxr-xr-x 1 root root 363 Oct 25 10:33 bin
drwxr-xr-x 1 root root 0 Oct 25 10:34 dev
drwxr-xr-x 1 root root 232 Oct 25 10:34 etc
drwxr-xr-x 1 root root 0 Oct 25 10:34 foreign_shares
lrwxrwxrwx 1 root root 9 Oct 25 10:34 home -> /tmp/home
drwxr-xr-x 1 root root 236 Oct 25 10:34 lib
drwxr-xr-x 1 root root 0 Oct 25 10:34 mnt
drwxr-xr-x 1 root root 0 Oct 25 10:34 proc
drwxr-xr-x 1 root root 962 Oct 25 10:33 sbin
drwxr-xr-x 1 root root 0 Oct 25 10:33 shares
drwxr-xr-x 1 root root 0 Oct 25 10:34 tmp
drwxr-xr-x 1 root root 37 Oct 25 10:34 usr
drwxr-xr-x 1 root root 49 Oct 25 10:34 var
drwxr-xr-x 1 root root 1080 Oct 25 10:33 www

[root@localhost mnt]# ls -la bin
total 563
lrwxrwxrwx 1 root root 7 Oct 25 10:34 [ -> busybox
lrwxrwxrwx 1 root root 9 Oct 25 10:34 addgroup -> tinylogin
lrwxrwxrwx 1 root root 9 Oct 25 10:34 adduser -> tinylogin
-rwxr-xr-x 1 root root 452500 Oct 25 10:33 busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 cat -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 chmod -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 chown -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 cp -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 date -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 dd -> busybox
lrwxrwxrwx 1 root root 9 Oct 25 10:34 delgroup -> tinylogin
lrwxrwxrwx 1 root root 9 Oct 25 10:34 deluser -> tinylogin
lrwxrwxrwx 1 root root 7 Oct 25 10:34 df -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 du -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 echo -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 false -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 free -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 grep -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 hexdump -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 kill -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 killall -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 ln -> busybox
lrwxrwxrwx 1 root root 9 Oct 25 10:34 login -> tinylogin
lrwxrwxrwx 1 root root 7 Oct 25 10:34 ls -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mkdir -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mknod -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 more -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mount -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 msh -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mv -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 ping -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 ps -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 pwd -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 rm -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 rmdir -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 sh -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 sleep -> busybox
lrwxrwxrwx 1 root root 9 Oct 25 10:34 su -> tinylogin
lrwxrwxrwx 1 root root 7 Oct 25 10:34 sync -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 tail -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 test -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 tftp -> busybox
-rwsr-xr-x 1 root root 75736 Oct 25 10:33 tinylogin
lrwxrwxrwx 1 root root 7 Oct 25 10:34 top -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 touch -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 true -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 umount -> busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 wget -> busybox
-rwxr-xr-x 1 root root 160 Oct 25 10:33 wipedisks

[root@localhost mnt]# ls -la etc
total 40
lrwxrwxrwx 1 root root 11 Oct 25 10:34 cron.d -> /tmp/cron.d
-rwxr-xr-x 1 root root 16 Oct 25 10:33 fdisk_fat32_claim_commands.txt
lrwxrwxrwx 1 root root 10 Oct 25 10:34 group -> /tmp/group
lrwxrwxrwx 1 root root 12 Oct 25 10:34 gshadow -> /tmp/gshadow
-rw-r--r-- 1 root root 17 Oct 25 10:34 host.conf
lrwxrwxrwx 1 root root 11 Oct 25 10:34 hostid -> /tmp/hostid
lrwxrwxrwx 1 root root 10 Oct 25 10:34 hosts -> /tmp/hosts
lrwxrwxrwx 1 root root 16 Oct 25 10:34 hosts.allow -> /tmp/hosts.allow
lrwxrwxrwx 1 root root 15 Oct 25 10:34 hosts.deny -> /tmp/hosts.deny
-rw-r--r-- 1 root root 1868 Oct 25 10:34 ld.so.cache
-rw-r--r-- 1 root root 14 Oct 25 10:34 ld.so.conf
-rw-r--r-- 1 root root 17 Oct 25 10:34 nsswitch.conf
-rwxr-xr-x 1 root root 7651 Oct 25 10:33 openssl.cnf
lrwxrwxrwx 1 root root 11 Oct 25 10:34 passwd -> /tmp/passwd
-rwxr-xr-x 1 root root 5834 Oct 25 10:33 protocols
lrwxrwxrwx 1 root root 16 Oct 25 10:34 resolv.conf -> /tmp/resolv.conf
-rwxr-xr-x 1 root root 11955 Oct 25 10:33 services
lrwxrwxrwx 1 root root 11 Oct 25 10:34 shadow -> /tmp/shadow

[root@localhost mnt]# ls -la lib
total 4459
-rwxr-xr-x 1 root root 128176 Oct 25 10:33 ld.so.1
-rwxr-xr-x 1 root root 2131944 Oct 25 10:33 libbigballofmud.so
lrwxrwxrwx 1 root root 18 Oct 25 10:34 libbigballofmud.so.0 -> libbigballofmud.so
-rwxr-xr-x 1 root root 26872 Oct 25 10:33 libcrypt.so.1
-rwxr-xr-x 1 root root 1159280 Oct 25 10:33 libc.so.6
-rwxr-xr-x 1 root root 12900 Oct 25 10:33 libdl.so.2
-rwxr-xr-x 1 root root 79512 Oct 25 10:33 libgcc_s.so.1
-rwxr-xr-x 1 root root 10276 Oct 25 10:34 libm.so.0
-rwxr-xr-x 1 root root 593880 Oct 25 10:33 libm.so.6
-rwxr-xr-x 1 root root 118136 Oct 25 10:33 libnsl.so.1
-rwxr-xr-x 1 root root 18312 Oct 25 10:33 libnss_dns.so.2
-rwxr-xr-x 1 root root 67148 Oct 25 10:33 libnss_files.so.2
-rwxr-xr-x 1 root root 122532 Oct 25 10:33 libpthread.so.0
-rwxr-xr-x 1 root root 90880 Oct 25 10:33 libresolv.so.2
drwxr-xr-x 1 root root 13 Oct 25 10:33 modules

[root@localhost mnt]# ls -la sbin
total 1242
-rwxr-xr-x 1 root root 14676 Oct 25 10:33 arytst
lrwxrwxrwx 1 root root 2 Oct 25 10:34 check_ps -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 check_ses_led -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 ddns_success -> rc
-rwxr-xr-x 1 root root 14312 Oct 25 10:33 detect_multipath
lrwxrwxrwx 1 root root 2 Oct 25 10:34 detectwan -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 disconnected_pppoe -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 diskerror -> rc
-rwxr-xr-x 1 root root 83416 Oct 25 10:33 dosfsck
lrwxrwxrwx 1 root root 2 Oct 25 10:34 erase -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 fdisk -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 filter -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 filtersync -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 fsck.minix -> ../bin/busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 fsck.msdos -> dosfsck
lrwxrwxrwx 1 root root 7 Oct 25 10:34 fsck.vfat -> dosfsck
lrwxrwxrwx 1 root root 16 Oct 25 10:34 getty -> ../bin/tinylogin
lrwxrwxrwx 1 root root 2 Oct 25 10:34 gpio -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 hb_connect -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 hb_disconnect -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 hotdiskadd -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 hotdiskremove -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 hotplug -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 hwclock -> ../bin/busybox
lrwxrwxrwx 1 root root 14 Oct 25 10:34 ifconfig -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 init -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 insmod -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 ipupdated -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 klogd -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 listen -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 lsmod -> ../bin/busybox
-rwxr-xr-x 1 root root 40132 Oct 25 10:33 lsraid
lrwxrwxrwx 1 root root 2 Oct 25 10:34 misc -> rc
-rwxr-xr-x 1 root root 56696 Oct 25 10:33 mkdosfs
lrwxrwxrwx 1 root root 14 Oct 25 10:34 mkfs.minix -> ../bin/busybox
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mkfs.msdos -> mkdosfs
lrwxrwxrwx 1 root root 7 Oct 25 10:34 mkfs.vfat -> mkdosfs
-rwxr-xr-x 1 root root 14244 Oct 25 10:33 mkraid
-rwxr-xr-x 1 root root 27460 Oct 25 10:33 mkreiserfs
lrwxrwxrwx 1 root root 14 Oct 25 10:34 mkswap -> ../bin/busybox
lrwxrwxrwx 1 root root 18 Oct 25 10:34 mount.smbfs -> /usr/sbin/smbmount
lrwxrwxrwx 1 root root 2 Oct 25 10:34 ntpd -> rc
-rwxr-xr-x 1 root root 42756 Oct 25 10:33 portmap
lrwxrwxrwx 1 root root 2 Oct 25 10:34 ppp_event -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 process_monitor -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 purgeshare -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 qos -> rc
lrwxrwxrwx 1 root root 6 Oct 25 10:34 raid0run -> mkraid
lrwxrwxrwx 1 root root 9 Oct 25 10:34 raidhotadd -> raidstart
lrwxrwxrwx 1 root root 9 Oct 25 10:34 raidhotremove -> raidstart
-rwxr-xr-x 1 root root 22644 Oct 25 10:33 raidreconf
lrwxrwxrwx 1 root root 9 Oct 25 10:34 raidsetfaulty -> raidstart
-rwxr-xr-x 1 root root 10068 Oct 25 10:33 raidstart
lrwxrwxrwx 1 root root 9 Oct 25 10:34 raidstop -> raidstart
-rwxr-xr-x 1 root root 393452 Oct 25 10:33 rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 reboot -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 redial -> rc
-rwxr-xr-x 1 root root 388608 Oct 25 10:33 reiserfsck
lrwxrwxrwx 1 root root 2 Oct 25 10:34 resetbutton -> rc
-rwxr-xr-x 1 root root 27376 Oct 25 10:33 resize_reiserfs
lrwxrwxrwx 1 root root 2 Oct 25 10:34 restore -> rc
lrwxrwxrwx 1 root root 14 Oct 25 10:34 rmmod -> ../bin/busybox
lrwxrwxrwx 1 root root 14 Oct 25 10:34 route -> ../bin/busybox
lrwxrwxrwx 1 root root 2 Oct 25 10:34 sendudp -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 ses_led -> rc
lrwxrwxrwx 1 root root 2 Oct 25 10:34 stats -> rc
-rwxr-xr-x 1 root root 5844 Oct 25 10:33 store_domain_sid
-rwxr-xr-x 1 root root 5844 Oct 25 10:33 store_machine_password
lrwxrwxrwx 1 root root 16 Oct 25 10:34 sulogin -> ../bin/tinylogin
lrwxrwxrwx 1 root root 14 Oct 25 10:34 swapoff -> ../bin/busybox
lrwxrwxrwx 1 root root 14 Oct 25 10:34 swapon -> ../bin/busybox
lrwxrwxrwx 1 root root 14 Oct 25 10:34 syslogd -> ../bin/busybox
-rwxr-xr-x 1 root root 10036 Oct 25 10:33 tmpgroupadd
-rwxr-xr-x 1 root root 5844 Oct 25 10:33 tmpgroupdel
-rwxr-xr-x 1 root root 10052 Oct 25 10:33 tmpuseradd
-rwxr-xr-x 1 root root 5844 Oct 25 10:33 tmpuseraddgroup
-rwxr-xr-x 1 root root 5860 Oct 25 10:33 tmpuserdel
-rwxr-xr-x 1 root root 5844 Oct 25 10:33 tmpuserdelgroup
-rwxr-xr-x 1 root root 5860 Oct 25 10:33 tmpusersetgroup
-rwxr-xr-x 1 root root 10036 Oct 25 10:33 user_note
lrwxrwxrwx 1 root root 2 Oct 25 10:34 write -> rc

[root@localhost mnt]# ls -la usr/local
total 2
drwxr-xr-x 1 root root 39 Oct 25 10:33 samba
drwxr-xr-x 1 root root 90 Oct 25 10:33 upnpmms

[root@localhost mnt]# ls -la www
total 902
-rw-r--r-- 1 root root 19492 Oct 25 10:33 Backup_Restore.asp
-rw-r--r-- 1 root root 11794 Oct 25 10:33 common.js
-rwxr-xr-x 1 root root 47 Jul 31 2003 Cysaja.asp
-rw-r--r-- 1 root root 25963 Oct 25 10:33 DDNS.asp
-rw-r--r-- 1 root root 4662 Oct 25 10:33 DHCPTable.asp
-rw-r--r-- 1 root root 19049 Oct 25 10:33 Diagnostics.asp
-rw-r--r-- 1 root root 17101 Oct 25 10:33 DMZ.asp
-rw-r--r-- 1 root root 17451 Oct 25 10:33 Factory_Defaults.asp
-rw-r--r-- 1 root root 1897 Oct 25 10:33 Fail.asp
-rw-r--r-- 1 root root 1897 Oct 25 10:33 Fail_s.asp
-rw-r--r-- 1 root root 1697 Oct 25 10:33 Fail_u_s.asp
-rw-r--r-- 1 root root 10260 Oct 25 10:33 FilterIPMAC.asp
-rw-r--r-- 1 root root 50259 Oct 25 10:33 Filters.asp
-rw-r--r-- 1 root root 3664 Oct 25 10:33 FilterSummary.asp
-rw-r--r-- 1 root root 24059 Oct 25 10:33 Firewall.asp
-rw-r--r-- 1 root root 33043 Oct 25 10:33 Forward.asp
-rw-r--r-- 1 root root 33575 Oct 25 10:33 Forward.asp.bk.asp
drwxr-xr-x 1 root root 322 Oct 25 10:34 help
drwxr-xr-x 1 root root 157 Oct 25 10:34 image
-rw-r--r-- 1 root root 57973 Oct 25 10:33 index.asp
-rw-r--r-- 1 root root 4300 Oct 25 10:33 index_heartbeat.asp
-rw-r--r-- 1 root root 4868 Oct 25 10:33 index_l2tp.asp
-rw-r--r-- 1 root root 3744 Oct 25 10:33 index_pppoe.asp
-rw-r--r-- 1 root root 7663 Oct 25 10:33 index_pptp.asp
-rw-r--r-- 1 root root 7619 Oct 25 10:33 index_static.asp
drwxr-xr-x 1 root root 194 Oct 25 10:34 lang_pack
-rw-r--r-- 1 root root 20219 Oct 25 10:33 Log.asp
-rw-r--r-- 1 root root 2617 Oct 25 10:33 Log_incoming.asp
-rw-r--r-- 1 root root 2759 Oct 25 10:33 Log_outgoing.asp
-rw-r--r-- 1 root root 39875 Oct 25 10:33 Management.asp
-rw-r--r-- 1 root root 26511 Oct 25 10:33 Outbreak_Alert.asp
-rw-r--r-- 1 root root 6288 Oct 25 10:33 Ping.asp
-rw-r--r-- 1 root root 14411 Oct 25 10:33 Port_Services.asp
-rw-r--r-- 1 root root 12927 Oct 25 10:33 PortTriggerTable.asp
-rw-r--r-- 1 root root 48842 Oct 25 10:33 QoS.asp
-rw-r--r-- 1 root root 7590 Oct 25 10:33 Quarantined.asp
-rw-r--r-- 1 root root 2801 Oct 25 10:33 Radius.asp
-rw-r--r-- 1 root root 4027 Oct 25 10:33 RouteTable.asp
-rw-r--r-- 1 root root 28709 Oct 25 10:33 Routing.asp
-rw-r--r-- 1 root root 1826 Oct 25 10:33 SES_Status.asp
-rw-r--r-- 1 root root 19140 Oct 25 10:33 Status_Lan.asp
-rw-r--r-- 1 root root 6506 Oct 25 10:33 Status_Router1.asp
-rw-r--r-- 1 root root 23787 Oct 25 10:33 Status_Router.asp
-rw-r--r-- 1 root root 18149 Oct 25 10:33 Status_Wireless.asp
drwxr-xr-x 1 root root 383 Oct 25 10:34 storage
-rw-r--r-- 1 root root 1354 Oct 25 10:33 style.css
-rw-r--r-- 1 root root 3114 Oct 25 10:33 Success.asp
-rw-r--r-- 1 root root 1969 Oct 25 10:33 Success_s.asp
-rw-r--r-- 1 root root 1935 Oct 25 10:33 Success_u_s.asp
-rw-r--r-- 1 root root 29 Apr 27 2004 SysInfo1.htm
-rw-r--r-- 1 root root 31 Apr 27 2004 SysInfo.htm
-rw-r--r-- 1 root root 5277 Oct 25 10:33 Traceroute.asp
-rw-r--r-- 1 root root 30177 Oct 25 10:33 Triggering.asp
-rw-r--r-- 1 root root 19466 Oct 25 10:33 Upgrade.asp
-rw-r--r-- 1 root root 19268 Oct 25 10:33 VPN.asp
-rw-r--r-- 1 root root 21034 Oct 25 10:33 WanMAC.asp
-rw-r--r-- 1 root root 4700 Oct 25 10:33 WEP.asp
-rw-r--r-- 1 root root 42200 Oct 25 10:33 Wireless_Advanced.asp
-rw-r--r-- 1 root root 28687 Oct 25 10:33 Wireless_Basic.asp
-rw-r--r-- 1 root root 19722 Oct 25 10:33 Wireless_MAC.asp
-rw-r--r-- 1 root root 6174 Oct 25 10:33 WL_ActiveTable.asp
-rw-r--r-- 1 root root 28 Sep 4 00:39 wlaninfo.htm
-rw-r--r-- 1 root root 4578 Oct 25 10:33 WL_FilterTable.asp
-rw-r--r-- 1 root root 23390 Oct 25 10:33 WL_WPATable.asp
-rw-r--r-- 1 root root 9661 Oct 25 10:33 WPA.asp
-rw-r--r-- 1 root root 3149 Oct 25 10:33 WPA_Preshared.asp
-rw-r--r-- 1 root root 5857 Oct 25 10:33 WPA_Radius.asp

Just received my SL yesterday from Buy.com

Took some topless photos

There does appear to be a serial port header.

There was a sticker over the flash memory stating firmware v 2.00.1, obscuring it's number but but we already know that from the Tom's article.

Also identified a few chips that Tom's article did not.

Sent copies of photos to jdepew

I'm really surprized that there has not been that much excitment over this new product from Linksys. I say this because I don't see anyone else but vincentfox talking about it.

vincentfox, hats off to you for the investigative work you are doing.

I ordered mine from buy.com and I'll be receiving it on Monday.

I'm really hopping that some of the great firmwares out there like DD-WRT get ported to fully exploit the ram and added capabilities of the WRTSL54GS.

Anyone care to speculate how long till we see a replacement firmware?

And one more question in comparing the WRT54G/S to the SL ....Does anyone think that having one antenna versus two will hinder the performace of the SL?

Yeah me too, not even that much hit-count on this post.

*shrug*

I'd be happy with the thing if even just as a NAS box. The routing and WiFi functions are just kinda nice extras.

Did you notice the commands in there for reiserfs, RAID, etc? Looks like lots of commands left in by the developers, that the web-UI doesn't use.

The thing I keep thinking about is OpenWRT and a command-line Torrent program. I could have a tiny low-power Torrent-box!

I will note that the external antenna is not removable. Bummer. But I do not really see this as supplanting the WRT54GL unit for my WISP needs anyhow so I can kind of overlook it. Average home user could throw a reflector on if they need a cheap range-boost anyhow. The primitive diversity mechanism that Linksys uses really doesn't make that big a difference in most home applications, so I don't think the single antenna is as big a hindrance as the fact that it's not removable.

I'm looking into the serial-port thing this afternoon. I guess I have to order some parts for that. I am a bit clumsy with soldering-iron so hope I don't break it. One thing I have not figured out, from the many serial-port web pages, is how they figure out which pin does what in the first place.

I think I know what chips do what, the last 2 are not identified in article at Tom's Hardware. Quick table:

CPU: BCM4704KPB (System-on-Chip solution)
RAM: Hynix HY5DU561622DT-J
Ethernet switch: BCM5325FKQM
USB? NEC D720101F1
Disk? BCM431BEKFBG

[deleted] Now that's there's an Autopsy page for this device, no need to link pix on some other site.

More copyage from the BBR thread:

The FCC documents are here:

https://gullfoss2.fcc.gov/prod/oet/...e=N&application_id=584250&fcc_id='Q87-WTSLGS'

But photos not very good. This motivated me to take those closeups to help others identify all the major chips.

Even a glance at the source code for firmware, the name CyberTan shows many times.

A glance through the CyberTan web-site shows a model WG-614C that has the same specs as this one. Page here:

http://www.cybertan.com.tw/product/wg614-c.asp

So it looks a lot like they are the same. I am not expert in all these vendor relationships but looks like the CyberTan device is the OEM and Linksys is simply repackaging it.

After reading information at Seattle Wireless, I saw that the 32-byte header is what tells the web-upgrade program that this firmware is good for this unit.

I came to the realization while looking through the OpenWRT site that the firmware for the all the BroadCom units is common, only the header differs for different units when doing web-upgrade. I verified this for myself by stripping the first 32 bytes from several different of their *.bin files and cmp the remaining *.trx file which were all byte-identical.

So there's a probability I think that I could pull the header from existing SL firmware file, slap that onto openwrt-brcm-2.4-squashfs.trx and get it to flash. It looks like from OpenWRT source that the 4704 is known. My big remaining question is the BCM5325FKQM chip. The source mentions BCM5325E (or compatible) in many places so it's just a question for me of is the F compatible enough with E that this will just work without needing modification.

Hmmmmm...... without knowledge of howto put a serial or JTAG on the board, if I brick it I'm dead in the water. Anyone have any pointers on HOW those guys who did serial-mods or JTAG figured out how to do that? I have a JP3 and JP4 (see pictures) which I suspect are something of that sort, but don't know how to tell for sure.

"CyberTan device is the OEM and Linksys is simply repackaging it."

That woudn't actually be much of a surprise. CyberTAN is also behind the Linksys-branded routers that Vonage provides to its customers.

I sure wish I had some help in researching this device.

*sigh*

I've been watching this with GREAT curiousity, since Linksys look like they might be ridding themselves of the WRT54GL. This could be the Next Linux Platform for the Linksys line, if the current stuff can be ported over.

I'd love to see a HyperWRT-enabled version of this firmware.

You did notice, I trust, that Linksys has released GPL code for this beast?

ftp://ftp.linksys.com/opensourcecode/wrtsl54gs/2.00.1/WRTSL54GS_v2.00.1.tgz

Yes, didn't I link that? I saw the GPL code soon after it was posted. Perhaps that was another forum. Thanks for adding it.

Anyhow, had already looked through the Linksys source. They do have chunks of their code that seem to differentiate for BCM5323F chip. So I may have an issue here. Stumbling in dark at this point.

The Linksys source doesn't compile easily for me. On the other hand the OpenWRT source was quite simple. Make menuconfig, and then make was about all it took. Mind you it took some hours on an old PIII-850 Linux box but it did build just fine.

I'll add that Linksys has 2.00.0 firmware for download, but 2.00.1 source code. Left hand and right hand not talking to each other. My device shipped with 2.00.1.

Love to help, but I know jack squat about routers except how to configure them. I do know a little programming, but not enough to be dangerous, and I don't have a busybox config to even compile the Linksys GPL code they have provided. Sorry.

I kinda 99% figured you knew about it, but didn't see any mention of it here. You seem far too smart to be digging with a shovel when there's a backhoe handy, but I wanted to make sure you knew about it, just on the REALLY off chance it had passed you by.

This may sound stupid question and a bit OT: I have a product that has the FCC ID. Can you please tell me the FCC page that will allow me to put in the DCC ID to show the FCC docs on the product?

I will marter my device for the cause...after i finish reading up on the BCM5323F.

Regarding FCC lookup, yeah I didn't find a simple place to just punch in a code-number and have it take me to that document.

What I found was under FCC > FCC E-filing > EAS > Generic Search
There's a bunch of stuff you can fill in, but I just fill in the first box which is the first 3 letters of the FCC code. In my case, Q87, and hit submit. It brings back all the filings under that group, all 187 of them from Linksys. Then you sor t through them to find the one you want. I don't know how to get there any faster.

We're in!

:cheering:

With the firmware provided by developer Kaloz, have OpenWRT running on it at this time.

Details to follow.

:thumb:

Flash space

Confirmation the flash is 8 megs:

root@OpenWrt:/bin# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 7296 2024 5272 28% /
none 15284 20 15264 0% /tmp

Anything else people would like to see now that I have a shell?

woot man. I knew you'd do it. congrats, u just made history now for me to find one locally...

dmesg output

I ran dmesg will paste that below.

Interestingly, looks like 266 MHz CPU not 300 as we all thought.

8M Flash, 32M RAM, plus USB functions make it a *finally* worthy successor to my old GS v1.0 unit.

root@OpenWrt:~# dmesg
CPU revision is: 00029006
Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.
Primary data cache 16kB, 2-way, linesize 16 bytes.
Linux version 2.4.30 (kaloz@arrakis) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Tue Jan 31 19:50:32 CET 2006
Setting the PFC value as 0x15
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 init=/etc/preinit noinitrd console=ttyS0,115200
CPU: BCM4704 rev 8 at 264 MHz
Using 132.000 MHz high precision timer.
Calibrating delay loop... 263.78 BogoMIPS
Memory: 30488k/32768k available (1409k kernel code, 2280k reserved, 100k data, 80k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
Squashfs 2.1-r2 (released 2004/12/15) (C) 2002-2004 Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 0) is a 16550A
b44.c:v0.93 (Mar, 2004)
PCI: Setting latency timer of device 00:01.0 to 64
eth0: Broadcom 47xx 10/100BaseT Ethernet 00:14:bf:e5:29:62
PCI: Setting latency timer of device 00:02.0 to 64
eth1: Broadcom 47xx 10/100BaseT Ethernet 00:90:4c:60:00:2b
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x20000,blocks=64
Using buffer write method
Flash device: 0x800000 at 0x1c000000
Creating 4 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "pmon"
0x00040000-0x007e0000 : "linux"
0x000c0000-0x007e0000 : "rootfs"
0x007e0000-0x00800000 : "nvram"
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
ip_conntrack version 2.1 (5953 buckets, 5953 max) - 320 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (jffs2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 80k freed
Algorithmics/MIPS FPU Emulator v1.5
diag boardtype: 0000042f
b44: eth1: Link is up at 100 Mbps, full duplex.
b44: eth1: Flow control is off for TX and off for RX.
Probing device eth0: found!
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
jffs2.bbc: SIZE compression mode activated.
PCI: Setting latency timer of device 01:01.0 to 64
PCI: Enabling device 01:01.0 (0004 -> 0006)
eth2: Broadcom BCM4318 802.11 Wireless Controller 3.90.37.0
Probing device eth0: found!
BFL_ENETADM not set in boardflags. Use force=1 to ignore.
device eth0 entered promiscuous mode
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
device eth2 entered promiscuous mode
eth2: attempt to add interface with same source address.
br0: port 2(eth2) entering learning state
br0: port 1(eth0) entering learning state
br0: port 2(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth0) entering forwarding state
br0: topology change detected, propagating
b44: eth1: Link is up at 100 Mbps, full duplex.
b44: eth1: Flow control is off for TX and off for RX.

just out of curiosity, do u still have usb support?

USB

Good question!

I don't have my flash-drive or USB-hard-drive with me at work.

When I get home I will plug it in, and see if I can access it.

Going to the gym now, hope this gets things rolling.

Perhaps if it is popular product, SL v2 will include a removable antenna

I'm sure it wouldn't be hard to yank one off an old WRT ( I got an uber-bricked one) and sauter it in its place on this board.

Thanks for the above information.

Woot. The GS goes down, and this comes to fill the void. And its got the ram/flash of the old GS'es too.. yay.

GPIO mappings

Quick table of GPIO functions:

GPIO pin
0 DMZ (disable=on,enable=off)
1 power (disable=blink,enable=on)
2 ?
3 ?
4 SES button (00=pressed,01=not pressed)
5 SES white LED (disable=on, enable=off)
6 reset button (00=pressed,01=not pressed)
7 SES orange LED (disable=on,enable=off)
8 ?
9 ?

Fun to run "gpio disable 7" and change LED's to your taste.

WRTSL54GS Not Working As Advertised Using Official Firmware

This is my first post and it may not be in the right forum.

I have been a Linksys user for some time and as a current owner of both a WRT54G and NSLU2 I was excited to hear that there would be a newly designed Router with external USB 2.0 storage connection capabilties. I have owned this product for 3 days now and I want to tell you about my problem.

My WRTSL54GS came with Firmware version v2.00.1 which is only slightly newer than the official firmware. After spending 3 days and an hour with Linksys tech support I am here to tell you that my WRTSL54GS, and I suspect all others with this official firmware version, will not allow an external (outside --> inside) connection to the attached USB drive. My router functions perfectly in all other aspects granting connectivity with all machines attached, wired and wireless, and an internal (from within my network) connection to my USB drives. But, it will NOT, as it has been advertised, allow me to connect to my USB drives from outside my network via a web browser or by any other method. This functionality has been advertised on many websites including the official Linksys website.

1. http://www.linksys.com/servlet/Sate...967848&pagename=Linksys/Common/VisitorWrapper
2nd bullet point: "Also connects hard drive or flash-based USB storage devices directly to your network to share music, video, or data files locally and over the Internet"

2. http://www.linksys.com/servlet/Sate...950302&pagename=Linksys/Common/VisitorWrapper
2nd paragraph, third sentence: "You can also set it up so that your storage is accessible from the Internet -- files can be easily downloaded via your web browser."

3. The box in which the WRTSL54GS came in. This information is listed on both the front and back of the box.

As well as many other sites, most of which seem to be just rehashing release information and have obviously not actually held one yet.

So to sum up my rant and end this post:

1. Unless I have gone crazy, I am unable to connect to my USB drives that are connected to this router via a web browser, ftp, or by any other means from outside my network. It works great from within through mapped drives, "My Network Places", and by manually typing the server name from "Start" --> "Run".

2. Linksys Tech support agrees with me and their people, while on the phone with me, could not do it either. They stated that the current version(shipped with the product) of the firmware will not do what it claims as advertised. Tech support escalated my call for an hour to supervisor after supervisor and said they would address my problem and respond to me via email.

3. Without talking about 3rd party programming and staying high level with the official GUI web browser interface that runs internally with the router. This product, unlike my NSLU2, does not provide either an FTP or HTTP server built into it to allow such connection in its current state. Nor, does it allow a port to be forwarded through the router to this function from the outside via its own browser managment.

***If anyone can get this to work with the official firmware, please show me the answer or please resolve this problem with enhanced firmware.***

P.S. As seen in another post somewhere. Yes you can, and I currently do have a Belkin Hi-Speed USB 2.0 7-port hub attached to it with multiple drives formatted in FAT32 and it works fine. NTFS is currently read-only(I assume firmware limited for now, similar to the early firware version of the NSLU2).

Tom

Well, this thread is more for people picking the SL apart. Stripping the very tasty hardware of it's good but confining factory firmware and replacing it with something more flexible. We are hardly Linksys employees knowledgable about every detail of their firmware. I doubt they would approve of what we are doing here.

What you have is perhaps a Linksys "marketing-speak" issue. Someone wrote something on the package and you see this as legally binding or fraudulent or something. I see your point. However you might be better served to take that up in a new post, not in this one.

As to how the problem could be resolved? I have not actually spent a lot of time with the Linksys firmware to see if it could be made to do what you want. I spent just about every moment from opening the box either trying to figure out how to get a command-line shell on it to gather info, or how to replace it. My immediate thought on browsing through their firmware for a few minutes was "good potential" but I was not so much interested in extending or twiddling their OS. Perhaps if you turned off the firewall and enabled remote management you could get something that would work. It would be an open invitation to system-crackers though.

Would I open up a standard Windows file-share port on my unit, for all the world to see? Ummm, that would be a "No!".

My personal Windows laptop setup is that I access my share away from home using this terrific program SftpDrive. This lets you access files over the encrypted SSH protocol but do it using the familiar Windows drive-letter interface. It works really well.

There are a number of ways you can skin the cat. Most of them will require alternate firmware and moderate fiddling around, not just "click to enable". If you are comfortable with learning about those options I would look at OpenWRT or soon enough one of the other alternate firmware being a good tool for making your SL hardware do more. Off the top of my head, perhaps a WebDAV module on the router could handle remote file-sharing in a semi-secure fashion but in a Windows clicky style. I don't like WebDAV but some people do. My preferred solution would be format the router-drives in ext3 (preferably mirrored!), turn on SSH, and use SftpDrive for remote file access. For local run the Samba daemon and do regular insecure Windows method.

Several possibilities, but not this week. Early days yet.

This week we just got the shiny new toy, it's all about porting the OS to run stably on it. No frills yet.

Those all sound like good options. I guess I was just hoping that the new WRTSL54GS would have the functionality of my WRT54G and NSLU2 consolidated into one piece of hardware. I wanted to move away from a file server and having machines running all of the time. Less noise and fewer fans(no moving parts except for the ext HD).

I will try one of the 3rd party firmware options when they get one hammered out within the next few weeks.

Thanks.

USB storage

I did a quick test of USB storage:

ipkg install kmod-usb-ohci
ipkg install kmod-usb-storage
ipkg install kmod-vfat

Rebooted and it auto-mounted my 1-gig flash-drive just fine.

Now for a LOT of people (not YOU), a router with a little 1-4 gig share for some shared documents is plenty of storage. And what a stunningly cool little file-server, with power consumption under 5 Watts!

Of course I'm sure the forum readers are already thinking about 300-gig drives, USB printers, and who knows what else.....

Re: USB storage

This is all execellent news - thanks for getting this to work! Is the version of OpenWRT you are using available somewhere? Are there special steps to flash this new unit? I may be interested in hacking around with it myself if I get one.

I believe Kaloz wants to wait until at least we have finished testing out the reset-button functionality. You need to be able to reset it, and also to have the option of failsafe mode with squashfs version, to be safe enough for general usage.

The copy I am running right now is only jffs2 version. I will post back as soon as it is available for testing. I think some caution will still apply so I would not encourage people to flash this yet, unless they accept risk of bricking.

Sounds good - will you announce it on the wiki too, or just here? Do you think it'll be a matter of days or more like weeks?

Thanks again!

I will just post here initially I think. I cannot speak for Kaloz and where he might post it on OpenWRT site.

I wouldn't expect it to take very long. Of course there is the small problem that he is in Hungary and I am in California USA so 9-hour time difference causes some delays

I don't think this has hit many stores yet...can't seem to really find it, but I know it's out there. I'll prob wait on getting one till I learn a bit more linux and ya'll get openWRT sorted out on it, but if I can help in any way, I'm here

I got mine from Buy.Com, didn't wait around for it to show in local stores.

At the moment I'm tinkering about with Samba. You don't realize what a pig Samba is until you try to fit into a tiny device, having a few problems. Reads work fine, writes to flash-drive not good, probably the USB-1 driver package I used.

Is there anything anyone would like me to test in particular? I can spend some time experimenting with the unit I have running. I'd love to see others working on this device, but the firmware is not quite ready today.

well I would personally like to see that antenna mod done. As soon as I were to get one, that's the first thing that would be done, since I'm in the long-range networking. Perhaps u should hook up a USB hub and see if u can get multiple devices running on that 1 USB port. Also, is the port powered? Man, there's so much I would want to do with it. Shit, you could even connect up a USB mouse and keyboard with it. They also make USB video cards....could u imagine a complete 200mhz box running through that? the possibilities are endless to what could be done with it, provided there's sufficient RAM or a pagefile could be utilized....hope this gets ur gears a crankin'

If you browse through the Wiki for OpenWRT docs, you can find some pretty wild projects already. One that sounds interesting is this one:

http://devices.natetrue.com/mobileap/

Now, this guy had to hack into the serial side because his router didn't have a USB port. Now we have a device with USB built-in. I already have a Nokia 6230 and USB cable for my laptop, might I make this same connection a little more directly? Interesting idea, a fully mobile WiFi router.

Another one that interested me is USB print-server.

Hubs are no problem. Of course there's going to be a limit to how many power-sucking USB devices you could hang off it. That wart is only going to handle so much. And I also think there is a current-limit spec on USB ports in general? I don't really see the SL at the center of a huge pile of equipment, maybe a few devices.

Actually, just get a powered hub. That way, the hub itself provides all the power needed on each USB port, and the USB port on the router doesn't have a lot of drain on it.

I have a motorola v551 cell phone at the moment, with plans to buy a razr off ebay in the near to mid future. Then again, both have bluetooth, and I have a USB to bluetooth adapter, but then we're getting uber complicated. The razr has a USB port on the side of the phone, so I would think that's the quickest route for me. Seems like and interesting thought tho

Plugging in my Nokia gives the following entries:

Feb 3 19:40:20 (none) kern.info kernel: hub.c: new USB device 01:02.0-1, assigned address 6
Feb 3 19:40:20 (none) kern.warn kernel: usb.c: USB device 6 (vend/prod 0x421/0x40f) is not claimed by any active driver.

So it does see something is there, just doesn't know what to do with it. Yet.

I see from some posts that the RC4 OpenWRT I am using is missing the usbserial module. Adding this back in may resolve this.

Update, got a kmod-usb-serial package, installed it.

Had to modify /etc/modules.d/70-usb-serial for the device:
usbserial vendor=0x421 product=0x40f

Rebooted, kernel sees a /dev/usb/tts/0

Installed microcom.

microcom -D/dev/usb/tts/0
AT
OK




(Explanation for those not familiar with old Hayes command-set, typing "at" command to modem and getting OK response means the modem is ready for commands.)

Is there anything the little box cannot do?

After some digging for PPP chat scripts for Cingular, I got it hooked up!

One SL unit, Nokia 6230 + USB cable, and some software.

Now mind you ping times on GPRS are just horrible, you wouldn't want to do much interactive work. Also have to change around the routing and iptables so it's the new WAN port.

But it's a pretty fun hack and no soldering required!

how's the actual speed on the cingular network. Also what plan u on that u can surf the net on. I have 1 meg of data transfer a month, so I wouldn't dare try that out till I had something better :S But Cingular is da bomb

Also, I'm sure one could write some iptables rules that if the real WAN port doesn't have an ip to backup to the cell.

Speed is okay, I don't know 130-200 Kbps or so on average. Good enough for access on the road. Latency on all celullar data networks I have used, precludes good use of ssh, VNC, remote-desktop or anything else highly interactive. But bulk traffic like web pages comes in at decent speeds once you get past the lag delay.

I have the old Cingular MediaWorks package at $20/month, used to be Unlimited data transfer, I don't know if they offer the same package under the same name any more. Most companies have something like it at around that price though.

Next project I think will be hooking up the USB printer, although that should be more straightforward and less exciting.

Just curious: is the vlan naming the same as the later WRTs (i.e. GS) with regard to ifnames, etc.? Also, I assume/hope the wireless is still separable from the ethernet switch for routing and firewalling purposes (this is one initial reason I went to OpenWRT - the ability to have fine iptables control over wireless/lan/wan).

I'll poke around and see what I can come up with. I have an old GS v1.0 unit to compare with. Perhaps it would help if you could tell me some commands you want run, and specific information?

Will be testing firmware with reset fix this afternoon also.

go vincent, makin history one day at a time

I have a WRT54G 1.1 and more recently a WRT54GS 2.0. The older one (which has a slower CPU) is my backup.

The OpenWRT wiki lists how the vlans work here:
http://wiki.openwrt.org/OpenWrtDocs/Configuration#head-b62c144b9886b221e0c4b870edb0dd23a7b6acab

So my units have different naming schemes for the vlans (the newer one makes a little more sense!). I'd guess the SL uses the newer scheme. More importantly, that same wiki link describes how to separate the wifi from the ethernet setments (by not using br0). This is cool, since you can then route between the wifi and lan subnets (and wan) separately and set different iptables rules, thereby protecting your lan machines from wifi (an extra layer of protection in case your wifi gets hacked). You can even separate different ethernet jacks into separate segments if you want, but I don't do this.

It might be obvious that the SL would have this same hardware setup and functionality, but I just wanted to verifiy before I get too excited about it.

...One thing that might be helpful is to post the results of "nvram show" - this will reveal the ifnames and vlan stuff, etc.

Oh, and I looked back at your dmesg post, and this seems to show the eth0, eth1, eth2, and br0 stuff, implying that the vlans are separable...

In fact, it looks like eth2 is wifi, which is in fact different than the recent G/GS versions. It'll be interesting to see how it all differs.

Thanks!

failsafe functional

I just tested firmware with functional "failsafe" mode on squashfs firmware. However DMZ LED not working correctly to show boot-phase, so timing the reset-press was done blind. While in failsafe though it flashes the SES button to remind you what mode you are in. Getting closer....

ifconfig output

I will do several posts with each chunk of information that I think
might be useful for what you want to know about network
architecture. Note I have disabled WiFi radio as I am not using it
right now. Starting with output of ifconfig -a:

br0 Link encap:Ethernet HWaddr 00:14:BF:E5:29:62
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:331 errors:0 dropped:0 overruns:0 frame:0
TX packets:411 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32900 (32.1 KiB) TX bytes:129002 (125.9 KiB)

eth0 Link encap:Ethernet HWaddr 00:14:BF:E5:29:62
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:321 errors:0 dropped:0 overruns:0 frame:0
TX packets:406 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37850 (36.9 KiB) TX bytes:133147 (130.0 KiB)
Interrupt:4

eth1 Link encap:Ethernet HWaddr 00:90:4C:60:00:2B
inet addr:10.70.1.106 Bcast:10.70.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:213 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:86557 (84.5 KiB) TX bytes:30609 (29.8 KiB)
Interrupt:5

eth2 Link encap:Ethernet HWaddr 00:14:BF:E5:29:62
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:24
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:2 Base address:0x2000

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)

brctl output

(tabs get messed up posting here)

root@OpenWrt:~# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0014bfe52962 no eth0
eth2

nvram show sorted output

Following is very long ~600 lines. I did not yet run nvram-clean.sh on the SL, so there are many unused Linksys variables. I replaced one line for a filter variable with =BUNCH OF STUFF since it was obscenely long line.

Intel_firmware_version=v1.41.8
MS_scan_folder1=
MS_scan_folder2=
MS_scan_folder3=
MS_scan_folder4=
MS_scan_folder5=
MS_scan_folder_num=0
MS_scan_folder_value=
MS_scan_max_num=10
MServer=0
QoS=0
aa0=3
access_share=mini
action_service=
action_service_arg1=
ag0=255
all_partitions_share=1
aol_block_traffic1=0
aol_block_traffic2=0
aol_block_traffic=0
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
autofw_port0=
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
blank_disk_info=
block_activex=0
block_cookie=0
block_java=0
block_loopback=0
block_proxy=0
block_wan=1
boardflags=0x0018
boardnum=42
boardrev=0x10
boardtype=0x042f
boot_ver=v3.5
bootnv_ver=1
ccode=0
cctl=0
cifs_master_enable=enabled
cifs_msdfs_enable=enabled
clkfreq=264
console_loglevel=1
create_modify_share_name=
create_modify_share_part=NTFS2
create_or_modify_share=disk_create
ct_modules=
d11g_bcn=100
d11g_channel=6
d11g_dtim=1
d11g_frag=2346
d11g_mode=6
d11g_rate=0
d11g_rateset=default
d11g_rts=2347
daylight_time=1
ddns_cache=
ddns_change=
ddns_enable=0
ddns_enable_buf=
ddns_hostname=
ddns_hostname_2=
ddns_hostname_buf=
ddns_interval=60
ddns_passwd=
ddns_passwd_2=
ddns_passwd_buf=
ddns_status=
ddns_username=
ddns_username_2=
ddns_username_buf=
def_hwaddr=00:00:00:00:00:00
dhcp_domain=wan
dhcp_lease=0
dhcp_num=50
dhcp_start=100
dhcp_wins=wan
dl_ram_addr=a0001000
dmz_enable=0
dmz_ipaddr=0
domadmins_gid=42002
domain_WRTSL54GS_sid=S-1-4-0-0-0-0-0-5-15-a556df1d-aa68baeb-bff6b41b-0-0-0-0-0-0-0-0-0-0-0
domain_active_pools=
domain_memberships=
dr_lan_rx=0
dr_lan_tx=0
dr_setting=0
dr_wan_rx=0
dr_wan_tx=0
enable_game=0
error_mail_smtp_port_num=
error_mail_smtp_server=
error_pop_up_machine_names=
error_pop_up_on_all=enabled
et0macaddr=00:14:BF:E5:29:62
et0mdcport=0
et0phyaddr=30
et1macaddr=00:90:4C:60:00:2B
et1mdcport=1
et1phyaddr=5
ezc_enable=1
ezc_version=2
filter=on
filter_client0=
filter_dport_grp10=
filter_dport_grp1=
filter_dport_grp2=
filter_dport_grp3=
filter_dport_grp4=
filter_dport_grp5=
filter_dport_grp6=
filter_dport_grp7=
filter_dport_grp8=
filter_dport_grp9=
filter_id=1
filter_ip_grp10=
filter_ip_grp1=
filter_ip_grp2=
filter_ip_grp3=
filter_ip_grp4=
filter_ip_grp5=
filter_ip_grp6=
filter_ip_grp7=
filter_ip_grp8=
filter_ip_grp9=
filter_mac_grp10=
filter_mac_grp1=
filter_mac_grp2=
filter_mac_grp3=
filter_mac_grp4=
filter_mac_grp5=
filter_mac_grp6=
filter_mac_grp7=
filter_mac_grp8=
filter_mac_grp9=
filter_maclist=
filter_macmode=deny
filter_port=
filter_port_grp10=
filter_port_grp1=
filter_port_grp2=
filter_port_grp3=
filter_port_grp4=
filter_port_grp5=
filter_port_grp6=
filter_port_grp7=
filter_port_grp8=
filter_port_grp9=
filter_rule10=
filter_rule1=
filter_rule2=
filter_rule3=
filter_rule4=
filter_rule5=
filter_rule6=
filter_rule7=
filter_rule8=
filter_rule9=
filter_services=BUNCH OF STUFF
filter_tod1=
filter_tod2=
filter_tod3=
filter_tod4=
filter_tod5=
filter_tod6=
filter_tod7=
filter_tod8=
filter_tod9=
filter_tod_buf10=
filter_tod_buf1=
filter_tod_buf2=
filter_tod_buf3=
filter_tod_buf4=
filter_tod_buf5=
filter_tod_buf6=
filter_tod_buf7=
filter_tod_buf8=
filter_tod_buf9=
filter_web_host10=
filter_web_host1=
filter_web_host2=
filter_web_host3=
filter_web_host4=
filter_web_host5=
filter_web_host6=
filter_web_host7=
filter_web_host8=
filter_web_host9=
filter_web_url10=
filter_web_url1=
filter_web_url2=
filter_web_url3=
filter_web_url4=
filter_web_url5=
filter_web_url6=
filter_web_url7=
filter_web_url8=
filter_web_url9=
firmware_version=v2.00.1
flash_type=Intel 28F640J3 4Mx16
foreign_disk_info=
forward_port=
fw_disable=0
get_mac=00:14:BF:E5:29:62
get_mac_index=1
get_sn=CJK00EC00470
get_sn_index=1
gid_range=42000-43000
gpio4=ses_button
gpio5=ses_led
gpio7=ses_led2
group_users=admin:1:admin guest:1:guest
guest_uid=35000
hb_server_domain=
hb_server_ip=
http_client_ip=10.70.1.55
http_client_mac=000:59:A9:2A:77
http_enable=1
http_lanport=80
http_method=post
http_passwd=admin
http_username=
http_wanport=8080
https_enable=0
ident_pass=0
il0macaddr=00:14:bf:e5:29:64
ipsec_pass=1
is_default=1
is_modified=0
l2tp_get_ip=
l2tp_pass=1
l2tp_server_ip=
lan_dhcp=0
lan_domain=
lan_hwaddr=00:14:BF:E5:29:62
lan_hwnames=
lan_ifname=br0
lan_ifnames=eth0 eth2 eth3 eth4
lan_ipaddr=192.168.1.1
lan_lease=86400
lan_netmask=255.255.255.0
lan_proto=static
lan_route=
lan_stp=0
lan_wins=
local_user_management=disabled
log_enable=0
log_ipaddr=0
log_level=0
logon_drive=Z:
logon_script=
mac_clone_enable=0
machine_comment=WRTSL54GS
machine_name=WRTSL54GS
manual_rate=0
mtu_enable=0
multicast_pass=0
nas_login=admin:admin:admin guest:guest:guest
nas_messag=
nas_message=Successfully deleted share mini.
nas_result=black
nfs_master_enable=disabled
nobody_gid=42001
ntp_mode=auto
ntp_server=130.207.244.240
old_lan_netmask=255.255.255.0
os_date=Nov 7 2005
os_flash_addr=bfc40000
os_name=linux
os_ram_addr=80001000
os_server=
os_version=3.91.38.0
pa0b0=0x170c
pa0b1=0xfa24
pa0b2=0xfe70
pa0itssit=62
pa0maxpwr=0x48
pdc_enable=disabled
pdc_pool=
photo_BMP=1
photo_GIF=1
photo_JPG=1
photo_PNG=1
photo_TIF=1
ping_ip=
ping_times=
pmon_ver=CFE 3.91.38.0
port_flow_control_1=1
port_flow_control_2=1
port_flow_control_3=1
port_flow_control_4=1
port_priority_1=0
port_priority_2=0
port_priority_3=0
port_priority_4=0
port_rate_limit_1=0
port_rate_limit_2=0
port_rate_limit_3=0
port_rate_limit_4=0
port_trigger=
ppp_ac=
ppp_demand=0
ppp_get_ac=
ppp_get_srv=
ppp_idletime=5
ppp_keepalive=0
ppp_mru=1500
ppp_mtu=1500
ppp_passwd=
ppp_redialperiod=30
ppp_service=
ppp_static=0
ppp_static_ip=
ppp_username=
pppoe_ac=
pppoe_demand=0
pppoe_idletime=5
pppoe_ifname=
pppoe_keepalive=0
pppoe_passwd=
pppoe_service=
pppoe_static=0
pppoe_static_ip=
pppoe_username=
pptp_get_ip=
pptp_pass=1
pptp_server_ip=
prev_gid=
prev_uid=
primary_pool_name=
primary_share_name=
printer_pool_name=
private_shares=All_Partitions:*:comment:/foreign_shares
qos_appname1=
qos_appname2=
qos_appname3=
qos_appname4=
qos_appname5=
qos_appname6=
qos_appname7=
qos_appname8=
qos_appport1=0
qos_appport2=0
qos_appport3=0
qos_appport4=0
qos_appport5=0
qos_appport6=0
qos_appport7=0
qos_appport8=0
qos_devmac1=00:00:00:00:00:00
qos_devmac2=00:00:00:00:00:00
qos_devname1=
qos_devname2=
qos_devpri1=0
qos_devpri2=0
qos_enable=no
qos_level1_file_extensions=
qos_level2_file_extensions=
rate_mode=1
remote_management=0
remote_mgt_https=0
reset_gpio=7
restore_defaults=0
root_passwd=admin
router_disable=0
router_name=WRTSL54GS
scratch=a0180000
sdram_config=0x0062
sdram_init=0x000b
sdram_ncdl=0x10104
sdram_refresh=0x0000
security_mode2=disabled
security_mode=disabled
security_mode_last=
sel_qosport1=0
sel_qosport2=0
sel_qosport3=0
sel_qosport4=0
sel_qosport5=0
sel_qosport6=0
sel_qosport7=0
sel_qosport8=0
ses_client_join=0
ses_count=0
ses_enable=1
ses_event=2
ses_led_assertlvl=0
ses_sw_btn_status=DEFAULTS
shared_info=All_Partitions:1:admin:rw
skip_amd_check=0
skip_intel_check=0
smb_admin_user=admin
sromrev=2
static_route=
static_route_name=
stats_server=
storage_groups_limit=15
storage_shares_limit=15
storage_users_limit=15
time_zone=-08 1 1
timer_interval=3600
traceroute_ip=
ubsa_enable=disabled
uid_range=35000-40000
upnp_enable=1
upnp_max_age=180
upnp_ssdp_interval=60
upnp_wan_proto=
user_share_permission_default=no
users_gid=42000
video_AVI=1
video_DAT=1
video_M4V=1
video_MP4=1
video_MPG=1
video_VOB=1
video_WMV=1
wan_device=vlan1
wan_dns=
wan_domain=
wan_gateway=0.0.0.0
wan_gateway_buf=0.0.0.0
wan_get_dns=
wan_get_domain=
wan_hostname=
wan_hwaddr=
wan_hwname=
wan_iface=eth1
wan_ifname=eth1
wan_ifnames=eth1
wan_ipaddr=0.0.0.0
wan_ipaddr_buf=0.0.0.0
wan_lease=86400
wan_mtu=1500
wan_netmask=0.0.0.0
wan_primary=1
wan_proto=dhcp
wan_run_mtu=1500
wan_speed=4
wan_unit=0
wan_wins=
watchdog=5000
web_wl_filter=0
wk_mode=gateway
wl0_active_mac=
wl0_afterburner=auto
wl0_akm=
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:14:BF:E5:29:64
wl0_ifname=eth2
wl0_infra=1
wl0_key1=
wl0_key2=
wl0_key3=
wl0_key4=
wl0_key=1
wl0_lazywds=1
wl0_mac_deny=
wl0_mac_list=
wl0_maclist=
wl0_macmode1=disabled
wl0_macmode=disabled
wl0_maxassoc=128
wl0_mode=0
wl0_mrate=0
wl0_net_mode=mixed
wl0_net_reauth=36000
wl0_passphrase=
wl0_phytype=g
wl0_phytypes=g
wl0_plcphdr=long
wl0_radio=0
wl0_radioids=BCM2050
wl0_radius_ipaddr=
wl0_radius_key=
wl0_radius_port=1812
wl0_rate=0
wl0_rateset=default
wl0_rts=2347
wl0_ssid=linksys
wl0_unit=0
wl0_wds=
wl0_wds_timeout=1
wl0_wep=disabled
wl0_wep_bit=64
wl0_wep_buf=
wl0_wep_gen=
wl0_wep_last=
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
wl0_wpa_psk=
wl0gpio2=0
wl0gpio3=0
wl0id=0x4320
wl_active_add_mac=0
wl_active_mac=
wl_afterburner=auto
wl_akm=
wl_antdiv=-1
wl_ap_isolate=0
wl_auth=0
wl_auth_mode=none
wl_bcn=100
wl_channel=6
wl_closed=0
wl_corerev=
wl_country=Worldwide
wl_country_code=ALL
wl_crypto=tkip
wl_dtim=1
wl_frag=2346
wl_frameburst=on
wl_gmode=6
wl_gmode_protection=off
wl_hwaddr=
wl_ifname=
wl_infra=1
wl_key1=
wl_key2=
wl_key3=
wl_key4=
wl_key=1
wl_lazywds=1
wl_mac_deny=
wl_mac_list=
wl_maclist=
wl_macmode1=disabled
wl_macmode=disabled
wl_maxassoc=128
wl_mode=ap
wl_mrate=0
wl_net_mode=mixed
wl_net_reauth=36000
wl_passphrase=
wl_phytype=g
wl_phytypes=
wl_plcphdr=long
wl_radio=0
wl_radioids=
wl_radius_ipaddr=
wl_radius_key=
wl_radius_port=1812
wl_rate=0
wl_rateset=default
wl_rts=2347
wl_ssid=linksys
wl_unit=0
wl_wds=
wl_wds_timeout=1
wl_wep=disabled
wl_wep_bit=64
wl_wep_buf=
wl_wep_gen=
wl_wep_last=
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=3600
wl_wpa_psk=
workgroup=Linksys
workgroup_or_domain=workgroup

Re: ifconfig output

Thanks - this is all great info! One experiement would be to separate the lan and wifi. Just set lan_ifname to eth0.

Then if you do ifconfig -a again, it should show the breakout of the 3 interfaces, and the MAC addresses of the lan and wifi will be separate. Should not affect you, since you are not using wifi.

Strange that there is no "vlan0ports" variable, which would control which ethernet jacks are part of that vlan. My GS has: vlan0ports=1 2 3 4 5*

Perhaps that's the default so it doesn't need to be set.

In any case, looks like we have:

lan: eth0
wan: eth1 / vlan1
wifi: eth2

I'm not sure where vlan0 comes into play, or what vlan wifi and lan are on...

I think we are pretty close to release of firmware. Then more people can try it, experiment for themselves, and post even more results. Kaloz has really done a great job with helping out on the firmware during a weekend! He deserves a huge thanks from everyone!

I have had lots of fun leading the charge on this project, but thankfully time for others to take over very soon. Getting a bit tired, have been relentlessly pursuing this for 12 days now. I will post back on this thread as well when it's somewhere for download.

Big thanks to you and Kaloz for the great work - anxious to try it!

ANNOUNCEMENT: SL FIRMWARE AVAILABLE FOR TEST

:cheering:

Kaloz has agreed to put it up on the OpenWRT site.

:clap:

Look on http://www.openwrt.org/ under Downloads in the people/kaloz/ directory. It's in the 2006-02-06 directory, but you can check the timestamps on the file are 05-Feb-2006. Also packages available there, built for that release. Changes will be checked into the SubVersion repository so future full releases should incorporate support for the SL unit.

PATIENCE REWARDED: Give it a good solid 5 *minutes* after flashing to let it do it's thing. Do not prematurely cycle the power because you think it's done.

Currently does not use DMZ LED during boot, so timing use of reset button to reach failsafe will require a little guesswork. You will know you are in failsafe, by the flashing SES button.

RISK: YOU HAVE BEEN WARNED!

Just don't come crying :cry: if you brick your SL and didn't even read through the documentation first for precautions to take or helpful tips on de-bricking it. No documented access at this time to serial or JTAG ports for this unit. So keep in mind that you may brick a $100 unit and accept that risk.

One more time: PLEASE read the documentation first!

Now I'm taking the afternoon off.

Y'all have fun! :thumb:

Going to reflash mine with JFFS2 version now and start poking around with Samba in the next few days. Perhaps it will also be possible to crunch in a half-decent BitTorrent client?

I look forward to hearing some other people's insights on this unit. And not just the software, also I'm sure there's one or two of you handy with soldering irons. It would be nice to know how to add serial ports to see the console for example.

Damn. :x I was hoping to install this box in my wiring closet, and use an extension antenna cable to get the signal out in the open. Are you saying there's no way for me to do that with this product?

Sure there's a way. Remove built-in antenna, get a soldering iron and substitute in an RP-SMA or RP-TNC connector. That part isn't rocket science, and isn't expensive. Just annoying to have to do it, eh?

Yes, I would like to :jester::whip: the clown who made that design choice.

vincentfox - thanks for the quick reply. I'll have to crack open my WRT (ordered today) before I fully understand what I need to do. I'm not very confident with the soldering iron yet so I'm still a little hesitant at calling this a no-brainer procedure.

I can't help you with the OpenWRT port but I applaude the work you're doing. Good luck man! :clap:

I finally got Samba working acceptably.

There's a samba 2.0.10 in Nico's testing directory. Yeah I know it's old but it's small and for home-LAN it's fine enough. I kept things simple set the smb.conf so that guest=root, no mucking about with accounts, etc.

I plugged in my 1-gig flash-drive and used it for the storage for this exercise.

A problem I kept running into was with writing large files. Something is broken with regards to FAT32 filesystems, but I'm not sure where the blame lies. I spent a while chasing it around and got nowhere.

So I gave up. I installed packages kmod-ext2, e2fsprogs, and fdisk.

fdisk the flash-drive, one big linux partition

mke2fs -j gave some error, had to find a fix which was
ln -s /proc/mounts /etc/mtab
mke2fs -j ....... worked fine then

reboot

Saw it automounted my flash-drive. Started Samba and tried writing a 350-meg file. Took 2 minutes 10 seconds. Not too bad, considering. Performance would likely be better with a hard drive.

So you can get it to work easily enough as a NAS device if you can live with your drive not being so portable to WinTel units anymore.

After that it's just a matter of installing openssh-sftp-server, and punch a hole in the WAN side of the firewall for ssh, and you have what the poster a while back wanted. A device that will let you get to your files easily from inside and outside the network.

On another note, I hooked it up to my "Watts Up?" meter and it shows that it uses about 8 Watts. So you have can a little all-in-one widget that is energy efficient too.

And I still have 4.6 megs free to add more packages on the builtin-flash.

chillispot? maybe even a radius server? that would be the entire operation I wanna build in 1 box

Interesting... you are definitely in uncharted territory here, but I wonder what the deal is with FAT32. I know there is a "large file" transfer issue on the WRT54GS v2.0 having to do with CPU timing. I really hope it's not a hardware issue.

Anyway, glad you got it working with ext2!

I don't understand the /proc/mounts issue - can you give more details on how you fixed this? How did you know to try the symlink?

Keep up the great work!

would there be any issues with running a LINKSYS PAP2 (Vonage) over the SL with the new firmware?

Chillispot and RADIUS not a problem, packages already.

FAT32, not sure what's up there didn't investigate every possible problem. Could be kernel module problem, could be just some issue with needing the right voodoo in smb.conf file. I went to their bug-tracker and submitted a report. I was really more interested in getting the performance numbers for writes on this box, to see what the hardware was capable of, so I took the ext3 shortcut.

PAP2 shouldn't be an issue I think. It's just a router as far as that is concerned. I've never owned a VoIP box, do they interact with router in some particular ways?

Nope. They just need high priority in QoS if your upstream bandwidth is constrained, etc, but other than that the Vonage units only need a laundry list of open (not forwarded) ports.

Oh yes, there's a QoS script I'm using from the OpenWRT forums that seems to work pretty well. The focus of this script is on simplicity. So they orient it around treating specified PRIORITY ports and IP's as express traffic. And everything else as bulk.

I like this approach on small routers. You can really get bogged down with doing complex scripts, Layer-7 filtering of protocols, multiple classes. You can end up spending a lot of time analyzing traffic, which is not something I would want a small router to waste much of it's limited resources on. A few privileged ports and IP's seems like plenty. For anything fancier get an old PC and load Linux on it, then you have plenty of room for such complex work. In My Humble Opinion, a lot of the current GUI-friendly other firmware projects have gotten bogged down on this QoS thing by folding in every conceivable user requested feature like L7.

Samba performance

Forgot to mention, I hooked up an old Barracuda IV 40-gig 7200RPM in a USB2 enclosure and used that to retest Samba write speeds. Came out identical so at this moment the moderate write-speeds are not device-limited. I thought maybe it was just the flash-drive.

You can pick your likely candidate for bottleneck. My guess would be the old Samba code, but the CPU and kmod-usb2 drivers also possible. Still a bit under 3 megs/sec on write is not shabby for this class of hardware.

I would be happier to see it up around 5-6 though.

So.....

Has anyone else received an SL and starting messing with it?

I got my SL just over a week ago. I was going to buy a WRT54G/S and I opted for the SL in hopes that the SL would be adopted by the opensource community. Hence I gambled that the SL would be a better investment than the WRT54G/S.

I'm using it now with the Linksys firmware.

My knowledge of Linux is nill. I'm kinda waiting for DD-WRT to come out with a version for the WRTSL54GS and then I'll be ready move away from the Linksys firmware. I need something a bit more friendly than OpenWRT.

Bummer... I got my WRTSL54GS yesterday, but upon opening the box, I saw that the silver/plastic case was marred and scratched (the top face had mutiple areas of abrasion, etc.)! Was looking forward to installing OpenWRT on it today, but I guess It'll have to wait; some people may not have been bothered by this, but I'm a bit of a stickler for this sort of thing. I'm surprized Linksys let it go out this way - the shrinkwrap was on, so it looks like it was not opened... Oh well.

More likely the store has a shrinkwrap machine and simply re-wrapped it. Pretty common practice, sadly.

Yes, I've wondered this before, especially when the shrinkwrap does not look quite right. This one did seem a bit non-standard (the corners/points seemed "out" more than usual), but it was not so "different" that I suspected a rewrap, at least not at first. It was from "Computers4Sure.com". They did have a pretty good price - maybe there's a reason...

Mail order companies tend to be worse about this. First, their margins tend to be lower so "eating" bad product just isn't in the cards. Second, they aren't nearby so they know you can't come down and kick their asses over it, you can only pay shipping to send it back and run the crapshoot that they don't QA test the gear, reshrink it, and send you the exact same thing back with a little note saying "tested OK"

me too

I just got mine in today and I noticed many scratches on the case. Pretty odd I thought.

I just received my 2nd unit from Buy.Com, no such problem.

Who did you buy them from, that came with scratches?

Computers4sure.com (an office depot company).

amazon

hi, may i ask one question?

I allready have the WAG54G v1.2 over ISDN. If i get the wrtsl54gs, and put it in repeater mode, should i be able to connect a usb hard disk on it and share it with all the other clients?

i do not want to use the wag just for the dsl modem and then have the dchp server to be the wrtsl54gs, because i will need then one more router or ap to put it as a repeater one floor down...

thanks...

hi, may i ask one question?

I allready have the WAG54G v1.2 over ISDN. If i get the wrtsl54gs, and put it in repeater mode, should i be able to connect a usb hard disk on it and share it with all the other clients?

i do not want to use the wag just for the dsl modem and then have the dchp server to be the wrtsl54gs, because i will need then one more router or ap to put it as a repeater one floor down...

thanks...

The stock firmware 2.00.0 and 2.00.1 seems to have inherited the old POST authentication/length, ezc vulnerabilities of the WRT54G described here: http://secunia.com/advisories/16806/. I noticed it while scanning through the 2.00.1 source code and I've been able to at least try the restore.cgi bug.

So take the usual precautions, secure your wireless, disable remote management... or install OpenWRT.

BTW, mine also came with scratches. It was from Amazon.

Well like any other "router" type device, you can disable specific functions and dumb it down if you want to.

Like to use it as an AP just set a new static LAN IP different from .1 and turn off DHCP server.

To use it as just as a NAS, turn off the radio too. I think itll make a pretty nice just plain old Network Attached Storage device.

What do you mean by "repeater"? Do you mean you will run an ethernet wire from WAG-LAN to SL-LAN? If so, then yeah this will work great.

If you mean WDS when you say repeater, I don't think the native Linksys firmware supports WDS (Wireless Distribution System) although I didn't really poke through it much. So you might need to load OpenWRT to do "repeater". Although that raises the problem of does the WAG support WDS.

Thanks vincentfox for your answer.

I have allready disabled the DCHP in WAG. What i want to do is to put the SL one floor down, wirelessly connected with the WAG in order to extend the coverage of the wireless network. If this is the WDS then yes i want to use it like that.

The official firmware i have for the WAG from LinkSys, supports WDS. if i enable WDS in SL, can i still use the usb hard drive in SL for the network?


and to add something more on that... the DCHP relay mode that all the LinkSys products have, works only if the SL will be connected with a cable or it can work if it is wifi?

The NAS sharing is independent of other functions performed. So WDS would not "interfere" with using it as a NAS device if that is what you mean. As I said, I don't have the Linksys firmware on my SL unit right now so I cannot verify if it has WDS in the menus. Someone else know?

Why would you need DHCP relay? You are doing one big happy WDS LAN so as long as there is a server somewhere on the network you should be all good.

USB clock?

Has anyone seen a USB clock device? It would be cool if there were a little thumb-device powered by a watch battery that I could synch the SL time from. For times when a network time source is not readily available.

http://www.digitball.biz/ls530.php

USB clock?

Yeah I had seen those "USB Clock Drive" devices in some web searches. However, my guess is it's a cheap watch mechanism stuck into the same piece of plastic without any connection to the USB interface. I say this because none of the places I ever see this device listed says anything except "displays time and temperature".

Not to be blunt....

Couldn't you use a usb drive as root file system and swap device? (of course keeping the firmware as /boot and home to all the speed entitled binaries)

check this out:
http://www.winischhofer.at/linuxsisusbvga.shtml

usb VGA would definitley be possible, and I would think that adding at least USB keyboard functionality into the kernal would be super-easy, we now have a box that is truly interactive!

Tofu SL goodness!

http://www.polarcloud.com/tofu

Someone pointed out to me that a GPS could also act as a reference time source. However it seems like gross overkill. Also dependent on having a view of the sky. Be nice to find a cheap and simple battery-powered clock that could be read via USB-serial.

You could built yourself a real time clock device and hook it up to the router using the SPI protocol and install it inside the device. Look for some easy schematics on the web for a very simple real time clock IC.

My soldering skills are that I can manage putting wires together without probably burning myself or damaging anything. Probably. I'd prefer something that required at most taking an assembled device and soldering a few wires into place. But I'll look into it.

First RETAIL sighting

I saw SL on the shelf at Frys Electronics in Sacramento, CA yesterday 2/18/2006.

Also WRT54GL on the shelf.

What about us users in europe (denmark) ?
Can't even seems to find it anywhere online, that will ship to denmark, within european union :/

I had a chat with the linksys staff a few days ago, I was asking if there are any plans to release the WRTSL54GS in Europe (Germany). The answer was a mixture of "we don`t have any plans to release it in Europe" and "I just don`t know", so my hopes are that the second guess will be right. Would be a shame if we had to import it.