This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build. (eg: 19519_NEWD-2_K2.6_mega-nv64k.bin).Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly, do NOT flash this experimental test build.
Last edited by phlegmer on Fri Jul 20, 2012 19:30; edited 1 time in total
I wasn't able to access the USB drive on build 19342, although it was mounted. Now it seems to be working. Thanks _________________ ▲ ACTIVE ▲
[Broadcom ARM64] ASUS RT-AC86U v? --802.11ac wave 2-- RT-AC86U Thread | ASUSWRT-Merlin 384.18-Kernel-4.1.27
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Fri Jul 20, 2012 16:25 Post subject:
skinnum wrote:
WNDR3700 system info displays channel as unknown
Indeed, just flashed this to my WZR-HP-G300NH - running in client mode + VAP to my WZR-HP-AG300H (still running 18024 on it), wired access on the G300NH is fine, but the VAP is reporting as unknown channel and not letting any clients connect to it, my client can see the SSID, just never connects. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Jul 20, 2012 16:40 Post subject:
QoS is better.. priorities seem to be working as well as layer7 so far.. though they mark(mark=X) differently now than stated on the wiki but it is matching the packets.
Wireless channel says unknown for WNDR3700 v1 & DIR-825 B1. PPTP server works again but MTU/MRU settings still stay blank after applying.
VAP is still visible & connecting clients fine here, how do you have your VAP setup buddee? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Correct me if I am wrong, but I get the impression that with every new build more new bugs are being introduced than old bugs being fixed? That would be very sad.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Fri Jul 20, 2012 16:57 Post subject:
My VAP is setup no differently than i have always done it. When i roll back to 19342, it works again with the same setup. Cept with older builds, since 17xxx, the VAP is reporting wrong channel but it still works, i use channel 11 and the VAP is always reporting channel 1 - which isn't correct, but with this build, its not letting clients connect to the VAP whatsoever.
Here is my pic of the config, which if you read closely, none of the values are correct, not to mention any of my machines that are set to auto connect to the VAP aren't doing so, there should be 3 client machines connected, its not allowing them to, roll back to 19342 - and it works fine, they auto connect like they should. There are already open trac tickets regarding VAP not working correctly, well, i see why now.. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Jul 20, 2012 17:20 Post subject:
buddee wrote:
My VAP is setup no differently than i have always done it. When i roll back to 19342, it works again with the same setup. Cept with older builds, since 17xxx, the VAP is reporting wrong channel but it still works, i use channel 11 and the VAP is always reporting channel 1 - which isn't correct, but with this build, its not letting clients connect to the VAP whatsoever.
Here is my pic of the config, which if you read closely, none of the values are correct, not to mention any of my machines that are set to auto connect to the VAP aren't doing so, there should be 3 client machines connected, its not allowing them to, roll back to 19342 - and it works fine, they auto connect like they should. There are already open trac tickets regarding VAP not working correctly, well, i see why now..
Have any settings other than default in Setup -> Networking page? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Wireless channel says unknown for WNDR3700 v1 & DIR-825 B1. PPTP server works again but MTU/MRU settings still stay blank after applying.
I'm running 18777. I just noticed, recently, that 5ghz radio wireless channel displays as "unknown" in the system info screen, when the channel is set to auto. Never tried setting it to anything else.
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Fri Jul 20, 2012 18:27 Post subject:
tatsuya46 wrote:
buddee wrote:
My VAP is setup no differently than i have always done it. When i roll back to 19342, it works again with the same setup. Cept with older builds, since 17xxx, the VAP is reporting wrong channel but it still works, i use channel 11 and the VAP is always reporting channel 1 - which isn't correct, but with this build, its not letting clients connect to the VAP whatsoever.
Here is my pic of the config, which if you read closely, none of the values are correct, not to mention any of my machines that are set to auto connect to the VAP aren't doing so, there should be 3 client machines connected, its not allowing them to, roll back to 19342 - and it works fine, they auto connect like they should. There are already open trac tickets regarding VAP not working correctly, well, i see why now..
Have any settings other than default in Setup -> Networking page?
tatsuya46, no offense, but i know how to setup a client mode + VAP, and like i said, its no different than any other time i set it up. Its not functioning for me, but also consider you don't have a WZR-HP-G300NH, so for your unit - it maybe working, for mine, it is not. Also consider that even what you see in the pic i posted, isn't correct, no matter how you slice it.
But to simply answer your question: no, i didn't change anything in the Networking tab, i shouldn't have to, i'm not running multiple WLANs, just client mode + vap, and no, i'm not going to unbridge anything either, once again, i shouldn't have to. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ