You're right, I should stick up some lsusb output and other data for each device maybe we'd be able to pick this apart. Unfortunately I left the BU-353 at home, will collect more information tonight perhaps. A bunch of negatives is not as helpful. It'd be nice to see one device that DID work so I could test out the concept at least.  From what I've read getting good usb-serial converter driver support in linux is an ongoing problem.

Beginning to wonder if it'd be more frutiful to spend time hacking working serial ports on the SL and just use a plain serial GPS.

Client mode...

I purchased another WRTSL54GS for a project and for the life of me I can't kick it into client mode.

Some settings I've tried:

I always set the following

nvram set wl0_mode=sta
nvram set wan_ifname=vlan1

and here are several settings I've tried for lan_ifnames

nvram set lan_ifnames="vlan0 eth1 eth2 eth3"

nvram set lan_ifnames="vlan0 eth1 eth3 eth4"

nvram set lan_ifnames="vlan0 eth2 eth3 eth4"

In fact I usually get locked out of the lan at some point and end up reloading the linksys bin,
resetting to factory and then uploading the openwrt bin.

I've tried the old kaloz bin and the latest? ndb version.

Any help appreciated regarding these settings.

I set wan as eth2 (only because I didn't want to re-write all of the other scripts.)
wan_device=vlan1
wan_proto=dhcp
wan_ifname=eth2

I also set the eth1 as OLD and put an IP address on it as a fall back...

old_proto=static
old_ipaddr=192.168.33.99
old_ifname=eth1
old_netmask=255.255.255.0

Lan should be default.

lan_netmask=255.255.255.0
lan_ipaddr=192.168.1.1
lan_proto=static
lan_ifname=eth0
lan_ifnames=vlan0 eth1 eth2

Not sure what 'lan_ifnames=vlan0 eth1 eth2' does but, it comes back every time I reboot.

I got wpa_supplicant working, but still need ifplugd.  And still need usb-serial-pl2303 to work!

Mike (mrdvt92)

Update: I've got all this working now see http://gpsd.davisnetworks.com/bin/view/ … GPSTracker

(Last edited by mrdvt92 on 3 Jun 2006, 15:39)

Wouldn't it be simpler to break the bridge, and then set wan_device and wan_ifname to the WiFi interface?

Are you aiming for client-bridged or client-routed?

I'm not trying to bridge at all.

client-routed where the wrt provides all of the IP roaming capability.

My current setup is at http://gpsd.davisnetworks.com/bin/view/ … tWRTSL54GS

(Last edited by mrdvt92 on 14 Mar 2006, 04:07)

By "break the bridge" I meant the existing bridge between LAN and WLAN. Use brctl show.

Oh! I understand what you were trying to get at.  Why reassign the eth2 (wireless) to "wan" when you can just change the eth2 to wlan and set it up some other way.  Well, you can do that, but then you'll have to rewrite the S45firewall and S50dnsmasq scripts.

Charles started a Wiki hardware page, I added some info:

http://wiki.openwrt.org/OpenWrtDocs/Har … /WRTSL54GS

netddos recently noted that USB LED in front seems to be locked into ON state, otherwise does nothing. Not sure what is up with this? Does it actually flash with original Linksys firmware? I used the original firmware very little and can't recall.

I've just started getting parts together for serial port, so haven't verified the serial port table at this moment.

(Last edited by vincentfox on 15 Mar 2006, 16:42)

Gang, I'm hoping one of y'all is sufficiently flush and motivated, to donate an SL to the developers.

I'm tapped out on funding for my hobby at the moment.  When there are major problems nbd or kaloz can send
me firmware to try out, but this is time-consuming and not nearly as good as if they had one themselves.

I did donate my first SL to Kaloz earlier, but a Kamikaze build apparently bricked it and without JTAG there
seems to be no way to revive it.

Well, imho the flash chip died, as the bug comes from the damaged nvram - something Kamikaze never touches at all. Anyways, anyting else then Kamikaze with kernel 2.6 should work just fine.

Well either way, it's dead correct?

By the way, the Wiki page for SL is correct, have both serial ports working fine at this time.  Setserial and stty are essential add-ons.

is it just me or RC5 kills the lan port of SL?

For example...

wired lan is inserted in port 1 of SL unit

i power cycle OR reboot the router via reboot command..

i wait for it to boot up again..

port 1 is dead...

i switch it to any other ports..say port 2...then it works..

i power cycle or reboot again...port 2 is dead..so i switch it any other port (including port 1)  then it works agan..

is it just me or is this a bug?

Help with WRTSL54GS and Lacie USB Harddrives

First thanks for all the hard work from many people on openwrt.  I downloaded and flashed my WRTSL54GS with no problems and started to add packages.  The various documentation in the  openwrt wiki and macsat.com have been great.  I have been able to add USB devices and watched as they were auto mounted, that was great.  Now I'm trying to mount an old LaCie 20 GB external harddrive, the enclosure supports USB 1.0 and firewire.  I'm running WhiteRussian RC5.    The USB Hardrive is attached to a USB 2.0 4 port hub with two other memory sticks attached at the same time.  Here is the output of dmesg after a fresh boot with all the devices attached and then a removal and re-attachement of the USB Harddrive.

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:03.0 to 64
usb-ohci.c: USB OHCI at membase 0xb8003000, IRQ 6
usb-ohci.c: usb-00:03.0, PCI device 14e4:4715
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Enabling device 01:02.0 (0000 -> 0002)
PCI: Setting latency timer of device 01:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xc0187000, IRQ 2
usb-ohci.c: usb-01:02.0, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Enabling device 01:02.1 (0000 -> 0002)
PCI: Setting latency timer of device 01:02.1 to 64
usb-ohci.c: USB OHCI at membase 0xc0189000, IRQ 2
usb-ohci.c: usb-01:02.1, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
hub.c: new USB device 01:02.0-1, assigned address 2
uhci.c: USB Universal Host Controller Interface driver v1.1
hub.c: USB hub found
hub.c: 4 ports detected
PCI: Enabling device 01:02.2 (0000 -> 0002)
ehci_hcd 01:02.2: PCI device 1033:00e0
ehci_hcd 01:02.2: irq 2, pci mem c01ba000
usb.c: new USB bus registered, assigned bus number 4
ehci_hcd 01:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
hub.c: usb_hub_port_status (2) failed (err = -145)
hub.c: usb_hub_port_status (2) failed (err = -145)
hub.c: usb_hub_port_status (2) failed (err = -145)
hub.c: usb_hub_port_status (2) failed (err = -145)
hub.c: get_hub_status failed
usb.c: USB disconnect on device 01:02.0-1 address 2
device eth0 entered promiscuous mode
hub.c: new USB device 01:02.2-1, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
hub.c: new USB device 01:02.2-1.1, assigned address 3
device eth2 entered promiscuous mode
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model: USB DISK Pro      Rev: PMAP
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor:           Model: USB DISK Pro      Rev: PMAP
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi removable disk sdb at scsi0, channel 0, id 0, lun 1
SCSI device sda: 243200 512-byte hdwr sectors (125 MB)
sda: Write Protect is off
Partition check:
/dev/scsi/host0/bus0/target0/lun0: p1
SCSI device sdb: 2880 512-byte hdwr sectors (1 MB)
sdb: Write Protect is off
/dev/scsi/host0/bus0/target0/lun1: p1 p2 p4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
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
hub.c: new USB device 01:02.2-1.3, assigned address 4
scsi1 : SCSI emulation for USB Mass Storage devices
  Vendor: Generic   Model: Flash Disk        Rev: 7.78
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sdc at scsi1, channel 0, id 0, lun 0
SCSI device sdc: 64000 512-byte hdwr sectors (33 MB)
sdc: Write Protect is off
/dev/scsi/host1/bus0/target0/lun0:<7>jffs2: attempt to mount non-MTD device 08:01
p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
b44: eth1: Link is up at 100 Mbps, full duplex.
b44: eth1: Flow control is off for TX and off for RX.
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,1)
hub.c: new USB device 01:02.2-1.4, assigned address 5
scsi2 : SCSI emulation for USB Mass Storage devices
jffs2: attempt to mount non-MTD device 08:11
imq driver loaded.
IPP2P v0.8.1_rc1 loading
HTB init, kernel part version 3.17
HTB init, kernel part version 3.17
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
SCSI disk error : host 0 channel 0 id 0 lun 1 return code = 70000
I/O error: dev 08:11, sector 0
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,17)
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
scsi: device set offline - not ready or command retry failed after bus reset: host 2 channel 0 id 0 lun 0
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
jffs2: attempt to mount non-MTD device 08:21
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,33)
SCSI disk error : host 0 channel 0 id 0 lun 1 return code = 70000
I/O error: dev 08:11, sector 0
FAT: unable to read boot sector
jffs2: attempt to mount non-MTD device 08:12
SCSI disk error : host 0 channel 0 id 0 lun 1 return code = 70000
I/O error: dev 08:12, sector 0
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,18)
SCSI disk error : host 0 channel 0 id 0 lun 1 return code = 70000
I/O error: dev 08:12, sector 0
FAT: unable to read boot sector
jffs2: attempt to mount non-MTD device 08:14
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,20)
usb.c: USB disconnect on device 01:02.2-1.4 address 5
hub.c: new USB device 01:02.2-1.4, assigned address 6
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 6
jffs2: attempt to mount non-MTD device 08:21
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,33)

df gives the following:

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 1024      1024         0 100% /rom
/dev/mtdblock/4           6272      2884      3388  46% /
none                     15276        56     15220   0% /tmp
/dev/scsi/host0/bus0/target0/lun0/part1   121328     46776     74552  39% /mnt/disc0_1
/dev/scsi/host1/bus0/target0/lun0/part1    31715     16869     14846  53% /mnt/disc2_1
/dev/scsi/host0/bus0/target0/lun1/part4     1424       487       937  34% /mnt/disc1_4

One of the memory sticks has two partitions, a main one the mounts like any other stick, and the second one simulates a floppy and mounts on window machines as A:\ or B:\

Any hints, ideas, or suggestions on how to mount the LaCie USB external HardDrive would be great.

Hi:
    How does one get the lid off of a wrtsl54gs?  I've been trying for a while. I admit that I'm a little timid as I don't want to destroy anything......  Thanks in advance.

you need to remove the rubber feet and underneath these feet there is a phillips head screw

Thanks!!!!!!!

Is there a package with stty in it.  I download mine from some web site.  It works but.  I like to keep everything in packages.  (My serial is via USB pl2303).

Mike (mrdvt92)

If someone has a working config for RC5 for this router, could you please post your NVRAM values for lan and wan settings?

nvram show | grep lan
nvram show | grep wan
nvram show | grep wl0

I've managed to unbrick mine, but wan and lan are reversed (actually the bridge is wan + wl0 and vlan0 is dead...)

It's a software setting, but any attempt on my part to fix it results in a bricked router.  I'm about to make a serial cable, bu tI've had bad luck today so I'm laying off any fine work - I don't want to fry any hardware.....  :-)

--Yan

Here are mine.  RC5's working good here, but who knows if it's optimal.

# nvram show | grep lan
size: 3847 bytes (28921 left)
vlan0ports=0 1 2 3 5u
lan_netmask=255.255.255.0
lan_stp=0
lan_hwaddr=[MAC]
lan_ifnames=eth0 eth2 eth3 eth4
lan_ipaddr=192.168.1.1
lan_proto=static
vlan1hwname=et0
vlan1ports=4 5
old_lan_netmask=255.255.255.0
lan_ifname=br0
vlan0hwname=et0
wan_device_old=vlan1

# nvram show | grep wan
size: 3847 bytes (28921 left)
wan_device=eth1
wan_gateway=0.0.0.0
wan_netmask=0.0.0.0
wan_proto=pppoe
wan_hwaddr=[MAC]
wan_ifnames=eth1
wan_iface=eth1
wan_ipaddr=10.99.99.99
wan_mtu=1492
wan_ifname=ppp0
wan_hostname=OpenWrt
wan_device_old=vlan1

root@OpenWrt:~# nvram show | grep wl0
size: 3847 bytes (28921 left)
wl0_net_mode=mixed
wl0_frameburst=on
wl0_akm=psk
wl0_infra=1
wl0_country_code=ALL
wl0_wme_sta_be=15 1023 3 0 0 off
wl0_ifname=eth2
wl0_wme_sta_bk=15 1023 7 0 0 off
wl0_mrate=0
wl0_mode=ap
wl0_ap_isolate=0
wl0_gmode=6
wl0_wme_no_ack=off
wl0_ssid=Tuscan
wl0_dtim=1
wl0id=0x4320
wl0_wme_ap_vi=7 15 1 6016 3008 off
wl0_closed=1
wl0_rate=0
wl0_plcphdr=long
wl0_macmode=disabled
wl0_radioids=BCM2050
wl0_wme_ap_vo=3 7 1 3264 1504 off
wl0gpio2=0
wl0_phytype=g
wl0gpio3=0
wl0_lazywds=1
wl0_afterburner=auto
wl0_antdiv=-1
wl0_wpa_psk=[password]
wl0_net_reauth=36000
wl0_auth=0
wl0_wme=off
wl0_radius_port=1812
wl0_wme_sta_vi=7 15 2 6016 3008 off
wl0_wme_sta_vo=3 7 2 3264 1504 off
wl0_maxassoc=128
wl0_phytypes=g
wl0_wep=disabled
wl0_frag=2346
wl0_country=ALL
wl0_rateset=default
wl0_wep_bit=64
wl0_rts=2347
wl0_wpa_gtk_rekey=3600
wl0_key=1
wl0_radio=1
wl0_bcn=100
wl0_hwaddr=[MAC]
wl0_gmode_protection=off
wl0_wme_ap_be=15 63 3 0 0 off
wl0_corerev=9
wl0_channel=0
wl0_wds_timeout=1
wl0_wme_ap_bk=15 1023 7 0 0 off
wl0_auth_mode=none
wl0_crypto=aes

Has anyone measured the current draw on this AP with the radio on?

The wall wart says 2A, but I am wondering if that's really true....  I have a 12V 0.75A supply that I'd like to use.  The USB hub will be powered by a separate 5V  0.75A supply.

Thanks,

--Yan

I've put my nvram settings (client mode wireless) on my wiki.

http://gpsd.davisnetworks.com/bin/view/ … GPSTracker

All I'm missing is an AP roaming capability?  Anyone know how to set that up?
Mike

I dug up my trusty Fluke 77 and it says .24 amps, with no wired ethernet connections but with the radio running.  Booting is .16 amps, so I guess the radio draws some .08 amps.

--Yan

This is exactly what I calculate...
100 mW RF power at about 10% RF efficiency = 1 Watt (RF+heat)/12 Volts = 0.0833 Amps

(Last edited by mrdvt92 on 5 Jun 2006, 05:02)

Solved LaCie USB external haddrive problem, they were mechanically challenged.  New hard drive and now it automounts great.  Almost happy with my WRTSL54GS, got qos, samba, usb, kismet, and ssh all running.  The only thing I'm not happy with is openvpn, the backport version from kamakazi was not built with ssl and does not encrypt, unless I'm doing something wrong.

Thanks again to everyone that put so much hard work into the openwrt.

Travis

Hi all,

I am considering buying a WRTSL54GS mainly because of the USB port and, of course, the possibility to run openwrt on it.
Some of you already tested the router and its USB port and reported your results here. Thanks for the information.

There are, however, two questions that I think have not been answered yet:
- can the USB port be used with a USB hub to connect more than one device?
- how fast is data transfered over the USB port? For instance, how fast can you read and write to an USB HDD?

I know that in theory the USB hub should work and that the port is USB 2.0, which means that maximum theoretical speed is 480 Mbps.
But I would prefer to have answers based on actual experience with this router.
Practice is never exactly like theory :-).

Thanks.

Fred