Router: D-Link DIR-890L
Firmware: v3.0-r28139 std (11/13/15)
Kernel: Linux DIR890L 3.10.93 #4932 SMP Fri Nov 13 07:10:00 CET 2015 armv7l
Status: Working
Previous: 28112
Reset: Yes
Mode: client (wl2; other 2 radios in AP mode)
Error(s): see below
Reset to defaults after flashing from 28112, manually set up client mode on wl2.
EDIT:
After running in client mode for about 2 days, the router couldn't connect to the main router any more, even after reboot or power cycle. This build seems not as stable as 27858 (which could go at least a week without interruption). _________________
Netgear R7800 kongpro 19.07 20190919 || Netgear R7000 36070M kongac (Client Bridge=5GHz, AP=2.4GHz with bridged VAP)
Linksys WRT32X davidc502 OpenWrt || Linksys WRT1200ACv1 Gargoyle 1.11.x
Linksys WRT1900ACSv2 dd-wrt 39956
Last edited by Ah-Pin-Kor on Tue Nov 17, 2015 0:25; edited 1 time in total
I have not seen anyone post on the Buffalo routers since all the bricks last month. I have not tried updating my firmware since. I was just curious as to whether any owners of this router have recently updated and what your status is?
any feedback would be great. Especially since these routers were sold with DD-WRT pre-installed. _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.
Posted: Sat Nov 14, 2015 21:34 Post subject: Asus RT-AC68U & Linksys E2000
asus_rt-ac68u-firmware r28139 (previous r28112)
Kernel: 3.10.93 #4927 SMP Fri Nov 13 06:54:51 CET 2015 armv7l DD-WRT
2.4Ghz (NG-mixed) with 40Mhz channel width: Ok
5Ghz (Mixed) with 80Mhz channel width: Ok
SSH: Ok, with
Telnet: Disabled but tested to work
USB 2.0 storage ext3 mount to JFFS: Ok
USB 3.0 storage EXT3 mount to /mnt: Ok
Samba shared drive: Ok
Site Survey: Ok
Wi-viz 2.4Ghz & 5Ghz: Yes
Reset: No
Status: Ok
Uptime: 2:40 hours
Linksys E2000
dd-wrt.v24-28139_NEWD-2_K3.x_mega-e2000
Kernel 3.10.93 #10180 Fri Nov 13 10:32:51 CET 2015 mips DD-WRT
SSH: Ok
Status: Ok
Site & Wi-viz Survey: Ok
I'm using a Netgear R7000 and this build is mostly working for me, but IPv6 is not working consistently. Specifically I'm using DHCPv6 with PD and the router is unable to get an IPv6 address from my ISP after each router reboot. If I SSH in to the router and manually run dhcp6c then I'm able to get an IPv6 address and IPv6 works correctly, but for some reason that's not happening automatically. I reset the router after flashing this build.
Router: Linksys ea6400
Firmware: DD-WRT v3.0-r28139 std (11/13/15)
Kernel: Linux 3.10.93 #4927 SMP Fri Nov 13 06:54:51 CET 2015 armv7l
Status: Good
Reset: No
Previous Build: r28112
Errors:
- could not update via web so need to ssh mtd linux2 & linux. Get some fluff error messages that can be ignored
Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sun Nov 15, 2015 11:16 Post subject:
cookieboyeli wrote:
Router: Asus RT-AC66U
Firmware: DD-WRT v3.0-r28139 giga (11/13/15)
Kernel: Linux 3.10.93 #10164 Fri Nov 13 10:20:22 CET 2015 mips
Status: Working with errors.
Reset: WPS NVRAM clear plus reset to factory defaults before and after.
Errors: Yes
Same issue as above with 0.02K/256K displayed NVRAM used.
Code:
nvram show
Code:
/dev/nvram: Out of memory
size: 20 bytes (262124 left)
Serial CFE data attached for assistance in debugging.
check your nvram from cfe. there is something corrupted inside. check "bootflags" variable for instance
this is the only thing which could lead to the situation that rootfs and kernel is detected on spi flash instead of nandflash _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Router: Netgear WNDR4000
Firmware: DD-WRT v3.0-r28139 mega (11/13/15)
Kernel: Linux 2.6.24.111 #27404 Fri Nov 13 02:40:58 CET 2015 mips
Status: Working
Reset: No
Errors: None So Far, Previous Version 28112 Had DNS issues where DNS would not resolve after 1-2 days of running and sometime router would freeze & had to do a force shutdown. (using DNSMasq Service For DNS Caching With OpenDNS Resolvers)
Linksys E1200 v2
DD-WRT v3.0-r28139 mega (11/13/15)
Linux 3.10.93 #10180 Fri Nov 13 10:32:51 CET 2015 mips
[dd-wrt.v24-28139_NEWD-2_K3.x_mega-nv64k.bin]
previous - reset
28139 mini (11/13/15)
Linux 2.6.24.111 #27402 Fri Nov 13 02:39:44 CET 2015 mips
Repeater Bridge working very well...
Haven't been up too long but moving lots data without problem
seems solid aside from the nvram thangy
Posted: Wed Nov 18, 2015 21:04 Post subject: Re: WZR-1750DHPD - Bricked Details from Serial connection
Hi BrainSlayer,
I am not sure what I am looking at, but I have attached the NVRAM SHOW output. I can reload an older version. Also, when I NVRAM ERASE this is the same data loaded (not sure if it should be less data or not).
Serial CFE data attached for assistance in debugging.
check your nvram from cfe. there is something corrupted inside. check "bootflags" variable for instance
this is the only thing which could lead to the situation that rootfs and kernel is detected on spi flash instead of nandflash
So far running smotth, the only problem is the internet speed stuck around 37-38 Mbps (i have 50 Mbps internet), with wired i could get 46 Mbps, and my other router with stock firmware also get 46 Mbps
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun Nov 29, 2015 14:45 Post subject: Re: WZR-1750DHPD - Bricked Details from Serial connection
mazecreator wrote:
Hi BrainSlayer,
I am not sure what I am looking at, but I have attached the NVRAM SHOW output. I can reload an older version. Also, when I NVRAM ERASE this is the same data loaded (not sure if it should be less data or not).
Serial CFE data attached for assistance in debugging.
check your nvram from cfe. there is something corrupted inside. check "bootflags" variable for instance
this is the only thing which could lead to the situation that rootfs and kernel is detected on spi flash instead of nandflash
newer builds are already available. check these first. from the log it just looks like the filesystem wasnt found. like a incomplete flash procedure _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
