New Kong Build 19210

10 posts / 0 new
Last post
Teknowiz
Teknowiz's picture
New Kong Build 19210

New build available.

http://www.desipro.de/ddwrt/r19210/

Build r19210 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
New:
kingkong builds for E3200/E4200

Fixed:
fix openvpn trac ticket #2534
fix pptp firewall rule

Only issue I noticed with this build and last one is that CPU load seems unusually high with my RT-N16 CPU load averaging 25% with no load.

fastfwd
fastfwd's picture
Kong: Thank you for making

Kong: Thank you for making the KingKong version available for E4200.

Using only the services I used with the 18730-VPN-60K build (i.e., OpenVPN Server enabled, DLNA disabled, SIP disabled), CPU load on my E4200 is unchanged from build 18730-VPN-60K.

OpenVPN Server is still broken; I'll file a bug report on the DD-WRT tracker.

Minor issues with this build and earlier Kong builds:

1. On the Wireless/WL0-Advanced and Wireless/WL1-Advanced tabs (Wireless_Advanced-wl0.asp and Wireless_Advanced-wl1.asp), TX Power after a 30-30-30 reset incorrectly defaults to 100. The default should be 40; the explanatory text for that field says "(Default: 40, Range: 1 - 251mW)".

2. On the Services/VPN tab (PPTP.asp), the Hash Algorithm field incorrectly defaults to SHA256. I believe that the field should default to SHA1, since that's the algorithm that OpenVPN uses by default when no algorithm is specified in the openvpn.conf configuration file.

3. On the Services/NAS tab (NAS.asp), in the MiniDLNA section: After a 30-30-30 reset neither the "Enable" nor "Disable" radio button is selected.

3. On the Services/NAS tab (NAS.asp), in the MiniDLNA section: After a 30-30-30 reset neither the "Enable" nor "Disable" radio button is selected.

4. On the Services/Proxy Server tab (Proxy.asp): After a 30-30-30 reset neither the "Enable" nor "Disable" radio button is selected.

5. On the Security/Firewall tab (Firewall.asp): If "Limit PPTP Server Access" is checked, it reverts to unchecked when Save or Apply Settings is clicked.

berndw
berndw's picture
I got this in my logfile

I got this in my logfile

May 8 10:15:23 router55 kernel: klogd started: BusyBox v1.19.4 (2012-05-07 20:21:19 CEST)
May 8 10:15:23 router55 kernel: nf_conntrack_pptp: Unknown symbol nf_ct_gre_keymap_destroy
May 8 10:15:23 router55 kernel: nf_conntrack_pptp: Unknown symbol nf_ct_gre_keymap_flush
May 8 10:15:23 router55 kernel: nf_conntrack_pptp: Unknown symbol nf_ct_gre_keymap_add
May 8 10:15:23 router55 kernel: nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_exp_gre
May 8 10:15:23 router55 kernel: nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_inbound
May 8 10:15:23 router55 kernel: nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_outbound
May 8 10:15:23 router55 kernel: nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_expectfn
May 8 10:15:23 router55 kernel: nf_nat_pptp: Unknown symbol nf_nat_need_gre

Kong
Kong's picture
Hi berndw,

Hi berndw,

hmmm, here the correct modules get loaded what output do you get with command:

cat /var/log/messages | grep vpn

@fastfwd

just after I included the mask_br fix Sash changed some more code in 19211, which may fix openvpn issues, we will see with the next build.

I checked the 100mW default on the E4200 , this is a default value for the e4200, as this gets dynamically set when the firmware detects the router at bootup. But since the webinterface displayed value is compiled in and not dynamically read it is not possible to match this. So the 40 is the general default value but for some models this is different.

Teknowiz
Teknowiz's picture
I can also confirm the Limit

I can also confirm the Limit PPTP Server Access bug. Setting the NVRAM variable "limit_pptp=" to 1 seem to work so it seems like a gui issue.

berndw
berndw's picture
Hi Kong

Hi Kong

I got a lot of messages like this ;-)

Jan 1 00:00:13 router55 syslog: vpn modules : vpn modules successfully unloaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : vpn modules successfully unloaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:14 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:15 router55 syslog: vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:16 router55 syslog: vpn modules : vpn modules successfully unloaded
Jan 1 00:00:16 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:16 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:16 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:16 router55 syslog: vpn modules : nf_nat_pptp successfully loaded
May 8 10:15:24 router55 syslog: vpn modules : vpn modules successfully unloaded
May 8 10:15:24 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
May 8 10:15:24 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
May 8 10:15:24 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
May 8 10:15:24 router55 syslog: vpn modules : nf_nat_pptp successfully loaded
May 8 10:15:28 router55 syslog: vpn modules : vpn modules successfully unloaded
May 8 10:15:28 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
May 8 10:15:28 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
May 8 10:15:28 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
May 8 10:15:28 router55 syslog: vpn modules : nf_nat_pptp successfully loaded
May 8 10:15:30 router55 syslog: vpn modules : vpn modules successfully unloaded
May 8 10:15:30 router55 syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
May 8 10:15:30 router55 syslog: vpn modules : nf_nat_proto_gre successfully loaded
May 8 10:15:30 router55 syslog: vpn modules : nf_conntrack_pptp successfully loaded
May 8 10:15:30 router55 syslog: vpn modules : nf_nat_pptp successfully loaded

At the moment i'm back to 18730, the last working OpenVPN-Firmware, i don't use PPTP

Bernd

fastfwd
fastfwd's picture
Kong: Thank you for the

Kong: Thank you for the comments here and on ticket 2536. I'm looking forward to testing a newer build when one becomes available.

Regarding the TX power default:

I understand that the default value is only a starting point and that each installation might require experimentation to discover the best value. I also vaguely recall reading that you made the change to 40mW in your builds, from 71mw or 100mW in the mainline DD-WRT code, for reasons of radio stability and reliability.

Are you saying that 40mW is not a good starting point for the E4200 and that the gui SHOULD default to 100mW for that router, or are you saying that 40mW is fine for the E4200 but that the gui unavoidably defaults to 100mW for reasons that are outside your easy control?

Kong
Kong's picture
Currently uploading a new

Currently uploading a new build with openvpn and pptp fix.

Wireless power setting works the following way:

Default on broadcom is 40mW, depending on the antennas some models need higher tx power or lower, e.g. the default for the RT-N16 is only 17mW.

I can of course change the value for the E4200 but then you'll suffer:-)

fastfwd
fastfwd's picture
No, there's no need to change

No, there's no need to change my TX power -- but thanks for offering.

I just wanted to know, without testing, whether it was best to stay with the 100mW default or override it to 40mW. You've answered my question: I'll leave it at 100mW on the E4200. Thank you!

And thanks for uploading Build 19215; I'll test that one later tonight.

foofoo
foofoo's picture
Can you please fix the WDS

Can you please fix the WDS bug? Sometimes it connects and sometimes it doesn't. On Wireless Status both routers show connection signal to wds but neither both ends cannot be pinged. The WDS is on 5ghz, exact same settings and exact same firmware, hardwaer is e3000 and e4200. Thank you