Print

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

[valith]

Model Name: DIR-868L   Hardware Version: B1   Firmware Version: 2.01

5GHz working fine
2.4GHz band, WPA, password incorrect

I tried to connect with 3 devices: MacBook and two iPhones, the result: "password incorrect" (on all devices).
When I keep the password the same and change WPA to WEP, then it works like a charm.
I deleted the network on my iPhones and MacBook (so nothing is cached).

I also tried changing the password, e.g. " 12345678", same issue. WPA "password incorrect", change to WEP, working fine.
Also changed the name of the network, still the same issue.

What could be wrong? Any suggestions?
Is my DIR-868 OK?

On the 5GHz band no issues at all.

By the way, I use it as an access point, so DHCP is disabled and I use the LAN port to connect it to my network instead of the WLAN port, but this shouldn't affect this imo.

Thanks in advance.

[FurryNutz]

Link>Welcome!

• What region are you located?
• Has a Factory Reset been performed?

You are behind on FW so if a factory reset fails to resolve this you might want to update FW:
http://forums.dlink.com/index.php?topic=62888.0

Follow the linked information to apply it...

[valith]

Link>Welcome!

• What region are you located?
• Has a Factory Reset been performed?

You are behind on FW so if a factory reset fails to resolve this you might want to update FW:
http://forums.dlink.com/index.php?topic=62888.0

Follow the linked information to apply it...

I'll read the FAQ
Location is Europe
I'll try FW update (download doesn't work now, but i'll try later)
And I'll try a factory reset too

I upgraded my FW from 2.00 to 2.01 (because I had the issue on 2.00 too). In the bug fix list of 2.03 I don't read anything that would fix my issue..

[FurryNutz]

Let us know how it goes either way. 

[valith]

factory reset gave me new insight.
when I disconnected it from the network and tried to access 2.4GHz with factory password: it worked!

Then I resumed, altering my IP address to my 192.168.x.x range (same as modem/router), turn off DHCP etc etc. connect the cable to my modem/router to the LAN port. Then the issues appeared again.. 

ping response to the DIR-868L wasn't stable (both wifi and LAN), messages got lost and/or response was bad.

This made me investigate the connection to my modem/router.
So I disconnected the DIR-868L and attempted to directly ping my modem/router (Cisco ECP3925 from my ISP).
I think that's were all the trouble starts...

Here's the result of my ping (LAN cable attached to modem/router, so without DIR-868, no use of wifi):
MacBook-Pro-van-Stefan:~ stef$ ping 192.168.x.x
PING 192.168.x.x (192.168.x.x): 56 data bytes
64 bytes from 192.168.x.x: icmp_seq=0 ttl=64 time=1.075 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 192.168.x.x: icmp_seq=1 ttl=64 time=2436.645 ms
64 bytes from 192.168.x.x: icmp_seq=2 ttl=64 time=1436.292 ms
64 bytes from 192.168.x.x: icmp_seq=3 ttl=64 time=434.847 ms
64 bytes from 192.168.x.x: icmp_seq=4 ttl=64 time=1.274 ms
64 bytes from 192.168.x.x: icmp_seq=5 ttl=64 time=1.018 ms
64 bytes from 192.168.x.x: icmp_seq=6 ttl=64 time=1.024 ms
Request timeout for icmp_seq 9
64 bytes from 192.168.x.x: icmp_seq=7 ttl=64 time=3839.732 ms
64 bytes from 192.168.x.x: icmp_seq=8 ttl=64 time=2839.207 ms
64 bytes from 192.168.x.x: icmp_seq=9 ttl=64 time=1839.177 ms
64 bytes from 192.168.x.x: icmp_seq=10 ttl=64 time=839.111 ms
64 bytes from 192.168.x.x: icmp_seq=11 ttl=64 time=1.258 ms
64 bytes from 192.168.x.x: icmp_seq=12 ttl=64 time=874.597 ms
64 bytes from 192.168.x.x: icmp_seq=13 ttl=64 time=1.084 ms
64 bytes from 192.168.x.x: icmp_seq=14 ttl=64 time=1.300 ms
64 bytes from 192.168.x.x: icmp_seq=15 ttl=64 time=1.105 ms
64 bytes from 192.168.x.x: icmp_seq=16 ttl=64 time=1.003 ms
64 bytes from 192.168.x.x: icmp_seq=17 ttl=64 time=0.898 ms
64 bytes from 192.168.x.x: icmp_seq=18 ttl=64 time=0.950 ms
64 bytes from 192.168.x.x: icmp_seq=19 ttl=64 time=1.286 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
64 bytes from 192.168.x.x: icmp_seq=20 ttl=64 time=14937.991 ms
64 bytes from 192.168.x.x: icmp_seq=21 ttl=64 time=13936.044 ms
64 bytes from 192.168.x.x: icmp_seq=22 ttl=64 time=12935.515 ms
64 bytes from 192.168.x.x: icmp_seq=23 ttl=64 time=11934.229 ms
64 bytes from 192.168.x.x: icmp_seq=24 ttl=64 time=10931.481 ms
64 bytes from 192.168.x.x: icmp_seq=25 ttl=64 time=9940.769 ms
64 bytes from 192.168.x.x: icmp_seq=26 ttl=64 time=8939.275 ms
64 bytes from 192.168.x.x: icmp_seq=27 ttl=64 time=7939.032 ms
64 bytes from 192.168.x.x: icmp_seq=28 ttl=64 time=6935.061 ms
64 bytes from 192.168.x.x: icmp_seq=29 ttl=64 time=5934.329 ms
64 bytes from 192.168.x.x: icmp_seq=30 ttl=64 time=4929.460 ms
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
--- 192.168.x.x ping statistics ---
48 packets transmitted, 31 packets received, 35.4% packet loss

So I think I should focus first on this issue.
Because my DIR-868L is a replacement for a TP-Link that was not working stable anymore (also 2.4GHz router installed as access point, DD-WRT).
I assume my modem/router (Cisco ECP3925) is affecting other parts of my network.

I reported this to my ISP.
Any suggestions?

[FurryNutz]

Internet Service Provider and Modem Configurations

• If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT and How NAT Works. Call the ISP and ask to see if the ISP modem can be bridged. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address of 192.168.0.1. Check to see if this is the same on the ISP modem, and if modem can't be bridged, change the DIR router to 192.168.1.1 or .0.254.
  Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on a Router

[valith]

Thanks for your quick response!
I understand what you try to tell me, but I think it won't work for me. Unless I miss something. I'll try to explain my set-up.

My home has multiple levels.
I'll try to draw the picture. But I need my modem as router, due to the setup (otherwise I'll need an additional router).
To my modem/router, multiple floors are connected
I want to use my DIR-868L as an additional access point with build in switch (using only LAN ports, not the WAN, and disable DHCP) According to the manual, this must be possible. And it was working, but only for the 5Ghz band.

I diasbled UpnP on my Cisco modem/router (to avoid ping/connection issues), but this didn't help me out.
If I ping from another point in my network, I also get high pings e.g. 775ms every now and then. most pings are ±1ms, but every now and then a spike can be seen.
Even 2173ms and some disconnects right now.
So I assume it's not cabling related, but an unstable Cisco EPC3925..
I also tried connecting my MBP to the WAP, connected via another cable to the modem/router. Also high pings ever now and then and some disconnects.

 +----------+                                             
|          |                                             
|  ISP     |                                             
+----+-----+                                             
     |                                                   
+----v-----+                                             
|          |                                             
| CISCO    |                                             
| 3925     |                                             
+-+--+--+--+                                             
| |  |  |        +---------------+    +----------------+
| |  |  |        |               |    |                |
| |  |  +-------^+   SWITCH 8P   |    |    WAP 2.4 & 5GHz
| |  |           |               |    |                |
| |  |           +---------------+    +----------------+
| |  |                                                   
| |  |                                                   
| |  |                                                   
| |  |           +---------------+                       
| |  |           |               |                       
| |  +----------^+  DIR-868L     |                       
| |              |               |                       
| |              +---------------+                       
| |                                                     
| |                                                     
| |                                                     
| |                                                     
| |                                                     
| +-------------->                                       
|                                                       
|                                                       
+---------------->                                       

[FurryNutz]

Well you have a WAP and the 868L running.
You can run the WAP as well, however technically you should have the WAP and the switch after the 868L and the ISP modem should be bridged. You have a could NAT condition which is not preferred.

ISP modem(bridged)>DIR-868L>switch<>WAP

Having two sources for WiFi radios can be done however different channels should be used:
DIR-868L: 2.4Ghz = Channel 11/5Ghz = 36 or 48
WAP:2.4Ghz = Channel 1/5Ghz = 149 or 165

SSID and PW can be the same on the 868L and WAP

[valith]

I found the cause...
Not the modem/router from my ISP (I replaced it, I noticed a little improvement, but still not a full fix. Ping times improved, less packet loss, but still WiFi 2.4Ghz issues).
But then I disconnected my Network printer (because I saw a lot of flickering lights on my switch to which the Canon MP640 printer was connected).
Instantly the 2.4GHz band was available and ping times decreased, no more packet loss within my network. Quite bizarre..

[FurryNutz]

Interesting...something on the printer isn't configured right.