Only been testing a few hours on my R7000, but it seems snappier, and I've yet to experienced any timeouts (when trying to access a site/address on the internet) yet. The newest BS builds also give me these timeouts.
Best firmware since 26500m.
Hey all sorry I'm new to this. I'm currently using the regular dd-wrt and not the kong mod. Would it be possible to update to the newest kong mod without going back to stock netgear firmware?
Yes,
download Kongs firmware and update via the gui as usual.
haru3173 wrote:
Hey all sorry I'm new to this. I'm currently using the regular dd-wrt and not the kong mod. Would it be possible to update to the newest kong mod without going back to stock netgear firmware?
_________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
Only been testing a few hours on my R7000, but it seems snappier, and I've yet to experienced any timeouts (when trying to access a site/address on the internet) yet. The newest BS builds also give me these timeouts.
Best firmware since 26500m.
Uptime 28h, and I just experienced my first timeout. Could be my cable modem, who knows. Still a pretty solid firmware.
This thread has gotten pretty messy. Please see and follow the instructions in my edit to the first post. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Little late to the party this time. I was watching Kong's WRT1900AC repository instead of the R7000 one *smile*. Just saw the new release last night and flashed it. And this thread just now.
Anyways, doing well on my R7000. Wireless and IPv6 are both doing really well.
Did change the MAC address on br0, since it was the same as that for vlan1, which led to the problem mentioned above. All fixed now *smile*.
Time will tell, but this release is looking good here!
Posted: Tue Jul 21, 2015 22:23 Post subject: Port Forwarding rules disappearing...
I have the R7000, using Build 27525M. All seems ok, except, I can't add any more than 13 rules into the Port Forwarding page. If I input more and then press either 'save' or 'apply settings', only the first 13 port forward rules remain - the rest just disappear. I know it's not an NVRAM issue, as i still have over 41kbs free.
Also, when I installed the new firmware, I did the proper reset to factory settings both before and after the upgrade.
I hope this gets resolved in the next firmware update...
Netgear R6300v2
Kong PTB 26970 file dated 5/22/2015 --> Kong PTB 27525 file dated 7/16/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: e1d2b8e66fd462d5618e40b09f031c02 (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 2015-02)
so far no WiFi drops either (will keep this thread updated if anything changes)
**note testing performed based on 30 minutes of observations from the far end of an SSH tunnel, I will update if anything above is not accurate**
ddup command love notes:
login as: root
DD-WRT v24-sp2 kongac (c) 2015 NewMedia-NET GmbH
Release: 05/22/15 (SVN revision: 26970M)
Authenticating with public key "xxxxxxxxxx"
Passphrase for key "xxxxxxxxxx":
==========================================================
root@DD-WRT:~# ddup --flash-latest
New release 27525 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% |*******************************| 20784k 0:00:00 ETA
Connecting to www.desipro.de (82.165.89.193:80)
fw.bin.md5 100% |*******************************| 63 0:00:00 ETA
Checksum: e1d2b8e66fd462d5618e40b09f031c02 expected e1d2b8e66fd462d5618e40b09f031c02
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 v3.0-r27525M kongac (c) 2015 NewMedia-NET GmbH
Release: 07/15/15
Authenticating with public key "xxxxxxxxxx"
Passphrase for key "xxxxxxxxxx":
==========================================================
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
I had an internet drop after about a day on this firmware on the R7000 on my wired desktop, and am now back using the Asus RT-AC68P with RMerlin firmware. Actually, it was more than a day, but I had to reboot a couple of times for some configuration changes I made. It was about a day of continuous uptime, though.
The internet drop on the R7000, and my needing a reboot to get the internet back may have been an anomaly of some sort (I hope), and I'll try it again at some point to see if that was the case. But the RT-AC68P is doing really well, so I'm not motivated to switch off of it at the moment.
Edit: Back on 27525 to see if internet drop was an anomaly or a firmware thing. Enquiring minds need to know *smile*.
Last edited by MrDoh on Mon Jul 27, 2015 5:47; edited 1 time in total
Dirty updated from 26000M (no, that isn't a typo) to 27525M on my Buffalo WZR-1750DHP. Will see if there are any issues, but everything seems fine directly after the update.
Now if only I could find a way to tether a Samsung Galaxy 3 to thing thing, I'd be golden...
I updated my main AC68R from 27085M to Kong build 7-16-15 #27525. Usually after a day or two up time, the 5gz band will become not usable: SSID is shown but can not be connected by any device previously connected to the 5gz band. The stranger thing is that this makes the same device can not connect 2.4ghz too. The only solution is to reboot. So I downgraded to 27085M.
Has anybody else seen the same issue?
For 27085M, my Nexus phone sometimes shows the network is disconnected and then re-connected by itself. This is better than rebooting router.
Dont know what happened to recent releases. But they not as stable and robust as before.
Up and running with r27525M for almost 22 days. Nice, solid release. _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
