So now what? Will we migrate to OpenWRT?
Personally I am considering after 5+ years on DD-WRT to give OpenWRT a try and follow Kong (cheers mate). I have made a lot of tunings on my router all these years, as most of us, and probably this will be a painfully procedure. On the other side I love DD-WRT and its community, this is making the switch even harder...
I would be glad to hear from anyone of you guys your thoughts.
Joined: 21 Jan 2017 Posts: 1686 Location: Illinois Moderator
Posted: Sun Sep 08, 2019 16:05 Post subject:
t81 wrote:
So now what? Will we migrate to OpenWRT?
Personally I am considering after 5+ years on DD-WRT to give OpenWRT a try and follow Kong (cheers mate). I have made a lot of tunings on my router all these years, as most of us, and probably this will be a painfully procedure. On the other side I love DD-WRT and its community, this is making the switch even harder...
I would be glad to hear from anyone of you guys your thoughts.
Based on some of the latest tweaks BS has made, I see no performance advantage of "KongPro" vs dd-wrt. Plus Luci is a P.I.T.A. and really requires the user to know a lot more technically about settings and what they do, not that dd-wrt isn't daunting either sometimes...
My performance evaluation between the two shows that dd-wrt is running slightly better now with qos tweaks BS made vs the latest KongPro 9-6-19 build.
There are other reasons to want to run KongPro, but for my needs, I have no reason to make the switch permanent. Others may like the package modularity for their specific needs. I would say for 80%+ dd-wrt will suit them fine. For the ultra nerd/control freak OpenWrt offers more ease to add specific things. _________________ FORUM RULES
So now what? Will we migrate to OpenWRT?
Personally I am considering after 5+ years on DD-WRT to give OpenWRT a try and follow Kong (cheers mate). I have made a lot of tunings on my router all these years, as most of us, and probably this will be a painfully procedure. On the other side I love DD-WRT and its community, this is making the switch even harder...
I would be glad to hear from anyone of you guys your thoughts.
Based on some of the latest tweaks BS has made, I see no performance advantage of "KongPro" vs dd-wrt. Plus Luci is a P.I.T.A. and really requires the user to know a lot more technically about settings and what they do, not that dd-wrt isn't daunting either sometimes...
My performance evaluation between the two shows that dd-wrt is running slightly better now with qos tweaks BS made vs the latest KongPro 9-6-19 build.
There are other reasons to want to run KongPro, but for my needs, I have no reason to make the switch permanent. Others may like the package modularity for their specific needs. I would say for 80%+ dd-wrt will suit them fine. For the ultra nerd/control freak OpenWrt offers more ease to add specific things.
Thanks for the info.
Quote:
There are other reasons to want to run KongPro
Can you mention some plz? I always used Kong builds. My current firmware is v3.0-r40270M kongat (07/11/19)
Also do I need to reset settings in order to flush BS? I suppose I have to.
Joined: 21 Jan 2017 Posts: 1686 Location: Illinois Moderator
Posted: Sun Sep 08, 2019 22:40 Post subject:
t81 wrote:
Can you mention some plz? I always used Kong builds. My current firmware is v3.0-r40270M kongat (07/11/19)
Also do I need to reset settings in order to flush BS? I suppose I have to.
If you go from Kong to BS, it's advisable to reset to factory settings when making the switch over. There's been a lot of recent changes that are big and could cause issues if you don't.
As far as OpenWRT-If you have to ask, then honestly there's no reason to make the switch...Going to OpenWRT with LuCi as the GUI is not for the novice/casual user or for "I just need "better" q.o.s." BS has overcome some of the gripes of qos... My very casual testing between the two reveals that there's not a huge reason to move to openwrt for my casual use/needs.
You go to OpenWRT because you are doing many complex things with your router like several VLAN's, parental control through modules/packages, ad-blocking through modules/packages, hotspot through modules/packages, etc. This modularity is nice if you have knowledge of coding and are willing to take the tons of time to teach yourself command line interface commands. This is not for the casual user.
OpenWrt provides a totally customizable platform where others can then build packages onto. This is exactly what Kong has done for his own purposes in "KongPro". He likes it because it was "easier" to integrate the packages he wanted. Kong is not the average user nor base case. He's generous to share his personal build with all of us.
He cherry picked the modules/packages for specific tasks he's doing, some of which are mentioned above.
Many people may want to use the same modules/features he does. I am not sure if there is a concise list of all the packages he chose to incorporate, but I do know he has a folder with a laundry list of packages you can load. If you want to know more...you need to read around our forums and/or someone else can chime in.... _________________ FORUM RULES
If you go from Kong to BS, it's advisable to reset to factory settings when making the switch over. There's been a lot of recent changes that are big and could cause issues if you don't.....
When you say reset to factory settings, you mean flash netgear firmware, then flash BS build?
I'm considering switching to BS builds.
Why do you want a Kong OpenWrt?
For me it was just a low latency reason and stable releases.
BS builds are really bad on my 500+ Internet with B or even B- bufferbloat and you newer know if it works but Kong OpenWrt is always A+ and rock solid already.
The cake qos is bad everywhere for 400+ Internet and not really optimized but OpenWRT SQM with fc-codel is pretty good.
There is also OpenWRT Hnyman r7800 build and i will try later to compare.
The UI on OpenWRT is awful and complicated but if you will need just a standard router or AP you will find it there with some learning curve _________________ Netgear R7800
Connected PC to Ethernet port, changed ip to 192.168.1.2,
started pinging192.168.1.1, unplugged - plugged router and when started receiving 128ms ping time tried to flash with tftp2.exe on Win7 with no luck.
How to proceed?
Joined: 21 Jan 2017 Posts: 1686 Location: Illinois Moderator
Posted: Sun Sep 15, 2019 17:38 Post subject:
t81 wrote:
Alozaros wrote:
yep will do the job...!!
otherwise via telnet/ssh
nvram erase && reboot
Connected PC to Ethernet port, changed ip to 192.168.1.2,
started pinging192.168.1.1, unplugged - plugged router and when started receiving 128ms ping time tried to flash with tftp2.exe on Win7 with no luck.
How to proceed?
UPDATE: flashing through CLI did the job
For the future, you need to get the R7800 in TFTP mode first...this is not like the old broadcom days and peacock thread....
To get the router in TFTP mode:
Start with the router off.
1-plug the Ethernet code between laptop/desktop and Wan. If you don't plug it into the wan port and try using a lan port I found that the router doesn't want to enter into tftp mode.I believe you have about 5 minutes before this mode times out and then boots the router back to normal operation.
2-find something that can push in the reset button and hold down the reset button and power on the router. Keep holding down the reset button as the router boots up.
3-watch the power LED, it will flash orange six times, or so, and then it should start to flash White. Once it starts flashing white you can release the reset button and then you can push the IMG file via TFTP.
Thank you very much. This is very useful info.
BTW even though the new build (r41027 std, is this a BS build???) states that I can find DNSCRYPT under Services, it is not there. Do you have this option?
Joined: 21 Jan 2017 Posts: 1686 Location: Illinois Moderator
Posted: Mon Sep 16, 2019 1:13 Post subject:
t81 wrote:
Thank you very much. This is very useful info.
BTW even though the new build (r41027 std, is this a BS build???) states that I can find DNSCRYPT under Services, it is not there. Do you have this option?
Joined: 16 Nov 2015 Posts: 4232 Location: UK, London, just across the river..
Posted: Mon Sep 16, 2019 10:00 Post subject:
hmmm... on all builds DNSCrypt GUI is removed...
on last Kong builds, DNScrypt 1.95 module is still present, but have to be called via CLI script...
otherwise, you can add DNSCrypt via entware and use
v2 instead... _________________ Atheros
TP-Link WR740Nv1 -----DD-WRT 45993 BS AP,NAT
TP-Link WR740Nv4 -----DD-WRT 44251 BS WAP/Switch
TP-Link WR1043NDv2 ---DD-WRT 46316 BS AP,NAT,AP Isolation,Ad-Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---DD-WRT 46166 BS AP,NAT,AD/Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Qualcomm/IPQ8065
Netgear R7800 -----DD-WRT 46259 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Broadcom
Netgear R7000 -----DD-WRT 46259 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,VLAN's,DoT,VPN
-----------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 by mac913
