Posted: Tue Sep 23, 2008 19:42 Post subject: Mega build V24_TNG svn10404 working well on WL-500gPv2
Answered my own question the other evening... I visited "downloads/others/eko" and read Eko's "readme.txt". The last paragraph reads:
"General rules: if you have old router with 4702 (4710) cpu and mini-pci
radio, you MUST use VINT build, if you have 5354 based router, you must
use NEWD build. All other routers can run both (VINT or NEWD) builds."
Figuring that a "NEWD" build produced by Eko after build 10137 might include stable USB storage support for the BCM5354, I downloaded "dd-wrt.v24-10404_NEWD_mega.bin" (dated Sept. 19th, 2008) and applied that build to my WL-500g Premium v2.
Printing continues to work and USB storage seems to be just as stable as with this post's 10137 mini build. I also have the VPN server running fine from jffs. Add the http web and ftp server capabilities I've gotten to work and, well, wow... dd-wrt is a winner!
I'll definately be making a dd-wrt donation...
SirSilentBob: I suspect there may be some residual data in NVRAM that isn't getting cleared and may be causing your USB printer sharing issues. I experienced that when jumping between various builds (wireless settings for instance). Or perhaps your default firewall rules have become the source of the issue. I had to use firewall builder to re-write my NAT and FW rules to resolve port forwarding issues. It turned out to be a boon because I now have a much better handle on exactly which traffic is permitted from/to which networks and what traffic is allowed into the router. For instance, I am explicitely allowing traffic on TCP ports 9100, 9101, and 9102 that originates from the internal network into the router.
Don't know, I have done the proper resets before and after flashes. Everything seems to be working so far.....knock on wood. I have not printed outside of the network, so I have not messed with that part of it, but I'll probably try printing over a VPN from a work computer sometime to see how that works. I imagine it will work fine, since I can get into the routers GUI and whatnot over VPN with no firewall issues. I'm just not keen about making port 9100 open on the wan because I don't want some script kiddie port scanner to find it and I come home and find all my paper and toner used up from someone printing "Lol I hacked your gibson!" a thousand times, heh. _________________ Netgear R7000 w/r31780M <KONG> build
Netgear R6700 (Un-opened with stock. My backup/emergency router if the R7000 takes a dump...)
2x Buffalo WHR-HP-GN 28493 (Used for 2.4 Ghz bridge when needed.)
Asus WL-500g Premium (1x v1 & 1x v2) (Still have, but retired for now.)
1x Linksys WRT54G v8 >>DD-WRT v24SP1 (The other routers needed something to point at and make fun of.)
Oh, I didn't mean that I opened port 9100 to the WAN - I wouldn't do that either (for the reason you mention). I meant that I opened TCP ports 9100, 9101, and 9102 to traffic traveling to/from the router from the internal network (192.168.1.0/24). No WAN involved here...
What I was thinking is that perhaps your printer sharing issues were linked to an odd firewall rule(s), like my Port Forwarding issues were.
The nice thing about Firewall Builder is the clean, graphical nature of what is going on. I couldn't make heads or tails of "iptables" at the command prompt. Too bad it's such a buggy product though - v3 will crash if I try to save or load a set of rules (Windows XP version) so I end up having to recreate all rules each time I wish to make a change.
I went to try that firewall builder and half of what I clicked on made the program crash... I never got beyond the initial setup where I select the firewall type/os it uses. Oh well, guess I'll wait for a later release. Ipchains is an effective powerful system, just a real bitch to do anything with it on the command line.
It would be nice, because my work computer uses a static IP, and I could easily open 9100 only to that IP, and then print directly to my home printer from work, without having to connect via VPN or anything. _________________ Netgear R7000 w/r31780M <KONG> build
Netgear R6700 (Un-opened with stock. My backup/emergency router if the R7000 takes a dump...)
2x Buffalo WHR-HP-GN 28493 (Used for 2.4 Ghz bridge when needed.)
Asus WL-500g Premium (1x v1 & 1x v2) (Still have, but retired for now.)
1x Linksys WRT54G v8 >>DD-WRT v24SP1 (The other routers needed something to point at and make fun of.)
CPU revision is: 00029029
Linux version 2.4.36 (bin@dd-wrt) (gcc version 3.4.6 (OpenWrt-2.0)) #1917 Tue Oc
t 14 15:43:07 CEST 2008
Setting the PFC to its default value
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 noinitrd cons
ole=ttyS0,115200
CPU: BCM5354 rev 3 at 240 MHz
Using 120.000 MHz high precision timer.
Calibrating delay loop... 239.20 BogoMIPS
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: no core
PCI: Fixing up bus 0
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-0 with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 3) is a 16550A
PCI: Setting latency timer of device 00:01.0 to 64
PCI: Setting latency timer of device 00:05.0 to 64
sb_doattach: incoming bus is PCI but it's a lie, switching to SB devid:0x4318
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
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
Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 131072
Physically mapped flash: Filesystem type: squashfs, size=0x20847d
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00020000 : "cfe"
0x00020000-0x007f0000 : "linux"
0x00102800-0x00310000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o
nly
0x007f0000-0x00800000 : "nvram"
0x00310000-0x007f0000 : "ddwrt"
sflash not supported on this router
Initializing Cryptographic API
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 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux 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 (squashfs filesystem) readonly.
Mounted devfs on /dev
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
USB20H fcr: 0x64
USB20H shim cr: 0x8f7
USB20H syn01 register : 0xfe00fe
USB20H syn03 register : 0x1
PCI: Setting latency timer of device 00:03.1 to 64
ehci_hcd 00:03.1: PCI device 14e4:471a
ehci_hcd 00:03.1: irq 6, pci mem b8003800
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:03.1: illegal capability!
ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
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.
Journalled Block Device driver loaded
hub.c: new USB device 00:03.1-1, assigned address 2
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: new USB device 00:03.1-1.1, assigned address 3
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: JetFlash Model: TS512MJF2A Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 1024000 512-byte hdwr sectors (524 MB)
sda: Write Protect is off
Partition check:
/dev/scsi/host0/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan0 entered promiscuous mode
device eth1 entered promiscuous mode
device vlan1 entered promiscuous mode
vlan1: Setting MAC address to 00 22 15 24 22 1b.
vlan1: dev_set_promiscuity(master, 1)
vlan1: dev_set_allmulti(master, 1)
vlan1: dev_set_promiscuity(master, -1)
device vlan1 left promiscuous mode
vlan1: dev_set_allmulti(master, -1)
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
Warning: DQ5 raised while program operation was in progress, however operation c
ompleted OK
Posted: Thu Nov 27, 2008 19:14 Post subject: usb.c: USB device not accepting new address=2 (error=-71)
About the "usb.c: USB device not accepting new address=2 (error=-71)"
I found this link on IBM where they describe this problem in more details. It is a kernel 2.4.X timming bug. Maybe you can fix it by just including a sleep somewhere into the usb module? Or maybe there is already a kernel patch? Please look into it. Seems we can finally fix this problem! Tks
Adding a sleep 5 prior to the mount command in my usb.startup script solved the problem of my USB-Stick not being mounted properly. It holds for several reboots now :D
My usb.startup looks now like this:
sleep 5
mount /dev/scsi/host0/bus0/target0/lun0/part1 /opt
sleep 5
I think it will solve the problem because I never had any problem mounting the USB-disk manually after startup. Just the startup-script did not work.
I have a Asus wl500-gP (V2) with dd-wrt V24-SP1(SVN revision 10012).
Adding a sleep 5 prior to the mount command in my usb.startup script solved the problem of my USB-Stick not being mounted properly.
That's not the same problem. usb error -71 happens when device is inserted, preventing it being recognized by the system. We can't even see it on dmesg.
Posted: Fri Nov 28, 2008 8:05 Post subject: Re: usb.c: USB device not accepting new address=2 (error=-71
Newgel wrote:
About the "usb.c: USB device not accepting new address=2 (error=-71)"
I found this link on IBM where they describe this problem in more details. It is a kernel 2.4.X timming bug. Maybe you can fix it by just including a sleep somewhere into the usb module? Or maybe there is already a kernel patch? Please look into it. Seems we can finally fix this problem! Tks
Posted: Fri Nov 28, 2008 23:07 Post subject: Re: usb.c: USB device not accepting new address=2 (error=-71
Eko wrote:
Try this build:
You are the man! This build is working perfectly. I've rebooted it a few times, turned it off and on again with and without the usb hub connected and it always recognized all devices (USB 2.0 HUB, printer and USB HDD). No more error 71 !!
Here is an output of hdparam when using USB 1.1 and USB 2.0.
USB 1.1:
root@Vortex:~# hdparm -tT /dev/scsi/host0/bus0/target0/lun0/part1
/dev/scsi/host0/bus0/target0/lun0/part1:
Timing cached reads: 2 MB in 2.22 seconds = 922.52 kB/sec
Timing buffered disk reads: 4 MB in 4.48 seconds = 914.29 kB/sec
USB 2.0:
root@Vortex:~# hdparm -tT /dev/scsi/host0/bus0/target0/lun0/part1
/dev/scsi/host0/bus0/target0/lun0/part1:
Timing cached reads: 62 MB in 2.01 seconds = 30.85 MB/sec
Timing buffered disk reads: 30 MB in 3.06 seconds = 9.80 MB/sec
I think you can commit your changes into the official sources and close bug #587
Joined: 02 Nov 2008 Posts: 12 Location: Davidsonville, Md
Posted: Sat Nov 29, 2008 3:27 Post subject: usb fixes
Any chance of this being included in a mega release anytime soon?
I am running dd-wrt on my ASUS WL500GP V2 and thats the only thing that is not working.. This would be great!
I can confirm that this build fixes USB startup and automount on my Asus WL-520gU when USB2.0 support is enabled in GUI. My setup is similar to Newgel's. Rebooted 10 times in a row - via GUI and via "reboot" command in the Telnet session - and my USB 2.0 hub with plugged in printer and USB flash drive were always recognized with no errors, and drive mounted. Before it was hit and miss, even with the latest 10991 build that I was using so far... _________________ Asus WL-520GU /w Tomato 1.23 ND USB Mod
Joined: 02 Nov 2008 Posts: 12 Location: Davidsonville, Md
Posted: Sun Nov 30, 2008 14:46 Post subject:
Looking good!
Found the mega release and flashed it..
Other than a spontaneous reboot when I plugged in the usb drive, things are looking great. Mounted it as vfat and was able to read/write files with no crash/reboot.
Many thanks!
Asus WL500GP V2 with DD-WRT v24-sp2 ( 11/25/08 ) mega
Posted: Thu Jan 29, 2009 21:07 Post subject: what version of dd-wrt
What version of dd-wrt someone could suggest to me for dir-320 +usb flash ?
I wrote in other forum, that with latest (2009-01-21) version I had problems, that system freezes for some seconds and stops responding; then comes back in ~10secs; happens in every often (in a minute) 30%ping loss in LAN ping.
(?)
janis
I never got beyond the initial setup where I select the firewall type/os it uses. Oh well, guess I'll wait for a later release. Ipchains is an effective powerful system, just a real bitch to do anything with it on the command line.
with MANY_PORTS SHARE_IRQ SERIAL_PCI en
