D-Link Range Extenders > DAP-1860

Devices seen but sometimes not bridged

<< < (2/3) > >>

GreenBay42:
This device does not have a DHCP server. The DHCP from the router it is connected to will pass through to the wireless clients connecting to the extender.

hchung:
Hi, so after a few weeks of playing around when the DAP-1860 doesn't quite work right, here's my notes:

1) If there's nothing attached via WiFi, the first device that connects tends to get DHCP bridged through the ethernet interface with no problem. And it is oh so fast!

2) If another device attaches to the DAP-1860, often the DAP-1860 will fail to bridge that device to the ethernet backhaul. The devices will see the DAP-1860 itself, as well as any other device on the WiFi segment if you manually assign an IP address to the device. The DAP-1860 will also see the device too and display the 169.229.X.X address too. But the device cannot talk to anything on the ethernet segment.

3) If a device stays connected via WiFi, after a while, maybe 5-10 minutes, the DAP-1860 will usually notice the device and start bridging it to ethernet backhaul. If that happens life is good. If it was connected via static IP, then switching to DHCP works too.

4) Many devices (especially smartphones) don't like staying on a WiFi network which isn't giving a lease. So connecting Android and iOS devices when the DAP-1860 isn't bridging it is difficult because the device won't wait for bridging to magically start, it'll just go off and select another network.

Is there anything I can do, or any engineer I can reach out to, in order to get help to make a DAP-1860 recognize new devices on the WiFI segment faster?

FurryNutz:
Any status on this?
Have you contacted D-Link support about this?


--- Quote from: hchung on May 17, 2018, 11:20:08 PM ---Hi, so after a few weeks of playing around when the DAP-1860 doesn't quite work right, here's my notes:

1) If there's nothing attached via WiFi, the first device that connects tends to get DHCP bridged through the ethernet interface with no problem. And it is oh so fast!

2) If another device attaches to the DAP-1860, often the DAP-1860 will fail to bridge that device to the ethernet backhaul. The devices will see the DAP-1860 itself, as well as any other device on the WiFi segment if you manually assign an IP address to the device. The DAP-1860 will also see the device too and display the 169.229.X.X address too. But the device cannot talk to anything on the ethernet segment.

3) If a device stays connected via WiFi, after a while, maybe 5-10 minutes, the DAP-1860 will usually notice the device and start bridging it to ethernet backhaul. If that happens life is good. If it was connected via static IP, then switching to DHCP works too.

4) Many devices (especially smartphones) don't like staying on a WiFi network which isn't giving a lease. So connecting Android and iOS devices when the DAP-1860 isn't bridging it is difficult because the device won't wait for bridging to magically start, it'll just go off and select another network.

Is there anything I can do, or any engineer I can reach out to, in order to get help to make a DAP-1860 recognize new devices on the WiFI segment faster?

--- End quote ---

hchung:
Sorry, not yet, I was out of town for a while and just got back. I'll send an email to support now and see what happens.

hchung:
Support said to install firmware V1.04B01, released at the end of June.
I'll give it a shot and see what happens.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version