Remember: This is a Personal Test Build and is highly experimental. Flashing is at your own risk.
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. 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. 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. _________________ KONG Builds for R7000, AC68U
Brainslayer for everything else
I haven't reset it (yet!), but so far so good, no issues stand out at the moment. _________________ KONG Builds for R7000, AC68U
Brainslayer for everything else
Netgear R6300v2
Kong PTB 26500 .chk file dated 3/23/2015 --> Kong PTB 26970 .chk file dated 5/22/2015
**Dirty Flash -- NO RESET**
File: No real Point in linking official Kong PTB repo as next PTB will overwrite this file... (but HERE is link to my personal repo) MD5: 59502822b82f95b06f6ad641e0248eb0 (Kong also provides this on web repo in a .md5 file)
DDNS -- OK (custom for dnsomatic)
SSH Tunneling -- OK
RDP session via SSH Tunneling -- OK
OpenDNS Content Filtering -- OK
SAMBA -- OK, 2tb public NAS no security
MiniDLNA -- OK (upon initial review, I will give the db time to build before testing thoroughly)
NO REBOOTS! (since new WiFi driver)
so far no WiFi drops either (will keep this thread updated if anything changes)
**note testing performed based on 15 minutes of observations from the far end of an SSH tunnel, I will update if anything above is not accurate**
ddup command love notes:
root@DD-WRT:~# ddup --flash-latest
New release 26970 for Netgear R6300V2 available.
Do you want to update (y/n) [default=n]:
y
Connecting to www.desipro.de (82.165.89.193:80)
fw.bin 100% |**************************************************| 20428k 0:00:00 ETA
Connecting to www.desipro.de (82.165.89.193:80)
fw.bin.md5 100% |**************************************************| 63 0:00:00 ETA
Checksum: 59502822b82f95b06f6ad641e0248eb0 expected 59502822b82f95b06f6ad641e0248eb0
Checksum for dd-wrt.v24-K3_AC_ARM_STD.bin ok.
Are you sure you want to proceeed (y/n) [default=n]:
y
Closing SSH connections now. Flashing now...
root@DD-WRT:~#
....
login as: root
DD-WRT v24-sp2 kongac (c) 2015 NewMedia-NET GmbH
Release: 05/22/15 (SVN revision: 26970M)
Authenticating with public key ... _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
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: Netgear R7000
Firmware: v24-sp2 (05/22/15) kongac - build 26970M
Previous FW: 26653(BS)
Kernel: Linux 3.10.72 #370 SMP Fri May 22 16:01:46 CEST 2015 armv7l
Status: Successful
Reset: Yes (erase nvram before and after flash)
Errors: None so far.
Router configuration is uncomplicated, acting as internet gateway and AP for about 15 devices including 3 client-bridges (all running various levels of DD-WRT). _________________ Ubiquiti EdgeRouter Lite | Primary router
D-Link dgs-1100-08 smartswitch | Main VLAN-aware switch
Netgear R7000 #1 | Primary AP
Netgear R7000 #2 | AC-only client-bridge (office)
Asus RT-AC66U | AC-only client-bridge (HTPC)
Netgear WNDR3700v2 | client-bridge (basement)
Up and running with 26970M for about 24 hours, everything seems to be working properly.
I upgraded from 26500M via "ddup --flash-latest" after rebooting the router (no reset to defaults). _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
update via "ddup --flash-latest" after rebooting the router (no reset to defaults), everyhting is running great even my debian config was untouched.
Configured IPv6, 6in4 tunnel successfully and it working fine, was not working on the previous build.
See instructions here, if someone wants to try it.
I'm starting to encounter some issues with wireless-G and 26970M.
I have a couple of Linksys wireless-G cameras, one is a bit of a distance from the R7000. With releases prior to 26500M, I had to use a wireless repeater (a TP-Link WR700N) to ensure a stable connection to the more distant camera. With 26500N, I was able to remove the repeater from my WLAN as I was getting a solid connection to the camera.
But now with 26970M, the connection to this camera is again tenuous. Sometimes the connection drops, other times the connection is OK but the transmit rate is low. I may have to reinsert the repeater to fix this, but it seems strange this issue is back. I did not change any settings when I moved from 26500M to 26970M.
I'm starting to encounter some issues with wireless-G and 26970M.
I have a couple of Linksys wireless-G cameras, one is a bit of a distance from the R7000. With releases prior to 26500M, I had to use a wireless repeater (a TP-Link WR700N) to ensure a stable connection to the more distant camera. With 26500N, I was able to remove the repeater from my WLAN as I was getting a solid connection to the camera.
But now with 26970M, the connection to this camera is again tenuous. Sometimes the connection drops, other times the connection is OK but the transmit rate is low. I may have to reinsert the repeater to fix this, but it seems strange this issue is back. I did not change any settings when I moved from 26500M to 26970M.
Has anyone else noticed anything similar?
Do you use Europe as Regulatory Domain?
BrainSlayer did some bullshit to regulatory domain settings and I have not yet rolled it back:
I'm starting to encounter some issues with wireless-G and 26970M.
I have a couple of Linksys wireless-G cameras, one is a bit of a distance from the R7000. With releases prior to 26500M, I had to use a wireless repeater (a TP-Link WR700N) to ensure a stable connection to the more distant camera. With 26500N, I was able to remove the repeater from my WLAN as I was getting a solid connection to the camera.
But now with 26970M, the connection to this camera is again tenuous. Sometimes the connection drops, other times the connection is OK but the transmit rate is low. I may have to reinsert the repeater to fix this, but it seems strange this issue is back. I did not change any settings when I moved from 26500M to 26970M.
Has anyone else noticed anything similar?
Do you use Europe as Regulatory Domain?
BrainSlayer did some bullshit to regulatory domain settings and I have not yet rolled it back:
I'm starting to encounter some issues with wireless-G and 26970M.
I have a couple of Linksys wireless-G cameras, one is a bit of a distance from the R7000. With releases prior to 26500M, I had to use a wireless repeater (a TP-Link WR700N) to ensure a stable connection to the more distant camera. With 26500N, I was able to remove the repeater from my WLAN as I was getting a solid connection to the camera.
But now with 26970M, the connection to this camera is again tenuous. Sometimes the connection drops, other times the connection is OK but the transmit rate is low. I may have to reinsert the repeater to fix this, but it seems strange this issue is back. I did not change any settings when I moved from 26500M to 26970M.
Has anyone else noticed anything similar?
Do you use Europe as Regulatory Domain?
BrainSlayer did some bullshit to regulatory domain settings and I have not yet rolled it back:
I'm starting to encounter some issues with wireless-G and 26970M.
I have a couple of Linksys wireless-G cameras, one is a bit of a distance from the R7000. With releases prior to 26500M, I had to use a wireless repeater (a TP-Link WR700N) to ensure a stable connection to the more distant camera. With 26500N, I was able to remove the repeater from my WLAN as I was getting a solid connection to the camera.
But now with 26970M, the connection to this camera is again tenuous. Sometimes the connection drops, other times the connection is OK but the transmit rate is low. I may have to reinsert the repeater to fix this, but it seems strange this issue is back. I did not change any settings when I moved from 26500M to 26970M.
Has anyone else noticed anything similar?
Do you use Europe as Regulatory Domain?
BrainSlayer did some bullshit to regulatory domain settings and I have not yet rolled it back:
With the suggested nonsense regulatory setting the distance will be really bad in 2.4G, EU/66 only outputs 14.5db compared to 17.5db previously.
I have Regulatory Domain set to United States, Regulatory Mode Off, and TCP Mitigation Factor 3. (I honestly do not remember why I chose 3 as it was many months ago.) Wireless Network Mode is set to G-only, and the wireless channel is Auto (currently channel 1). I have one virtual interface for the AP. The rest of the settings for this AP are defaults. _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Cheers Kong!