Joined: 29 Jul 2009 Posts: 390 Location: kemerovo, russia
Posted: Wed Oct 27, 2010 4:43 Post subject:
DIR-320. firmware from 15280 to 15508 (http://dd-wrt.com/dd-wrtv2/downloads/others/eko/V24_TNG/svn15508/dd-wrt.v24-15508_NEWD_mini_usb_ftp.bin). after flashing device doesn't mount drives, so the startup script fails. drives are mounted with this script:
Code:
#!/bin/sh
mount -noatime /dev/scsi/host0/bus0/target0/lun0/part1 /opt
swapon /dev/scsi/host1/bus0/target0/lun0/part2
mount -o bind /opt/etc/profile /etc/profile
mount -noatime /dev/scsi/host1/bus0/target0/lun0/part1 /mmc
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Wed Oct 27, 2010 13:36 Post subject:
barryware wrote:
jumran wrote:
Thanks for the great work Eko. Build seems to be working fine on my Asus RT-N16 and VLAN support through the GUI seems to be working fine. I was able to set port 4 on the router to VLAN 3 without using any startup commands or manual command entries.
The only issue with the build and last few (5-6 builds) is that when logging to a Remote Server is enabled and security log is enabled and set high to log all Dropped, Rejected and Accepted packets, it works fine until the router is rebooted. After the reboot, Accepted packets logs somehow automatically gets set back to disabled and accepted packets are no longer logged. Re-enabling accepted packets log works again but stops functioning after a reboot. Would be nice to have this bug fixed. I think the last build that did not have this issue was 14800 series build.
I am not using stophammer. Or at least I don't think I am. It shows not running in the "service" command.
My optware is on a usb drive. settings and file permissions on the drive do not change with a build update. After updating to this build and restoring settings via fraters restore script and a re-boot, accepted packets is disabled.
This needs further verification by others. _________________ [Moderator Deleted]
Joined: 31 Jul 2009 Posts: 492 Location: Toronto, ON, CA
Posted: Wed Oct 27, 2010 14:59 Post subject:
Frater's comments seem to be valid in my case as soon as I disable the stop hammer service and reboot the router, logging accepted packets becomes enabled again. Enabling the stophammer service stop logged packets once again.
barryware wrote:
barryware wrote:
jumran wrote:
Thanks for the great work Eko. Build seems to be working fine on my Asus RT-N16 and VLAN support through the GUI seems to be working fine. I was able to set port 4 on the router to VLAN 3 without using any startup commands or manual command entries.
The only issue with the build and last few (5-6 builds) is that when logging to a Remote Server is enabled and security log is enabled and set high to log all Dropped, Rejected and Accepted packets, it works fine until the router is rebooted. After the reboot, Accepted packets logs somehow automatically gets set back to disabled and accepted packets are no longer logged. Re-enabling accepted packets log works again but stops functioning after a reboot. Would be nice to have this bug fixed. I think the last build that did not have this issue was 14800 series build.
I am not using stophammer. Or at least I don't think I am. It shows not running in the "service" command.
My optware is on a usb drive. settings and file permissions on the drive do not change with a build update. After updating to this build and restoring settings via fraters restore script and a re-boot, accepted packets is disabled.
This needs further verification by others.
_________________ Asus RT-N16 [Build King Kong 18050M NEWD-2 K2.6 + Optware + My Page]
Last edited by jumran on Wed Oct 27, 2010 16:06; edited 1 time in total
I got my WRT310N recovered from this build. It is fairly safe to say that if you have a WRT310Nv1, load this one at your own risk. Fun, fun, testing builds lol.
I'm not sure if it's the M20 or the build, but my wireless indicator is off (even though several wireless connections are active and functioning). The light for the setup button is on though.
As for VLANs, it appears that ports 1-4 are reversed (i.e. I change the VLAN for port 4 and it affects port 1).
Hi,
Flashed to my E3000(upgraded from WRT610Nv2)went OK. but something funny with ssh .cant access the router using gFTP on NokiaN810 so rollback to 15453.
Joined: 05 Dec 2009 Posts: 377 Location: Toronto, Canada
Posted: Wed Oct 27, 2010 20:42 Post subject:
RCShadows wrote:
I got my WRT310N recovered from this build. It is fairly safe to say that if you have a WRT310Nv1, load this one at your own risk. Fun, fun, testing builds lol.
I got my WRT310N recovered from this build. It is fairly safe to say that if you have a WRT310Nv1, load this one at your own risk. Fun, fun, testing builds lol.
I'd flash but I don't have JTAG handy right now, and it's the only router in the house! Not going to risk it, right now at least.
I couldn't find my JTag after a move but I did find out that the WRT310Nv1 can be put into a mode to accept tftp from a post BS made with another person that had a problem. It is not just catching the ping after a boot either.
Start the ping. While holding the reset button, power-cycle the router. The power light will flash constantly and your ping should return ttl=100. In another DOS window, have your tftp command already entered and hit return. Once tftp is done, the power light will turn solid after 30-60 seconds. Do a normal 30-30-30 and you are good to go.
I did flash with the factory image before going to DD-WRT though just to be safe. It was good to find out the "real" recovery mode on the 310 . I guess it's a normal recovery management console procedure, with the reset button thrown in that threw me. Good info for the future on these units.
Last edited by RCShadows on Wed Oct 27, 2010 23:16; edited 1 time in total
Joined: 05 Dec 2009 Posts: 377 Location: Toronto, Canada
Posted: Thu Oct 28, 2010 4:32 Post subject:
Loaded this build on my WRT310Nv1.
Unlike poor RCShadows above, this build loaded on my unit. :roll:
A few things of note:
* VLANs do not work at all.
Quote:
roboswitch: Probing device eth1: found a 5395!
* When testing VLANs, I set port 4 to be the WAN port and the WAN port as a standard LAN port. However, no change was made, even after waiting 30 seconds and rebooting as a final test. When I went to reverse the changes, the router crashed upon applying the settings and rebooted.
* Upon the first reboot after flashing and applying new settings, the device appeared to be unresponsive during boot. The proper LAN lights lit up, and the internet icon was active, but the wireless icon was not and the power light was blinking. I let this sit for about 5 minutes, after which I pulled the power, and it booted normally. I've rebooted multiple times to see if it is reproducible but it appears not.
. I guess it's a normal recovery management console procedure, with the reset button thrown in that threw me. Good info for the future on these units.
