Support for R6400v2 (with different boardid's) and R6700v3 added.
Your reports for Broadcom units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors:
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build (e.g. 29440_NEWD-2_K2.6_mega-nv64k.bin). Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build. _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Router: Netgear R7000
Firmware: DD-WRT v3.0-r36840M kongac (09/03/2018)
Kernel Version : Linux 4.4.153 #598 SMP Mon Sep 3 22:38:12 CEST 2018 armv7l
Status: Working
Reset: No
Previous: 36820M
Errors: No
Temperatures : CPU 54.7 °C / WL0 48.0 °C / WL1 50.0 °C
Working very well :
Router mode : DHCP
SFE Enable STP Enable
DNSMasq
Encrypt DNS
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Local DNS
No DNS Rebind
Query DNS in Strict Order
Usb
Nas, Samba, JFFS2, MiniDLNA
wl0, wl1
Vpn (OpenVPN Client)
DDNS -- OK (custom for dnsomatic)
SSH Tunneling -- OK (update to 2048 bit key!)
**note: Flashed from the far side of an SSH tunnel. Initial testing performed based on 30 minutes observations, I will update if anything above is not accurate**
DDNS -- OK (custom for dnsomatic)
RDP session via SSH Tunneling -- OK
OpenDNS Content Filtering -- OK
SAMBA -- OK, 2tb public NAS no security
MiniDLNA -- NOT TESTED THIS TIME
ddup command love notes:
I forget what version I was on 7/30/18 if i recall...
ddup --flash-latest
*** REBOOT HERE ***
login as: root
DD-WRT v3.0-r36840M kongac (c) 2018 NewMedia-NET GmbH
Release: 09/03/18
Authenticating with public key "rsa-key-20180327"
Passphrase for key "rsa-key-20180327":
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Router Name6200v2 What it is
Router Model Netgear R6250 What it ain't
Firmware Version DD-WRT v3.0-r36840M kongac 09/03/18
Kernel Version Linux 4.4.153 #598 SMP Mon Sep 3
Previous 36820
no reset
no errors
Working
I can now confirm the only method of upgrading/downgrading this unsupported unit:
You have to soft brick it. Try to upgrade/downgrade via WebGUI or ddup will do it.
Then tftp with 24170-dd-wrt-K3_R6200V2_7-Aug-2014.chk. Timing is no issue.
Then install dd-wrt.v24-K3_AC_ARM_STD.bin via WebGUI.
So now it is on 36840
GW AP
VAP on both radios
1TB HDD serving minidlna
usb entware YAMon3 nano others
ovpn client
proftp
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Wed Sep 05, 2018 11:41 Post subject:
Router Model: Linksys EA6900 (XVortex CFE)
Firmware Version: DD-WRT v3.0-r36840M kongac (09/03/2018)
Kernel Version: Linux 4.4.153 #598 SMP Mon Sep 3 22:38:12 CEST 2018 armv7l
Upgraded: from 36820M via telnet (upgrade via WebGui or DDUP not possible, due to XVortex CFE)
Reset: No, not this time
Configuration: Gateway, AP, DHCP server, 2,4GHz wireless running, 5GHz running, some static leases.
Unbridged VAP on 5 GHz. working!
NVRAM size just below 32K (NVRAM size should not be a problem with the Xvortex CFE)
Status: Up and stable for 2 h, excellent wireless speed and range,
Errors: none so far
Router: WiFi R7000 (2.4Ghz + 2 VAPs & 5Ghz +VAP)
Firmware: DD-WRT v3.0-r36840M kongac (09/03/2018)
Kernel Version : Linux 4.4.153 #598 SMP Mon Sep 3 22:38:12 CEST 2018 armv7l
Status: Gone Back to Spare R7000 with Working 35550M
Reset: No
Previous: 36410M
Errors: Can Not Connect to VAP on 5Ghz (WL1.1)
With the WiFi Router with build 36840M I did an "erase nvramm" and "reboot" and started creating my 2 VAPs on the 2.4Ghz Radio and one VAP on the 5Ghz Radio. The one problem I'm seeing is that the 5Ghz VAP has the same MAC Address as the 2.4Ghz #2 VAP....
Code:
Firmware: DD-WRT v3.0-r36840M kongac (09/03/18)
Time: 01:05:55 up 5 min, load average: 0.00, 0.04, 0.00
WAN IP: 0.0.0.0
I did try changing the MAC Address Manually on one of the VAP through the GUI and it would go back to the same MAC Address, so I am unable to change the MAC Address. _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Wed Sep 05, 2018 16:02 Post subject:
I have a modified Linkys EA6900 (MAC addresses are in the CFE for this router so can be changed in CFE), I started with setting MAC address for eth2 further away from eth1 (I used +2) to create room for MAC addresses of more than one VAP.
You could try a similar thing, so start with increasing the MAC address of eth2
You probably have to erase nvram then set MAC address of eth2 + 2, as the MAC addresses of the VAP are then derived from eth1 and eth2.
Previous: v3.0-r36820M kongac (ddup upgrade)
Reset: no
Configuration: AP on 2.4 GHz and 5 Ghz + VAP on 2.4 GHz.
Status: Up and stable for 12 h
Errors:
Code:
Sep 5 18:34:31 DD-WRT_Router daemon.err httpd[1186]: Request Error Code 408: No request appeared within a reasonable time period.
Sep 5 18:35:34 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:35:34 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:36:26 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:36:33 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:36:35 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:36:36 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:39:25 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:39:25 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:39:27 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:40:36 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
Sep 5 18:40:37 DD-WRT_Router daemon.warn dnsmasq-dhcp[1032]: no address range available for DHCP request via br0
I have a modified Linkys EA6900 (MAC addresses are in the CFE for this router so can be changed in CFE), I started with setting MAC address for eth2 further away from eth1 (I used +2) to create room for MAC addresses of more than one VAP.
You could try a similar thing, so start with increasing the MAC address of eth2
You probably have to erase nvram then set MAC address of eth2 + 2, as the MAC addresses of the VAP are then derived from eth1 and eth2.
Never tried it just a thought
I don't think the MAC duplication is really a problem since they are different physical networks but just to make things simpler/clearer for me I did similar for my TM1900/AC68Us. I changed the last two octets of my et0macaddr to :10 on my first router, :20 on the second and so forth to help tell the MAC addresses apart for client-side troubleshooting. Then I set 0.macaddr to et0macaddr+4 and 1.macaddr to et0macaddr+8 to leave a bit more breathing room for the two VAPs I have on both 2.4 & 5 GHz.
During my testing I noticed I could change et0_macaddr in NVRAM and commit the changes, and it would be obeyed. I assume the same would be true with 0.macaddr & 1.macaddr, though I didn't try it. So if the OP doesn't want to modify CFE, he can first try modifying the addresses stored in NVRAM and see if they'll stick and be obeyed on his router model. If he erases nvram they'll need to be changed again, of course.
New rt-ac68u B2 1.4ghz cpu. Sent info to BS two weeks ago to get it added.
Router Model Asus RT-AC68U
Firmware Version DD-WRT v3.0-r36840M kongac (09/03/1
Kernel Version Linux 4.4.153 #598 SMP Mon Sep 3 22:38:12 CEST 2018 armv7l
Everything working fine so far, up 13+ hours. _________________ I am far from a guru, I'm barely a novice.