Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DennisOlof1]

I am back with a update. This is a follow up to the original thread of the bugs in the original firmware for the dap-1360.

Hardware Version=C1
Firmware Version=3.02

http://forums.dlink.com/index.php?topic=53373.0

Now I have been on the v3.04 firmware for some time. And all the bugs i reported in the URL above are gone, as far as I can tell. Even though they did not post any information on the v3.04 firmware update I think they reworked so many thing in the firmware they just left out that information, it was probably to much to list. The way I can tell this is by looking at the logs, what happens when the unit boots up and so on. Anyway I have been running one unit as "Access Point" and the other one as "Wireless Client". And everything is running perfect. There are a few minor issues with the web interface but over all it is working great now. Stable and solid.

It does feel like I am using my computer connected with a LAN cable, as my network in the house is wired 100Mbit, even though I am running my computer over the WLAN. It is working great, everything it smooth, no reboots or any problem with the DAP-1360. The only things I see under "statistics" -> "logs" are a few things that I do not know what they are, but I do not thing it matters any more because the units are now working fine. Great by D-link to fix these errors as it would crash and lock up, terrible bad bugs in the v3.02 firmware.

-----------------------------------

From the "Access point" I do see this reported, but I guess you can ignore it, and even
the "D3 hot -> L1" lines do stop after a few log pages, with the new firmware.

"wlan0: Delete MC entry not found!"
"wlan0: Authentication failled! (4-2: MIC error)"
"D3 hot -> L1"

-----------------------------------

From the "Wireless Client" I do see this reported, but I guess you can ignore it, and even
the "D3 hot -> L1" lines do stop after a few log pages.

"wlan0: Delete MC entry not found!"

-----------------------------------

So, over all, the firmware must be updated to get rid of the bad bugs that makes the unit crash and
stop working. I am sure all the other functions I have not tried working fine with the new firmware.
Also the unit does not get hot, speeds are good, and the response from the webinterface is fast.

[marcusosb]

Hi I have read your previous posts and I have experienced the exact same issue that you have had.
I cant seem to find the v3.04 firmware you have described, all my searches thus far point me to v3.02
Would you be able to provide the link to where you downloaded this version from?

[FurryNutz]

http://forums.dlink.com/index.php?topic=56324.0

Hi I have read your previous posts and I have experienced the exact same issue that you have had.
I cant seem to find the v3.04 firmware you have described, all my searches thus far point me to v3.02
Would you be able to provide the link to where you downloaded this version from?

[DennisOlof1]

I am back with a update, now on firmware v3.04 and it has been running great compared to before the firmware update. There are no changes to the "logs" I have reported before.

And it seems as the "logs" reset or "start over" when there is no empty space left, and I have found no strange reports in the logs, there are a few things that could be cleaned up as some thing reported in the "logs" are not in use. But as it has no impact on the operation of the unit(s) it does not need to be fixed. So I have been running one unit as a standard "Access Point" and connected to that with another unit (same make / model / firmware) as a "wireless client". I have been running the setup for about six weeks. Permanently connected (just like using a LAN) cable and going about my business as usual. So far so good, until today.

First of all, I have made no changes to the unit(s) as the configuration is the same as when I started testing the system. For some reason the "wireless client" lost the connection to the "access point" and I did have the option to check the "logs" on both units, as I have multiple computers, cables and so on. At first I thought the "access point" had crashed, but I cleared the logs and it showed that the "wireless client" unit was trying to get "authenticated" or "re-authenticate" because the connection was lost . But the "AP" keeps rejecting the unit, over and over again, like it was stuck in a loop.

So I saved some data from the logs and though, ah, ok, I will reboot the units and see if that fixes the problems. To my big surprise the problem is still there and I will post some information here what is going on. The funny thing is that by using a laptop I could connect to the "AP" before AND after I rebooted it, so it is working just fine. But somehow it is now rejecting my "wireless client" unit to connect, even though both units have been rebooted.

It is strange because I have made no changes to the units, what so ever. You would expect after rebooting the two units that they would start working just fine again, somehow the AP is now blocking my "wireless client". Feels like this is a bug as I noticed before that it does take several "authentication" attempts to connect to the access point, regardless of what device you are using to access the WLAN.

Worst case scenario, you need to do a H/W reset of the units, that would fix the issue, but is kind of extreme, a power cycle of the units should be enough.

[FurryNutz]

Any other interferences in the area? New WiFi neighbors?

What wireless modes are you using? Mixed or single?

[DennisOlof1]

Puh, that took a lot of work. It seems this problem has been reported on other dlink units as well. I do not know why, what the error is. But this will probably make you wonder, I have no clue what it is or if you can fix it.

1. First I thought the units where broken. I tried a lot of things, and in the end I did a factory reset (using the button on the units) and re-installed everything. This did not solve anything, and my setup is as described above. Connecting with my laptop works fine, tried with a smart phone to. Worked before, during and after the breakdown. So no problems there.

2. It seems that the "wireless client" can not connect any more to the "AP" regardless of all actions taken so far, to reset / re-install / re-configure my system setup. I even tried to use my spare unit (that is also a
DAP-1360 and has not been in use, or even activated, during my test period), and that could not connect as a "wireless client", even though it has different MAC address and gets different IP from my zywall DHCP.

3. It seems that however I install my units (got three dap-1360) one as "wireless client" and the other as "AP" it does not work. Here is the strange part. I have a older DWL-G700AP that can run as "wireless client" (remember no specific changes has been made to the AP configuration), and that unit could connect to my "AP" even though it had to go through a few authentication processes initiated from my "AP". It does work, I can use a computer over this setup, even though the older DWL-G700AP is a bit slow, at last it is WORKING AGAIN !

Here is what keeps repeating it self on the "AP" when I try to use another DAP-1360 as a "wireless client". Remember I have tried swapping the units around and so on, but I still get the same results regardless of what unit is running as "AP" and so on. Such a strange error, and I can not get it to go away even though a hardware reset should remove anything left in the units memory etc.
 
rlx-linux user.warn kernel: wlan0: WPA2-AES PSK authentication in progress...
rlx-linux user.warn kernel: wlan0: A wireless client is associated - C8:BE:19:71:FF:98
rlx-linux user.warn kernel: wlan0: A STA is rejected by 802.1x daemon - C8:BE:19:71:FF:98

Sometimes I see this to to in the loop above.

rlx-linux user.warn kernel: wlan0: Authentication failled! (4-2: MIC error)

Keeps looping in the logs and no success at establishing a connection. And because it works with the dwl-g700ap I am confused and can not figure out what is going on. The only thing I do know is that all units still work as standard APs and accepts connections from laptops, smart phones but for some reason my other dap-1360 units are blocked from running in my setup.

Here is someone with the same problem but on another dlink product, more or less.

http://forums.dlink.com/index.php?topic=39174.0

Wonder if this is a firmware issue or not. As the older v3.02 had other major issues that just made the units crash to and from but at least v3.04 is stable. It is so strange, you would think that a H/W reset of the units would get you up and running again. And that this error could happen again after time, that is at least somewhat logical. I will get back with updates if I find anything that will fix this problem.

[DennisOlof1]

Puh, some more wasted time testing out this problem.

I have used different SSID, passwords and other things that was suggested could fix the problem but no luck there. The only good thing is that at least I will not be using the units this way but more as "standard" APs and I guess I will have to use a timer to power cycle the units once every day, as that might prevent this error.

So, factory reset did not work as I stated before. However there are a few things I got wrong, as I have done some more testing. Everything works fine, if you use no encryption or WEP. But with WPA / WPA2 (TKIP or AES) it does not work. So "wireless client", "bridge" and other modes, did not work. Anything where you used WPA or WPA2 encryption.

My older DWL-G700AP can connect as "wireless client" in WPA2 with AES without problems, so can my laptop to. The laptop has always been able to connect regardless of encryption.

My conclusion is that this must be some sort of firmware bug, or that a "factory reset" does not clear everything in the unit even though that is stated by the manual. I have seen some people using JTAG on some D-link products and getting some sort of debug mode or at least you can see everything thats is going on as the unit is booting. So this is what I am thinking about in terms of information provided by the unit, of what is going on, other than the information I can see in the logs.

Will just have to wait and see if D-link will produce a fix for this somewhere down the line, I guess they will come out with more fixes and firmware updates as the units are not "end of life".

[FurryNutz]

I recommend that you phone contact D-Link support and talk to level 2 or higher support and inform them about this...Let us know what you find out.

[DennisOlof1]

FurryNutz, I do not need that. It might be possible to re-upload the same firmware to sort the problem.

Anyway, as I am using a timer to power cycle the units, that are now running, to create three WLAN spots, ch1, ch6 and ch11 (close proximity), and they are connected to a firewall. Everything seems to work fine.

At least v3.04 of the firmware is stable and fast, compare the the original v3.02 that was bad, as the units would randomly crash or lock up. Even if there are more firmware updates for the units, in the future, I will probably not use new firmwares, as the units are in a remove location, I can not get to them.

So I am happy as it is.

Thanks to the people on the forums (you) and dlink who probably read my postings here and fixed the major issues and got the unit to at least good working order, that is at least what you would expect from a product you buy, minor errors and so on you can ignore. No firmware is perfect and so on.

So I believe my issues with the DAP-1360 are finally resolved, once and for all.

[FurryNutz]

Yay. Thanks for sharing the info.

Enjoy.

[Axel49]

I have added a comment in a new thread concerning this very interesting subject!

Follow-up thread: http://forums.dlink.com/index.php?topic=60378.0