Dir-615 E3
Upgraded from 17967 to 18000, went fine no reboot problems at all,everything else seems good and stable, did not try Factory to DD-WRT flash 18000 because i was upgrading, but the size of that file does look quite a bit bigger in size as pointed out by chateau.
Joined: 26 Apr 2011 Posts: 203 Location: Sacramento CA
Posted: Tue Dec 13, 2011 4:48 Post subject: E2100L
E2100L Upgrade from 17990 to 1800 went well. USB connection and SAMBA working OK. Same observation as others regarding wifi led not lit and web gui indicating that USB drive is not mounted.
we really need that BrainSlayer tweaks the build script so that at the end of the build process it generates a file containing the sha1/md5 hashes of the files that were built. Either a single file in the build root or each flash image with its own checksum file.
that would solve the problem (assuming you take the time to verify the hashes) created by incomplete firmware files bricking routers as the wr1043nd build 18000 is currently doing.
Joined: 17 Jun 2006 Posts: 31 Location: Seoul, Korea
Posted: Tue Dec 13, 2011 8:13 Post subject:
Successfully flashed r18000 on DIR-825 Rev. B1.
Wireless works nice so far(more test is needed), but
mounting ext3 is failed.
Here's some dmesg:
============================
<3>[ 25.030000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 27.460000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 29.840000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<6>[ 30.760000] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
<6>[ 30.760000] bonding: MII link monitoring set to 100 ms
<3>[ 30.780000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<6>[ 31.430000] device eth1 entered promiscuous mode
<4>[ 31.620000] ag7100_ring_free Freeing at 0x83b83000
<4>[ 31.620000] ag7100_ring_free Freeing at 0x83b0f000
<4>[ 31.650000] rtl8366sr_phy_setup ethUnit=1
<4>[ 31.650000] phyUnit=4 is link
<4>[ 31.660000] Writing 6
<6>[ 31.660000] device eth1 left promiscuous mode
<3>[ 32.330000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<4>[ 32.350000] ag7100_ring_free Freeing at 0x8336b000
<4>[ 32.350000] ag7100_ring_free Freeing at 0x83b83000
<4>[ 32.430000] rtl8366sr_phy_setup ethUnit=1
<4>[ 32.430000] phyUnit=4 is link
<4>[ 32.440000] Writing 6
<6>[ 33.330000] etherip: Ethernet over IPv4 tunneling driver
<4>[ 34.210000] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_exp_gre
<4>[ 34.220000] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_inbound
<4>[ 34.230000] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_outbound
<4>[ 34.230000] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_expectfn
<4>[ 34.240000] nf_nat_pptp: Unknown symbol nf_nat_need_gre
<3>[ 35.510000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 36.010000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 36.400000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 36.790000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 37.190000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 37.580000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
<3>[ 37.970000] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4)
============================
Cannot mount ext3(USB Stick).
I've not tested for ext2 or fat32 yet. But there's a problem with mounting ext3. (I'm not sure if this is USB-module related problem or FileSystem-module related problem.)
Linksys WRT160NL
I don't use USB
Befor build 17461: WiFi was unstable. Many TX/RX errors, disconnects. PPTP worked well. L2TP worked terribly.
17461: Stable WiFi (no TX/RX errors and disconnects). PPTP worked well. LED-s worked fine. L2TP worked terribly.
17967-18000: Stable WiFi. WiFi LED dont work.
L2TP work more stable:
L2TP-connection up, but after disconnects, reconnect is too long (up to several hours).
At this time log look like this:
and connection up again.
But in last builds PPTP don't work:
1. PPTP-connection up, router get IT address from porvider.
2. Оnce there is a strange outbound traffic on WAN port ~30Mb/s (my limit 5Mb/s!), and after several second (10-20 sec) PPTP tunel terminated.
3. The router automatically picks up the connection again and everything repeats.
Joined: 17 Jun 2006 Posts: 31 Location: Seoul, Korea
Posted: Tue Dec 13, 2011 8:19 Post subject:
znstyle wrote:
Cannot mount ext3(USB Stick).
I've not tested for ext2 or fat32 yet. But there's a problem with mounting ext3. (I'm not sure if this is USB-module related problem or FileSystem-module related problem.)
Is there who succeed in mounting ext3 with this r18000 build?
OK, I Tested FAT32. Automount works nice for FAT32 USB Stick.
It means, it is not USB-module related problem.
Joined: 17 Jun 2006 Posts: 31 Location: Seoul, Korea
Posted: Tue Dec 13, 2011 8:38 Post subject:
znstyle wrote:
znstyle wrote:
Cannot mount ext3(USB Stick).
I've not tested for ext2 or fat32 yet. But there's a problem with mounting ext3. (I'm not sure if this is USB-module related problem or FileSystem-module related problem.)
Is there who succeed in mounting ext3 with this r18000 build?
OK, I Tested FAT32. Automount works nice for FAT32 USB Stick.
It means, it is not USB-module related problem.
I'll test ext2 later.
OK, just tested ext2 => Success.
It means, ext2 and FAT32 works fine, but ext3 is broken.
I cannot wait for this ext3 problem to be fixed, so I've just switched my FileSystem from ext3 to ext2. It works now.
Joined: 17 Jun 2006 Posts: 31 Location: Seoul, Korea
Posted: Tue Dec 13, 2011 10:50 Post subject:
r18000 @ DIR-825 B1
I found 5 problems with this r18000 build @ DIR-825.
1. ext3 not working.
2. 'find' command missing.
3. Multi-Byte Characters(like Korean Language) are not printed properly with 'ls' command. They are printed as ???????. (question mark)
Alternatively, when I use
'for i in * ; do echo $i ; done'
command for retrieving filenames, it prints Multi-Byte Character properly.
There is no problem with Multi-Byte Charecters I/O. For example, when using 'cat', file contents with Korean charecters are printed properly.
Also I can make a directory name with Korean characters and able to change directory to it.
Just problem with 'ls', printing as ???????.
Both in ssh & telnet, 'ls' command does not support Multi-Byte Character.
(in r17461, no problem with Multi-Byte Character.)
(Seems Busybox on r18000 does not support Multi-Byte? (because, 'ls' is a busybox command.))
4. when 'ls', filenames are printed only in a single text-color. I cannot distinguish which one is a directory, which one is a symbolic link, by the text color. Both in ssh & telnet. (I'm using PuTTY, there was no problem with r17461.)
5. 'echo -n' (echo without newline) not working. This is not a critical issue, but some scripts which are made of 'echo -n' does not work properly. (It worked in r17461 and below.)
Several Problems with r18000 for me (DIR-825). I'm about to revert to r17461. _________________ Netgear R7800 - r37495M kongat 10/28/18 (Main Router)
Linksys EA8500 - OpenWrt Kong Pro Q2 5/8/19 (Sub AP)
D-Link DIR-825 - (Retired)
Joined: 12 Jan 2011 Posts: 10 Location: São Paulo, Brazil
Posted: Tue Dec 13, 2011 14:29 Post subject:
I don't know if I'm doing something stupid but my notebook (AR9285 wifi card) can't connect to dd-wrt when Wireless Network Mode is set to N-Only (2.4 GHz). I remember that in 17201 I have no problem with that and now it onlyworks with NG Mixed.
My router is a Linksys E2100L and the problem happens with any type of wireless authentication, even, open wireless.
next time read the forum and wait a few days before flashing and see what the other people are saying about that particular build.
Currently i'm still running factory after trying dd-wrt 17201 and OpenWRT backfire (i tried both rc6 and a svn trunk snapshot) but i went back to the factory image and i'm waiting for either OpenWRT or dd-wrt to publish a build i'd be happy with.
E2100L Flashed as "HOPED FOR" - Went well with full factory reset, then the usual 30/30/30 once I found the reset button!
Results - Client Bridge Routed "Works"
V.I - "Works"
WPA2 PERSONAL "Works"
Observation - Signal strength about 6 dbi increase went from 78 -80 down to 72 dbi - The main AP is next door not far but the house is brick and there is a RV parked right in the line of sight, so I have to pick up the signal off the corner where it is less focused.
Site Survey has better accuracy, note 15706 listed a lot of distant signals but 1800 list stronger signal and it would show the changes in my antenna positioning unlike 15706 which would not reflect any change in my neighbors signal, which made it difficult to tune the antenna.
TX / RX (0 errors) so far.
The only thing I am checking is the throughput with internet test files.
GUI is much better in all respect - I am able to log in wireless and have not experienced any issues "All of us do not have the router located on a near by shelf"! Also it appears more responsive.
Wifi light comes on for a moment during reboot but remains off after connection is established.
BS "Take Five" it looks like you are on the Right Track with this build.