Kong 20780 released

63 posts / 0 new
Last post
Li Tai Fang
Li Tai Fang's picture
mrg666 said:

mrg666 said:

gambitmac said: Has anyone had any problems with Portforwarding working on this build. It's not working for me!

port forwarding is working for me. Kong and buddee, thanks for disabling the usb initialization. This build is running great on the WNR3500L which was upgraded from 18730 build.

Speaking of WNR3500L and 18730......

I've tried many different kong builds and regular dd-wrt builds for WNR3500L as a repeater bridge, up to kong 20500, but 18730 gives by far the best wireless signal measured by SNR. 

Do you guys find the same thing? If so, does the newest build have signal strengths comparable to 18730?

Thanks. 

mrg666
mrg666's picture
 

 

Li Tai Fang said:

mrg666 said:

gambitmac said: Has anyone had any problems with Portforwarding working on this build. It's not working for me!

port forwarding is working for me. Kong and buddee, thanks for disabling the usb initialization. This build is running great on the WNR3500L which was upgraded from 18730 build.

Speaking of WNR3500L and 18730...... I've tried many different kong builds and regular dd-wrt builds for WNR3500L as a repeater bridge, up to kong 20500, but 18730 gives by far the best wireless signal measured by SNR.  Do you guys find the same thing? If so, does the newest build have signal strengths comparable to 18730? Thanks. 

I use the WNR3500L as a router only with the Kong builds. Since the wifi AP part is turned off, I can't comment on the wireless performance. Two E2000's are used as WiFi APs and they are connected via 1Gb ethernet to the WNR3500L. E2000s run Tomato. The WiFi performance is excellent with the RT-N builds of Toastman. Both E2000s are upgraded with external antennas, just for the record.

 

Almaz
Almaz's picture
I'm a long time DD-WRT user

I'm a long time DD-WRT user and lately I've been using E3000 with 14929. Wifi worked OK, so I wanted to upgrade to the latest version to see the difference. Tried a few versions of Kong firmware, including the latest 2 and so far WiFi signal is much lower than before. Let's just say when my Galaxy S3 worked fine about 20-25ft away from the router using 14929 then with Kong firmware, signal was very weak, and kept disconnecting. 2.4ghz is used as a client and 5ghz is used for internal wireless network. So I tried for the first time latest Shibby Tomato and everything worked great out of the box. I'd love to see Kong DD-WRT to try the same drivers from Shibby Tomato. Both firmwares are great.

Kong
Kong's picture
Hi guys,

Hi guys,

concerning the signal strength. A lot of people complain about low signal strength compared to older drivers. I ran several tests every time we included a new driver. In fact there was a driver once which suffered from signal degration over time. But the drivers in the latest builds don't have that problem.

What has changed in drivers included in builds > 15000 ist that they support energie management. I just did a few tests yesterday to compare the WNR3500L to a R6300. In that test I checked signals indoor and outdoor and I still had a good signal with a nokia phone that was located outside the house in a distance of 40m.

The question is if there are settings that result in low signals? Can you provide the output of:

nvram show | grep wl0

and

nvram show | grep tx

Li Tai Fang
Li Tai Fang's picture
I'm running 18730 on WMR3500L

I'm running 18730 on WMR3500L right now. The 18730 build registers the best wireless signal out of all other versions that I've tried, e.g. kong 20500, kong 19545, kong 17865, and the "official" 14896.
It's set up as a Repeater Bridge:

root@WNR3500Repeater4:~# nvram show | grep wl0 | awk -F '=' '$2!=""'
size: 22163 bytes (10605 left)
wl0.1_radius_port=1812
wl0_net_mode=mixed
wl0_frameburst=off
wl0.3_key=1
wl0_leddc=0x640000
wl0_ipaddr=0.0.0.0
wl0.2_radius_port=1812
wl0_shortslot=auto
wl0_wep_buf=:::::
wl0_akm=psk2
wl0_macmode1=disabled
wl0.2_netmask=0.0.0.0
wl0_infra=1
wl0_wds6_enable=0
wl0_bcn_rotate=0
wl0.3_radius_port=1812
wl0.1_key=1
wl0.1_hwaddr=C2:3F:0E:9F:5B:E7
wl0_bandlist=b
wl0_br1_netmask=255.255.255.0
wl0_wme_sta_be=15 1023 3 0 0 off
wl0.3_auth_mode=disabled
wl0_ifname=eth1
wl0_wme_sta_bk=15 1023 7 0 0 off
wl0_mrate=0
wl0_mode=apstawet
wl0_ap_isolate=0
wl0_wme_no_ack=off
wl0_gmode=1
wl0.2_wpa_gtk_rekey=3600
wl0_nband=2
wl0_nreqd=0
wl0_security_mode=psk2
wl0.1_crypto=aes
wl0.3_bridged=1
wl0_wme_txp_be=7 3 4 2 0
wl0_wds1_enable=0
wifi_display=wl0
wl0_dtim=1
wl0_ssid=TARDIS_made_in_Gallifrey
wl0_dfs_preism=60
wl0_wds7_enable=0
wl0_wme_txp_bk=7 3 4 2 0
wl0_web_filter=0
wl0id=0x4329
wl0_vlan_prio_mode=off
wl0_txant=3
wl0.2_hwaddr=C2:3F:0E:9F:5B:E4
wl0_bridged=1
wl0_vifs=wl0.1
wl0_br1_nat=0
wl0_br1_enable=0
wl0.1_ipaddr=0.0.0.0
wl0_hw_rxchain=3
wl0.3_netmask=0.0.0.0
wl0_wme_ap_vi=7 15 1 6016 3008 off
wl0.3_akm=disabled
wl0_bss_maxassoc=128
wl0_plcphdr=auto
wl0_rate=0
wl0_closed=0
wl0_macmode=disabled
wl0_wme_ap_vo=3 7 1 3264 1504 off
wl0_radioids=BCM2056
wl0_phytype=n
wl0_lazywds=0
wl0_afterburner=off
wl0_netmask=0.0.0.0
wl0_antdiv=3
wl0.1_auth_mode=none
wl0.1_akm=psk2
wl0_wpa_psk=mywirelesspassword
wl0.2_crypto=off
wl0.1_ifname=wl0.1
wl0_wds2_enable=0
wl0.2_auth=0
wl0_wds8_enable=0
wl0_mbss=1
wl0_unit=0
wl0X1_security_mode=psk2
wl0_authmode=open
wl0_txpwr=40
wl0.3_hwaddr=C2:3F:0E:9F:5B:E5
wl0_nmode=-1
wl0.1_multicast=0
wl0.1_wep_buf=:::::
wl0.2_ipaddr=0.0.0.0
wl0_reg_mode=off
wl0_wme=on
wl0_radius_port=1812
wl0_auth=0
wl0_rxchain=3
wl0_wme_sta_vi=7 15 2 6016 3008 off
wl0.3_wpa_gtk_rekey=3600
wl0_wme_sta_vo=3 7 2 3264 1504 off
wl0.3_crypto=off
wl0_wds3_enable=0
wl0.2_key=1
wl0.1_mode=ap
wl0_maxassoc=128
wl0_wds9_enable=0
wl0_max_unauth_users=0
wl0_phytypes=n
wl0_frag=2346
wl0_wep=disabled
wl0.1_closed=0
wl0.1_ap_isolate=0
wl0_distance=2000
wl0_nbw=20
wl0_btc_mode=0
wl0.1_radius_ipaddr=0.0.0.0
wl0_rateset=default
wl0.1_ssid=Fringe Division
wl0_wme_apsd=on
wl0.3_ipaddr=0.0.0.0
wl0_wme_txp_vi=7 3 4 2 0
wl0_wchannel=0
wl0.1_authmode=open
wl0_wme_txp_vo=7 3 4 2 0
wl0_radius_override=1
wl0.1_bss_maxassoc=128
wl0_nmode_protection=auto
wl0_br1_ipaddr=0.0.0.0
wl0.1_bridged=1
wl0_rts=2347
wl0_wds4_enable=0
wl0_radauth=0
wl0_hw_txchain=3
wl0.2_auth_mode=disabled
wl0_wpa_gtk_rekey=3600
wl0_sta_retry_time=5
wl0_key=1
wl0.2_closed=0
wl0.1_netmask=0.0.0.0
wl0_dfs_postism=60
landevs=vlan1 wl0
wl0_radio=1
wl0_wds0=*,auto,aes,psk2,TARDIS_made_in_Gallifrey,mywirelesspassword
wl0.1_wpa_psk=mywirelesspassword
wl0_nbw_cap=1
wl0.1_nat=1
wl0.1_gtk_rekey=3600
wl0_bcn=100
wl0_hwaddr=C0:3F:0E:9F:5B:E6
wl0_gmode_protection=auto
wl0.2_akm=disabled
wl0.1_wpa_gtk_rekey=3600
wl0_radmacpassword=0
wl0_abenable=1
wl0.3_auth=0
wl0_wme_ap_be=15 63 3 0 0 off
wl0_nmcsidx=-1
wl0_corerev=17
wl0_channel=1
wl0_wds5_enable=0
wl0_wme_ap_bk=15 1023 7 0 0 off
wl0_wds10_enable=0
wl0.1_auth=0
wl0.1_wep=disabled
wl0_auth_mode=none
wl0.3_closed=0
wl0_crypto=aes
wl0_txchain=3
wl0.2_bridged=1
----------------------------------------------------

root@WNR3500Repeater4:~# nvram show | grep tx
wl_txstreams=0
size: 22164 bytes (10604 left)
wl0_wme_txp_be=7 3 4 2 0
wl0_wme_txp_bk=7 3 4 2 0
wl0_txant=3
wl_wme_txp_vi=7 3 4 2 0
wl_wme_txp_vo=7 3 4 2 0
dr_lan_tx=0
wl0_txpwr=40
txchain=3
dr_wan_tx=0
wl0_wme_txp_vi=7 3 4 2 0
wl0_wme_txp_vo=7 3 4 2 0
wl0_hw_txchain=3
wl_wme_txp_be=7 3 4 2 0
wl_wme_txp_bk=7 3 4 2 0
wl0_txchain=3
----------------------------------------------------

If you're interested in the output for other builds, I can do that too, after I have some time to flash and re-flash.

Kong
Kong's picture
OK so far I'd say these

OK so far I'd say these settings are ok. Can you show me a screenshot of the Time Graph from inssider : http://www.metageek.net/products/inssider/

Once connected and then disconnected (just disconnect using windows wireless tool)
To compare both you should create one with your current build and one with the latest build.

Li Tai Fang
Li Tai Fang's picture
Kong said: OK so far I'd say

Kong said: OK so far I'd say these settings are ok. Can you show me a screenshot of the Time Graph from inssider : http://www.metageek.net/products/inssider/ Once connected and then disconnected (just disconnect using windows wireless tool) To compare both you should create one with your current build and one with the latest build.

Oh darn, I only have Linux boxes. 

ReDaLeRt
ReDaLeRt's picture
Hi,

Hi,

Can anyone get 40MHz channels working on RT-N16 with this release?

I'm setting up my wifi to channel 1 and "lower" configuration. After committing this setup the router establishes a 40MHz channel correctly but several seconds later it downgrades to 20MHz.

I upgraded from 18050M kingkong and done the monitoring with inSSIDer and a Ubi Airview2-ext

Thank you in advance.

ReDaLeRt
ReDaLeRt's picture
Oh, I forgot! On the Status -

Oh, I forgot! On the Status -> Wireless page it says:

Channel: -1 + 1

w*f?!

Best regards.

PS: N-only mode.

ReDaLeRt
ReDaLeRt's picture
(delete this post please)

(delete this post please)

gambitmac
gambitmac's picture
Has anyone been experiencing

Has anyone been experiencing excessive high loads with this build? I'm seeing load averages of 14-20 then DNS stops working and router looses internet connection and reboots.

gambitmac
gambitmac's picture
ReDaLeRt said: Oh, I forgot!

ReDaLeRt said: Oh, I forgot! On the Status -> Wireless page it says: Channel: -1 + 1 w*f?! Best regards. PS: N-only mode.

It's a Kong thing, I have the same problem due to heavy 2.4GHz AP clost to my router.

http://www.smallnetbuilder.com/wireless/wireless-features/31743-bye-bye-40-mhz-mode-in-24-ghz-part-1

Kong
Kong's picture
You get high loads in case

You get high loads in case FPU emulation is off. What build date are you using, should be 02/26/13?

tangsoft
tangsoft's picture
weird, in Linksys E3000, this

weird, in Linksys E3000, this version just stop forwarding anything, so it cannot get access to internet. i have to downgrade to 20575.

ES13Raven
ES13Raven's picture
Kong,

Kong,

I am running kingkong 19277 on an ASUS RT-N16. I want to upgrade to the 20780 update. Do you recommend the whole "30-30-30" hard reset before and after upgrades? Or is clearing the browser cache good enough?

Thanks!

Li Tai Fang
Li Tai Fang's picture
ES13Raven said: Kong, I am

ES13Raven said: Kong, I am running kingkong 19277 on an ASUS RT-N16. I want to upgrade to the 20780 update. Do you recommend the whole "30-30-30" hard reset before and after upgrades? Or is clearing the browser cache good enough? Thanks!

 

Clearing browser cache is simply to prevent some situations where the browser is not presenting you the router's webpage, but what's saved in your browser cache. 

30-30-30 resets are to prevent old configuration variables from an old build to mess with the new build. 

Totally different stuff. 

slobodan
slobodan's picture
As far as I have understood

As far as I have understood from Kong, 30/30/30 is not required when flashing Kong builds. If you have problems with the new build, you are still able to do a 30/30/30 later.

gambitmac
gambitmac's picture
Kong said: You get high loads

Kong said: You get high loads in case FPU emulation is off. What build date are you using, should be 02/26/13?

I'm using 2/26/13, was a problem with  not clearing out NVRAM before flashing. did a 30,30,30 and average loads are doing well.

slobodan
slobodan's picture
 

 

gambitmac said:

Kong said: You get high loads in case FPU emulation is off. What build date are you using, should be 02/26/13?

I'm using 2/26/13, was a problem with  not clearing out NVRAM before flashing. did a 30,30,30 and average loads are doing well.

In the past six months (or more) I flashed many Kong builds, but I have never done 30/30/30. Imho, the failure to reboot when Optware was running was due to K90nzbget, which entered a loop which in principle had to take about 200 seconds, but for some reason it choked trying to kill zombie processes. A simple solution is to comment out the loop between "stop)" and "killall -9 nzbget" (but do not comment out killall -9 nzbget).

 

Myname
Myname's picture
Any way/options to activate

Any way/options to activate WiFi 5 GHz?

Twist
Twist's picture
I got r20780 kong running at

I got r20780 kong running at a Linksys E3000 (was a 610v2 once) and the Kingkong Build at my E4200v1 which is configured as an AP.
I recommend a 30-30-30 reset and clearing of the browser cache after every flash as I had various problems when changing builds..
5GHz works, 2,4GHz works. Uptime right now is 13 days.
I put this into the Startup Script of the E4200v1:
***
echo 262144 > /proc/sys/net/core/rmem_max
echo 262144 > /proc/sys/net/core/wmem_max
echo "4096 16384 262144" > /proc/sys/net/ipv4/tcp_wmem
echo "4096 87380 262144" > /proc/sys/net/ipv4/tcp_rmem
echo 1000 > /proc/sys/net/core/netdev_max_backlog
***
It should be some kind of Performance optimization. Is that ok?

I want to use the E3000 as 3G Router...can anyone point me to a step by step howto for getting it to work with a E398/K5005 or E182x/E1823 ? (Yes I know my APN and the rest of the Provider Settings.)

Thanks!

slobodan
slobodan's picture
Twist said: I put this into

Twist said: I put this into the Startup Script of the E4200v1: *** echo 262144 > /proc/sys/net/core/rmem_max echo 262144 > /proc/sys/net/core/wmem_max echo "4096 16384 262144" > /proc/sys/net/ipv4/tcp_wmem echo "4096 87380 262144" > /proc/sys/net/ipv4/tcp_rmem echo 1000 > /proc/sys/net/core/netdev_max_backlog *** It should be some kind of Performance optimization. Is that ok?

It's not bad, but also set congestion control to Westwood. This is much faster than Vegas.

Twist
Twist's picture
slobodan said:  t's not bad,

slobodan said:  t's not bad, but also set congestion control to Westwood.  This is much faster than Vegas. 

did that too. 

Kong
Kong's picture
Twist said: I got r20780 kong

Twist said: I got r20780 kong running at a Linksys E3000 (was a 610v2 once) and the Kingkong Build at my E4200v1 which is configured as an AP. I recommend a 30-30-30 reset and clearing of the browser cache after every flash as I had various problems when changing builds.. 5GHz works, 2,4GHz works. Uptime right now is 13 days. I put this into the Startup Script of the E4200v1: *** echo 262144 > /proc/sys/net/core/rmem_max echo 262144 > /proc/sys/net/core/wmem_max echo "4096 16384 262144" > /proc/sys/net/ipv4/tcp_wmem echo "4096 87380 262144" > /proc/sys/net/ipv4/tcp_rmem echo 1000 > /proc/sys/net/core/netdev_max_backlog *** It should be some kind of Performance optimization. Is that ok? I want to use the E3000 as 3G Router...can anyone point me to a step by step howto for getting it to work with a E398/K5005 or E182x/E1823 ? (Yes I know my APN and the rest of the Provider Settings.) Thanks!

I tested 3G last weekend with my vpn build, using a E1750. All I had to do was enter the apn and pin. After a reboot connection was up.

Twist
Twist's picture
Do I need to enable Core USB

Do I need to enable Core USB Support? USB Storage Support? Do I need to set a PIN if I don't use it normally?

Thanks!

Myname
Myname's picture
Hi, on E3200 with this FW,

Hi, on E3200 with this FW, the maximum Rate I can reach is 144 Mbps. Tried several channels, but thiss is the max. Is there any options how to increase the rate? As per official E3200 specification, it should be much higher then 144 Mbs

TTomas
TTomas's picture
Hello

Hello
UPnP is not working on 3500l
(broken on last 2 builds)

messerchmidt
messerchmidt's picture
running an e3000 with a nv60k

running an e3000 with a nv60k build. Was having issues with optware causing the router to freeze. Did a 30-30-30 reset and removed the usb stick. still having issues dropping the wan connections.

slobodan
slobodan's picture
messerchmidt said: running an

messerchmidt said: running an e3000 with a nv60k build. Was having issues with optware causing the router to freeze. Did a 30-30-30 reset and removed the usb stick. still having issues dropping the wan connections.

Yes, I noticed something like that: after you press Apply you have to wait 10 minutes since Optware initialization is called by rc start. Even better, Save instead of applying and reboot the router, then wait 10 minutes.

Twist
Twist's picture
3G works with an other USB

3G works with an other USB Modem and the same settings, plug&play...but the K5005 does not work.
Its in the support list: http://www.dd-wrt.com/wiki/index.php/3G_/_3.5G#HUAWEI

oh well...I will use the other stick (Huawei E1823).

Solved: K5005 is supported with newer firmware:
t-mobile speedstick LTE v11_433_61_10_55
This does not change the Dashboard!

now my Dovado 4GR is useless ;-)

I am sorry to have bothered you.

Pages