Print

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

[smeyerpe]

I have a DAP-1522 setup as a bridge with my Asus RT-N56U on the 5GHz channel. When these two devices are connected, they are perfect for what I want which is to connect my Blu Ray player and TV with their LAN ports to the network. However, the connection randomly drops. The first DAP I had before returning it would, during a infinite ping test from PC->Router->DAP would succeed 11 times with 1 or <1 ms response time (yes!) and then time out 4 times (no!) before reconnecting for another successful 11 pings followed by 4 failures. The exact pattern showed itself when pinging the router from Laptop->DAP->Router. Figuring I got unlucky, I returned the DAP for a 2nd one. This one is much worse as there is no discernable pattern to the drops. Using the same ping tests, the silly thing will connect for as long as 10 minutes and as short as never (ok so I really waited 10 minutes or so). On this unit, as soon as the connection goes, it is gone for good. It never reconnects until the DAP is power cycled. Power cycling the router does not seem to have any affect on the comms. The GREAT part is, when I go to the DAP config web page (from the laptop plugged into the DAP), there is nothing out of the ordinary in the logs AND the status says it is connected. Meanwhile pings are failing, failing, failing...

The other thing that really bothers me is, if I switch the DAP to connect to the 2.4GHz channel of the router, it works flawlessly. Unfortunately, I don't want my streaming vid addictions to eat up my web addictions which are currently residing on the 2.4GHz band.

I've tried a few items posted here such as setting the DAP to only use AES, turning off Wi-Fi Protected Setup and disabling wireless MAC cloning. Nothing seems to change the behavior. I haven't yet poked around in the "Advanced Wireless" setting screen or the QoS.

This is the device info as reported by the DAP (names may have been change to protect the mostly innocent):

Firmware Version : 1.31 , Tue 30 Nov 2010
Connection Type :   Static IP 
MAC Address :  XX:XX:XX:XX:XX:XX
IP Address :  192.168.14.2
Subnet Mask :  255.255.255.0
Default Gateway :  192.168.14.1
Wireless Radio :  Enabled
Status :  connected
MAC Address :  XX:XX:XX:XX:XX:XX
Network Name(SSID) :  XXXXXXXX50
Channel :  48
Security Type :  WPA2- Personal / AES
Wi-Fi Protected Setup : Disabled / Configured

Any suggestions would be greatly appreciated. If you need more info on my setup, please just ask. Thanks in advance.

[smeyerpe]

In a slight update, as I was typing the original post, my pings (PC->Router->DAP) started working (yes!) for exactly 11 times before timing out 4 times (no!). Rinse, repeat. 11 good. 4 bad.  To infinity and beyond.

So, it looks like, given enough time, the current DAP I have will behave just like the first one.

Has anyone ever seen anything like this? Or, better yet, seen it and know how to fix it?

I should also mention that all this is happening with the DAP and router about 5 feet from each other while I'm testing the DAP. The DAP shows a signal strength of 85% on the 5GHz and 100% on the 2.4GHz.

Thanks again.

[FurryNutz]

Any cordless house phones?
Any other WiFi routers in the area?

Are the routers set up for automatic or manual channel scan?

[smeyerpe]

Thanks for the quick reply Furry.

Any cordless house phones?

Yes, we have a set of DECT 6.0 phones. I believe these transmit at 1.9MHz so I assume they aren't an issue.

Any other WiFi routers in the area?

Besides the 2.4MHz band on my router, the only other 2 wireless devices that show up with inSSIDer are two 802.11g Linksys (one of which is completely open so if anyone needs free wifi, let me know).

Are the routers set up for automatic or manual channel scan?

I have it set to manual channel 48 with a channel bandwidth of 20/40Hz. I just picked 48 for no good reason other than to mess around with it. Likely, I should have set it to at least 40Hz higher than the default channel, but since I'm the only 802.11n on the block, I'm not all that worried about it yet. I'm happy to try other settings as well.

[jerry6]

try ch 157 , 50% signal strength and short GI in advanced . if nothing works maybe you have a bad 5 ghz radio ,
 What revision you have ?
I'm thinking of buying another , have first version , wondering if new version has changed for the worse

[FurryNutz]

Yes I would disable SHORT GI..Might disable WMM Enable too to test. Keep us posted.

[smeyerpe]

try ch 157 , 50% signal strength and short GI in advanced . if nothing works maybe you have a bad 5 ghz radio ,
 What revision you have ?
I'm thinking of buying another , have first version , wondering if new version has changed for the worse

As a stand alone or aggregate change, neither the signal strength or GI setting affect the functionality. Changing the channel to 157 did alter the failures however. On 157, there is no discernible pattern to the ping failures. On five consecutive 100 pings, I got 28% drop, 4% drop, 0% drop, 27% drop and 3% drop.

Interestingly, the pings always fail in groups of 3 or 4 in a row. When only 3 fail, either the ping just before or just after nearly fails, in the 1.7-1.9s range (with a 2s default timeout).

I haven't yet tried messing with the WMM settings. I'll try that next. I'll also check the version of the actual box and report that as well. The firmware is 1.31 which I believe to be the latest.

Thanks again for the suggestions.

[FurryNutz]

I recommend turning OFF all WIRELESS devices, FULL POWER OFF while testing. Of course leave the router and DAP going and connect one PC for testing. Let us know.

[smeyerpe]

I recommend turning OFF all WIRELESS devices, FULL POWER OFF while testing. Of course leave the router and DAP going and connect one PC for testing. Let us know.

All of the testing has been done with only the wireless devices needed being on. So, the router, the DAP and the laptop. The desktop I use for testing is hardwired to the router.

The hardware version is A1, by the way.

I may just have to bite the bullet and spend another $40ish to get another Asus router and set it up as a bridge. Having a bridge that only works intermittently is a real problem for streaming. I'll try a few more channels to see if that helps. Right now, I'm not expecting much. *sigh*

[FurryNutz]

What FW version is currently loaded?

Does this happen in AP mode as well as bridged mode?
I presume if it does then it's possible this unit needs to be RMAd.

[kskimmel]

Go to 5 ghz page on the ASUS 56U and turn off link aggregation.  I had the same issue and this fixed it.

[FurryNutz]

Let us know if this helps.

[smeyerpe]

Go to 5 ghz page on the ASUS 56U and turn off link aggregation.  I had the same issue and this fixed it.

Well shoot - I actually took the DAP-1522 into work and set it up as an access point. Perhaps I'll go buy another one and give that a whirl.

As an aside, the access point has been working flawlessly at work with upwards of 30 devices hitting it at the same time.