Posted: Tue Nov 21, 2017 19:25 Post subject: Remove Netgear R6250 from compability list
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Tue Nov 21, 2017 19:51 Post subject: Re: Remove Netgear R6250 from compability list
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
There are reports that Kong build 33525 is working on this unit. I just did a very quick search...so likely other Kong builds are supporting this unit as well.
redhawk _________________ The only stupid question....is the unasked one.
Posted: Wed Nov 22, 2017 9:29 Post subject: Re: Remove Netgear R6250 from compability list
redhawk0 wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
There are reports that Kong build 33525 is working on this unit. I just did a very quick search...so likely other Kong builds are supporting this unit as well.
redhawk
Indeed Kong's are working correctly. On the other hand BS builds brick the router since version 30432. This is also happening with several TrendNet devices. I wouldn't say remove it from the list, but it would be very useful to write down there what's the max version you can use. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Wed Nov 22, 2017 11:22 Post subject: Re: Remove Netgear R6250 from compability list
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
Hi Eventine,
I have a R6250 running Kong's 33770 and previous builds quite well so far on this router...
What are the "out of memory" symptoms?
Does it happen after one year only? Exactly?
Does a reboot fix it?
Posted: Wed Nov 22, 2017 12:23 Post subject: Re: Remove Netgear R6250 from compability list
limerick_fr wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
Hi Eventine,
I have a R6250 running Kong's 33770 and previous builds quite well so far on this router...
What are the "out of memory" symptoms?
Does it happen after one year only? Exactly?
Does a reboot fix it?
I think his writing was kind of rushed. What I think he meant to say is that for more than a year, BS builds are not working on this router because as the firmware is too big then it bricks the router, as I explained on my previous comment. This started in end of August 2016. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Wed Nov 22, 2017 18:19 Post subject: Reporting issues to Brainslayer and Kong?
Xeon2k8 wrote:
What I think he meant to say is that for more than a year, BS builds are not working on this router because as the firmware is too big then it bricks the router, as I explained on my previous comment. This started in end of August 2016.
@redhawk0 et al,
What is the best method to report these issues to BS and Kong? There are many BCM routers whose builds are too big, plus other significant fixes like what quarkysg has done w/ PBR+SFE and the DIR-868/860, WDS is now broken for recent k26 and k3x builds, etc. As noted in a previous thread, the 'K3X too big' issue was going on for quite a while, and BS said he was unaware until you got in touch with him...despite all the build threads (and others) reporting it. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Posted: Fri Nov 24, 2017 20:22 Post subject: Re: Remove Netgear R6250 from compability list
redhawk0 wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
There are reports that Kong build 33525 is working on this unit. I just did a very quick search...so likely other Kong builds are supporting this unit as well.
redhawk
I have DD-WRT v3.0-r30020M kongac and have the problem. So I read that too but it's not true. And what about the "new" WPA2 issues?
Posted: Fri Nov 24, 2017 20:29 Post subject: Re: Remove Netgear R6250 from compability list
limerick_fr wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
Hi Eventine,
I have a R6250 running Kong's 33770 and previous builds quite well so far on this router...
What are the "out of memory" symptoms?
Does it happen after one year only? Exactly?
Does a reboot fix it?
symptons are that:
1) cannot access router, both lan and wifi
2) wifi (i think DHCP) is not working/cannot connect
3) Lan starts lagging when the problem starts, and then after 1-2h doesn't work
4) The logs, as reported by all the others, is: issue, killing this process, bla bla bla, out of memory and then nothing else (i can provide them)
Reboot will make the router start working again, the problem is, with 30020 router WILL LAST only 2-3 days, with newer, only one day (I have to reboot the router every night)- Problems start ALWAYS at around 00:30 AM.
Before that time RAM is TOTALLY EMPTY and CPU load less than 1%. So is not a problem of the firmware being "too big".
Consider I'm using dd-wrt for home
Posted: Fri Nov 24, 2017 20:30 Post subject: Re: Reporting issues to Brainslayer and Kong?
jwh7 wrote:
Xeon2k8 wrote:
What I think he meant to say is that for more than a year, BS builds are not working on this router because as the firmware is too big then it bricks the router, as I explained on my previous comment. This started in end of August 2016.
@redhawk0 et al,
What is the best method to report these issues to BS and Kong? There are many BCM routers whose builds are too big, plus other significant fixes like what quarkysg has done w/ PBR+SFE and the DIR-868/860, WDS is now broken for recent k26 and k3x builds, etc. As noted in a previous thread, the 'K3X too big' issue was going on for quite a while, and BS said he was unaware until you got in touch with him...despite all the build threads (and others) reporting it.
we reported everything on this forum on proper post, and directly to him. No answer
Posted: Fri Nov 24, 2017 20:31 Post subject: Re: Remove Netgear R6250 from compability list
Xeon2k8 wrote:
limerick_fr wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
Hi Eventine,
I have a R6250 running Kong's 33770 and previous builds quite well so far on this router...
What are the "out of memory" symptoms?
Does it happen after one year only? Exactly?
Does a reboot fix it?
I think his writing was kind of rushed. What I think he meant to say is that for more than a year, BS builds are not working on this router because as the firmware is too big then it bricks the router, as I explained on my previous comment. This started in end of August 2016.
Sorry for not answering I had tough days, and I thought i'd have recived notifications by mail. Can you please tell me what "too big" means? Ram? Space?
Posted: Fri Nov 24, 2017 23:17 Post subject: Re: Remove Netgear R6250 from compability list
Eventine wrote:
Xeon2k8 wrote:
limerick_fr wrote:
Eventine wrote:
Can you please remove the Netgear R6250 from the compability list? (www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear)
New dd-wrt firmwares are not working for more than 1 year ("out of memory" issue, everyone is talking about it, no one has ever found the issue).
So people that are looking for a router don't make mistake.
Asking to fix problem seams to be not viable, so at least please remove it from the list.
Eventine
Hi Eventine,
I have a R6250 running Kong's 33770 and previous builds quite well so far on this router...
What are the "out of memory" symptoms?
Does it happen after one year only? Exactly?
Does a reboot fix it?
I think his writing was kind of rushed. What I think he meant to say is that for more than a year, BS builds are not working on this router because as the firmware is too big then it bricks the router, as I explained on my previous comment. This started in end of August 2016.
Sorry for not answering I had tough days, and I thought i'd have recived notifications by mail. Can you please tell me what "too big" means? Ram? Space?
Flash storage _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Sat Nov 25, 2017 15:24 Post subject: Re: Remove Netgear R6250 from compability list
Xeon2k8 wrote:
Flash storage
I'm not a pro of dd-wrt, but "killing process" and "out of memory issue" are about ram. What flash has to do in all of that? And if it's only a flash storage problem, can I expand somehow (creating an external storage driver, witth usb key)?
you cannot add flash with a usb stick. The bootstrap (CFE) would need to include USB drivers to be able to even talk to the USB stick before booting the main firmware and there just isn't enough room for those.
When builds exceed flash size it is USELESS to complain about it in the forums. If you want it fixed then open a trouble ticket for the device. But before doing that verify that it is out of space.
For example on my Netgear AC1450 if I telnet into it and run the command dmesg this is what I get:
So, the thing has a 128MB flash chip in it. Then further down we get:
Creating 1 MTD partitions on "brcmnand":
0x000002000000-0x000008000000 : "ddwrt"
hex 0x000008000000 calculates out to 96MB. Where is the extra 32MB of flash? Only Netgear knows!
Further up in the dmesg we get
found TRX Header on nflash!
nflash: squash filesystem with lzma found at block 41
Creating 5 MTD partitions on "nflash":
0x000000000000-0x000000080000 : "boot"
0x000000080000-0x000000200000 : "nvram"
0x000000380000-0x000002000000 : "linux"
0x000000520000-0x000002000000 : "rootfs"
0x000000200000-0x000000220000 : "board_data"
The Linux partition is where the dd-wrt image goes. If you take hex 0x000002000000 (33554432) and subtract hex 0x000000380000 (3670016) you get 28.5MB flash. Since the file http://www.desipro.de/ddwrt/K3-AC-Arm/dd-wrt.v24-K3_AC_ARM_STD.bin is smaller than that - I know it will fit.
You need to run these calculations from the dmesg output to eliminate any bugs or other nonsense from the webinterface that would prevent a flash. If you find the new firmware is larger than the Linux partition - then THAT is a bug, you need to report it via svn and you need to post what you find in the wiki for the router model, if there is one.
For out of memory bugs you need to do the following. First reboot the router then telnet into it and run the command "top" Here it the output from my AC1450
Mem: 37140K used, 217396K free, 0K shrd, 4088K buff, 11332K cached
CPU: 0.3% usr 0.8% sys 0.0% nic 98.4% idle 0.0% io 0.0% irq 0.2% sirq
Load average: 0.02 0.05 0.01 2/68 29165
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
1075 1 root S 3992 1.5 0 0.3 httpd -p 80
1030 1 root S 1372 0.5 0 0.1 wland
29105 1256 root R 1176 0.4 1 0.1 top
883 1 root S 1168 0.4 0 0.1 telnetd
918 1 root S 1672 0.6 0 0.0 dnsmasq -u root -g root --conf-file=/tmp/dnsmasq.conf --cache-size=1
1026 1 root S 1440 0.5 0 0.0 process_monitor
1077 1 root S 1184 0.4 0 0.0 resetbutton
1256 1255 root S 1164 0.4 1 0.0 -sh
1255 883 root S 1160 0.4 1 0.0 /bin/login
1 0 root S 976 0.3 1 0.0 /sbin/init
617 1 root S 800 0.3 0 0.0 /sbin/mstpd
613 1 root S 756 0.3 0 0.0 /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
1055 1 root S 728 0.2 0 0.0 cron
Record this somewhere (copy and paste to notepad) and then wait until the router is having problems with being out of memory (and you would need to reboot it) and then telnet in and run top again
Notice the VSZ (Virtual memory SiZe) of the individual daemon programs. In a router that is out of memory you may have one of these with a very large VSZ after a long period, this would be because of a memory leak in that program. That is a bug and needs to be reported.
If the daemons look OK then run ps and see if there's a program there which has chewed up all the ram but is just not active.
you cannot add flash with a usb stick. The bootstrap (CFE) would need to include USB drivers to be able to even talk to the USB stick before booting the main firmware and there just isn't enough room for those.
When builds exceed flash size it is USELESS to complain about it in the forums. If you want it fixed then open a trouble ticket for the device. But before doing that verify that it is out of space.
For example on my Netgear AC1450 if I telnet into it and run the command dmesg this is what I get:
So, the thing has a 128MB flash chip in it. Then further down we get:
Creating 1 MTD partitions on "brcmnand":
0x000002000000-0x000008000000 : "ddwrt"
hex 0x000008000000 calculates out to 96MB. Where is the extra 32MB of flash? Only Netgear knows!
Further up in the dmesg we get
found TRX Header on nflash!
nflash: squash filesystem with lzma found at block 41
Creating 5 MTD partitions on "nflash":
0x000000000000-0x000000080000 : "boot"
0x000000080000-0x000000200000 : "nvram"
0x000000380000-0x000002000000 : "linux"
0x000000520000-0x000002000000 : "rootfs"
0x000000200000-0x000000220000 : "board_data"
The Linux partition is where the dd-wrt image goes. If you take hex 0x000002000000 (33554432) and subtract hex 0x000000380000 (3670016) you get 28.5MB flash. Since the file http://www.desipro.de/ddwrt/K3-AC-Arm/dd-wrt.v24-K3_AC_ARM_STD.bin is smaller than that - I know it will fit.
You need to run these calculations from the dmesg output to eliminate any bugs or other nonsense from the webinterface that would prevent a flash. If you find the new firmware is larger than the Linux partition - then THAT is a bug, you need to report it via svn and you need to post what you find in the wiki for the router model, if there is one.
Thanks for the accurate procedure, but it's not "out of space" is "out of memory" (--> RAM)