Har själv haft en hel del WRT54G/GS/GL-enheter, för att inte tala om de man satt i drift via jobbet. För en månad sen dog min första inköpta WRT54GS och med tanke på att det var en v1.0 så hade den närmare 6 år på nacken. Mer prisvärd produkt är svårt att hitta.
Men då var det dags att hitta en ersättare. Det är minst sagt en djungel om man ska ha välfungerande modern hårdvara som dessutom har fullgott stöd för DD-WRT. Någon riktigt WRT54GS-ersättare finns inte, men det närmaste jag hittat är WRT320N.
WRT320N är en relativt ny enhet och dokumentation är det sparsamt med. Jag tog tillfälle i akt och slängde ihop en lista med problem. Den är ursprungligen skriven för DD-WRT forumet och därmed på engelska. Vill hålla er up-to-date so kolla där, jag kommer inte underhålla denna lista på detta forum.
Known issues with the WRT320N
Complicated to debrick
As the Common Firmware Environment[1.1] has a typo in the command that flashes from TFTP[1.2] a bricked unit must be unbricked with the help of serial console-access[1.3]. To connect to the serial interface of the device, which is located at the bottom and inside the WAN port[1.4], one must use an USB/RS232 to LVTTL (TTL 3,3V)[1.5] adapter as otherwise you can cause damage on your device[1.6].
Also, as the reset button is not enabled in CFE[1.3], to erase NVRAM from within CFE one must issue the command "erase nvram" followed by "reboot"[1.3]. To flash a new image within CFE one must issue the command "flash -ctheader : flash1.trx" and then proceed with the commonly known procedure of TFTP-flashing[1.3]. The issues with the faulty CFE can dealt with once TJATG for this device is in working order[1.7].
If one does not have serial console-access it is possible to erase NVRAM by grounding GPIO6 for 6-8 seconds[1.3]. As seen in a picture of the PCB[1.8] GPIO6 is on top of "19" and right of "20". More details about grouping GPIO6 can be found in the forum[1.9]
Update:
A work-around[1.10] involving the WPS-button is said to be available as of 2009-12-19 or by build 13493[1.10].
Sources:
[1.1] http://www.linux-mips.org/wiki/Common_Firmware_Environment
[1.2] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[1.3] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[1.4] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[1.5] Could someone confirm this and also provide a credible source?
[1.6] Could someone confirm this and also provide a credible source?
[1.7] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[1.8] http://www.dd-wrt.com/phpBB2/files/229_527.jpg
[1.9] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[1.10] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=63004&postdays=0...
30-30-30 reset does not work
Linksys wired the reset button to the wrong GPIO, hence a 30-30-30 reset will not work[2.1].
Issue relevant as of:
2010-01-17
Sources:
[2.1] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
UPnP is broken
This issue is believed to be a general issue with DD-WRT and the Linux 2.6 kernel[3.1][3.2] (which so far is only used by a few devices, one of them being WRT320N). Many of the UPnP-related issues seem to come from the UPnP-daemon crashing[3.3][3.4]. Some cases report that a viable workaround is changing the UPnP daemon to miniupnpd[3.5][3.6].
Update:
Issue is said to be fixed as of 2009-12-28 by build 13527[3.7].
Sources:
[3.1] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=61674&postdays=0...
[3.2] http://svn.dd-wrt.com:8000/dd-wrt/ticket/1306
[3.3] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[3.4] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[3.5] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=61674&postdays=0...
[3.7] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=63539&postdays=0...
CPU use averages to 100%
The web-interface tends to show an average CPU use of >=100%[4.1] but when checking top via SSH there doesn't seem to be any process responsible for such use of resources[4.2][4.3], still many users report the device being slow[4.4]. Some users have found the UPnP daemon to crash within a few minutes and that being the source of high CPU utilization[4.5], turning off UPnP seems to help these cases[4.6][4.7].
Update:
Issue is said to be fixed as of 2009-12-28 by build 13527[4.8].
Sources:
[4.1] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.2] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.3] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.4] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.5] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.6] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.7] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[4.8] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=63539&postdays=0...
No support for VLAN-tagging (IEEE 801.2Q) or Jumbo Frames
The switch chip, BCM53115, which can also be found in the Linksys WRT610N, does on hardware-level support both VLAN-tagging (IEEE 801.2Q) and Jumbo Frames[5.1]. However, since the chip is currently lacking a kernel driver the factory configuration cannot be changed. Note that the option "Assign WAN Port to Switch" actually works at the kernel IP level by adding the Internet "vlan2" device to the main bridge[5.2].
Issue relevant as of:
2010-01-17
Sources:
[5.1] http://www.broadcom.com/collateral/pb/53115-PB01-R.pdf
[5.2] http://www.dd-wrt.com/wiki/index.php/Linksys_WRT610N#No_VLAN_...
The LAN-ports are labeled backwards
This means that port labeled as 4 on the device is port 1 when it comes to VLAN-configuration, 3 is 2, 2 is 3 and 1 is 4[6.1]. The WAN-port which is labeled 0[6.1].
Issue relevant as of:
2009-12-18
Sources:
[6.1] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
IPv6-related problems
There is very little consistent information available on this issue but it seems to be related to radvd[7.1]. This is some of the feedback gotten from users:
[7.2]"Thanks for the build, The ipv6 using the HE tunnel broker doesn't seem to be working."
[7.3]"Thank Eko, the ipv6 seems to be coming up fine now with the 13000 build. I don't see any errors in the log file except that radvd is looking for radvd.conf file in the wrong place. I fixed it by addig radvd -C /tmp/radvd.conf in the startup script. After that cliets get the ipv6 address right, but can't connect to any ipv6 address. Tracert or ping yield 1 Destination net unreachable. I am using HE tunnel broker and I am using the same scripts I used on the 11296M NEWD Eko build on my old WRT54GS ver1 router (which was working for months without any issues)"
[7.4] "After some research, it seems creating the ipv6 over ipv4 tunnel is failing."
[7.5]: "I'm currently running 13000M and I have problems with the ipv6. When I try to create a tunnel interface I get an ioctl: no such device."
[7.6]: "Among other things ipv6 is the main reason I use dd-wrt, still no support with the 12982 build, it would be nice if it is supported. daemon.info radvd[792]: version 1.2 started daemon.err radvd[792]: can't create socket(AF_INET6): Address family not supported by protocol"
Issue relevant as of:
2010-01-17
Sources:
[7.1] http://www.litech.org/radvd/
[7.2]http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0&postorder=asc&start=20
[7.3]http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0&postorder=asc&start=152
[7.4]http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0&postorder=asc&start=159
[7.5]http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0&postorder=asc&start=198
[7.6]http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0&postorder=asc&start=85
Enabling the OpenVPN client bricks the device
The generation of OpenVPN certificates bricks the device due to NVRAM overflowing[8.1][8.2]. The NVRAM is 64KiB big (0x007f0000-0x00800000)[8.2][8.3], but is unfortunately limited to 32KiB as the CFE must be able to read from it[8.4].
Issue relevant as of:
2010-01-17
Sources:
[8.1] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[8.2] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...
[8.3] http://svn.dd-wrt.com:8000/dd-wrt/ticket/986
[8.4] http://www.dd-wrt.com/phpBB2/viewtopic.php?t=58566&postdays=0...