QoS doesn't appear to be working for me. As I work from home with teenage kids, it's a major issue! Have returned to BrainSlayer's 24160 build for the time being.
Just downloaded and installed the fw 25015 dated Sep. 17 on my Asus RT-N66U. Everything seems to be working pretty well, except for some inherited issues.
(Note:this N66U router has its WAN disabled and is running in pure AP mode.)
Firstly,after setup and reboot, I couldn't connect to wl0.1, even though its radio was on. Issuing the command "wl -i wl0.1 status" gave me a Mac address that is slightly different from the Mac obtained from Wireless>Basic Settings tab. In another word, it is showing E2:XX:XX:XX:XX:11 instead of E2:XX:XX:XX:XX:13. By clicking the Apply Settings button, the former Mac changed and matched the latter. And then I could connect to this wl0.1 intrface.
Secondly, the commands "startservice radio_off_0" and "startservice radio_on_0" are not working consistently either.
I've experienced both issues with previous fw (24200).
Having the same problem but on a R7000. After reboot cannot longer connect to wl0.1. Clicking on "Apply Settings", clients can connect again.
After reboot "wl -i wl0.1 status" returns:
SSID: ¾
BSSID: AB:CD:EF:GH:IJ:7C
and after "Apply Settings":
SSID: ò¾
BSSID: AB:CD:EF:GH:IJ:82
SSID looks also different characters.
Upgraded to 25015m-sp1, unfortunately, the issue with wl0.1 interface still exists on my N66U.
That is, after reboot I still get BSSID as E2:XX:XX:XX:XX:11 for wl0.1; clicking on "Apply Settings", the BSSID then changes to E2:XX:XX:XX:XX:13 for the same interface, and I can connect to this wl0.1 interface thereafter.
BTW, E2:XX:XX:XX:XX:11 is actually my WAN MAC (and WAN is disabled), if that matters.
Just downloaded and installed the fw 25015 dated Sep. 17 on my Asus RT-N66U. Everything seems to be working pretty well, except for some inherited issues.
(Note:this N66U router has its WAN disabled and is running in pure AP mode.)
Firstly,after setup and reboot, I couldn't connect to wl0.1, even though its radio was on. Issuing the command "wl -i wl0.1 status" gave me a Mac address that is slightly different from the Mac obtained from Wireless>Basic Settings tab. In another word, it is showing E2:XX:XX:XX:XX:11 instead of E2:XX:XX:XX:XX:13. By clicking the Apply Settings button, the former Mac changed and matched the latter. And then I could connect to this wl0.1 intrface.
Secondly, the commands "startservice radio_off_0" and "startservice radio_on_0" are not working consistently either.
I've experienced both issues with previous fw (24200).
Having the same problem but on a R7000. After reboot cannot longer connect to wl0.1. Clicking on "Apply Settings", clients can connect again.
After reboot "wl -i wl0.1 status" returns:
SSID: ¾
BSSID: AB:CD:EF:GH:IJ:7C
and after "Apply Settings":
SSID: ò¾
BSSID: AB:CD:EF:GH:IJ:82
SSID looks also different characters.
Upgraded to 25015m-sp1, unfortunately, the issue with wl0.1 interface still exists on my N66U.
That is, after reboot I still get BSSID as E2:XX:XX:XX:XX:11 for wl0.1; clicking on "Apply Settings", the BSSID then changes to E2:XX:XX:XX:XX:13 for the same interface, and I can connect to this wl0.1 interface thereafter.
BTW, E2:XX:XX:XX:XX:11 is actually my WAN MAC (and WAN is disabled), if that matters.
wan disabled could make a difference, as this changes the timing, and I recall I have fixed one issue with bssid before were the interface was not ready yet. Once I find the time I'll look into it. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
updated my Asus RT-AC66R to 25015-SP1. nothing negative to report. _________________ Please state what make and model router plus the build number and type of DD-WRT you are using. Screen prints and a network diagram can are also helpful. Before you create a new post, use the search function. Chances are your issue has happened to someone else.
Dear Kong, thanks for your hard and excellent working on kong build,
one bug for both 25015M and 25015M SP1 for asus ac66 and Netgear 6300v1, when I use a pc behind the 25015M route, I can't dial up to a pptp server, but other builds are OK, hope you will notice this small problem.
thank you.
You can find Kongs newest version (all beta & no support)here.
http://desipro.de/ddwrt/ _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
Pptp passthrough is broken in version > 24800 <= 25100. Use either version 24800 or a version newer than 25100.
yes, I found that. my netgear R6300v2 with kong version 25100 also has the same symptom, even by default I enable vpn passthrough, and I upgrade to the kong 25735M, issue solved.
but with my R6300 and asus ac66R, kong's newest K3-AC version still is 25015SP1, so vpn passthrough still can't work, I am waiting for a new release.
