• February 24, 2018, 09:59:07 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Wi-Fi / DHCP issues; unable to connect, incorrect MAC address, bad handshakes  (Read 1588 times)

spn183

  • Level 1 Member
  • *
  • Posts: 2

I have a DCS-2630L-DA32 that has connectivity problems. My access point has reported authentication/handshake failures and cases where the client (camera) automatically drops itself from the network by request. I have numerous other wireless clients (phones, laptops, set top boxes, etc.) with absolutely zero issues on the same access point. It’s been connected to the same Wi-Fi network for months without issue. It just started to have problems within the past few days.

Basic info:

  • Firmware: 1.03.03
  • Hardware: A1
  • WAP: Cisco 2702i 802.11ac
  • 5GHz, channel 60, 20 MHz width, -55 dB.
  • No interference or other issues to speak of.
  • SSID is broadcast, only standard alphanumeric characters used for the SSID name and WPA2-PSK.

I have two Cisco SG300s in line between the WAP and my firewall. The firewall is a Supermicro box running pfSense 2.3.3-RELEASE, and is the DHCP server mentioned below.

I’ve updated the firmware to 1.03.03 and performed a factory reset, only configuring the wireless network settings to test. I’ve seen a number of different results when trying to connect:

Authentication/handshake failure example:

Code: [Select]
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: Overwrote hwidb address f07f.0681.13c0 with MBSSID address f07f.0681.13c0
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: sending eapol to client on BSSID f07f.0681.13c0
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: [count = 3] Sent PTK msg 3 to client, no timer set
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: [count = 3] Handshake msg to client, timer set: timeout 100 ms
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: Executing Action [state: WPAV2_PTK_MSG4_WAIT, event: TIMEOUT] for client
Aug 25 18:07:25: (0000.0000.0000): dot11_aaa: 4-way Handshake failure for client

I’ve also seen some disassociation requests after successful authentication and association:

Code: [Select]
Aug 25 18:45:34: %DOT11-6-ASSOC: Interface Dot11Radio1, Station   b2c5.5428.da32 Associated KEY_MGMT[WPAv2 PSK]
Aug 25 18:45:34: (0000.0000.0000): dot11_aaa: client Associated
Aug 25 18:45:34: (0000.0000.0000): dot11_aaa: accounting not enabled for this client
Aug 25 18:45:34: (0000.0000.0000): dot11_mgmt: bss client assoc/reassoc updated stats curr_assoc 3 cur_bss_assoc 3 cur_rptrs 0 cur_bss_rptrs 0
Aug 25 18:45:34: (0000.0000.0000): dot11_mgmt:lwapp_session_timeout not starting for this client
Aug 25 18:45:34: (0000.0000.0000): dot11_mgmt: decrementing reference count(previous ref=3, sta_ptr=0x9BE61DC)
Aug 25 18:45:43: (0000.0000.0000): dot11_driver: Dot11Radio1: Rx Deauth for this client
Aug 25 18:45:43: (0000.0000.0000): dot11_mgmt: receive de-auth msg from station, reason 768
Aug 25 18:45:43: (0000.0000.0000): dot11_mgmt: incrementing reference count (previous ref=2, sta_ptr=0x9BE61DC)
Aug 25 18:45:43: (b2c5.5428.da32): SM: ---Open Authentication 0x9BE61DC: Delete (2)SM:    Assoc (2) --> Init (0)
Aug 25 18:45:43: (0000.0000.0000): dot11_aaa: Received disassociation notice for client
Aug 25 18:45:43: dot11_dot1x_gtk_update_on_disassociate: Recieved gtk update notice due to disconnect for b2c5.5428.da32 on vlan 10
Aug 25 18:45:43: (0000.0000.0000): dot11_dot1x: Recieved gtk update notice due to disconnect for client on vlan 10
Aug 25 18:45:43: (0000.0000.0000): dot11_aaa: Updating aaa attributes for user
Aug 25 18:45:43: (0000.0000.0000): dot11_aaa: AAA Client (b2c5.5428.da32, A591654) is deleted
Aug 25 18:45:43: (0000.0000.0000): dot11_aaa: Sending abort request for client to local Authenticator
Aug 25 18:45:43: b2c5.5428.da32: dot11_auth: Received abort request for client No client entry to abort for application 0x1
Aug 25 18:45:43: (0000.0000.0000): dot11_mgmt: verifying station is infra client, null sta_ptr 0x9BE61DC or sta_ptr->assoc_ext_tlv.elem_id 0x0
Aug 25 18:45:43: (0000.0000.0000): dot11_mgmt: bss client disassoc updated stats curr_assoc 2 cur_bss_assoc 2 cur_rptrs 0 cur_bss_rptrs 0
Aug 25 18:45:43: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station b2c5.5428.da32 Reason: Sending station has left the BSS

Sometimes this happens when a client can’t obtain an IP address, so I checked my DHCP server and found two interesting things:

Code: [Select]
Aug 25 18:40:15 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:16 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:18 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:18 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:21 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:21 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:24 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:40:24 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:35 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:36 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:38 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:38 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:41 dhcpd DHCPDISCOVER from b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10
Aug 25 18:45:41 dhcpd DHCPOFFER on 10.0.10.30 to b2:c5:54:08:da:32 (DCS-2630L) via igb1_vlan10

  • The MAC address of the camera per the AP is b2:c5:54:28:da:32, which is also what is printed on the label on the bottom of the camera’s stand, in my switch’s CAM table, etc. However, as seen above, the DHCP server receives a request from b2:c5:54:08:da:32. Notice the fourth octet has shifted from 28 to 08. Because the camera is set up via Wi-Fi, I assume it has two Wi-Fi radios so that it can maintain both the setup network as well as the normal user network, but that does not explain why my AP sees one client MAC while a different one is used for the DHCP request. You also usually see the last couple of octet changes in this cases, not one in the middle.
  • The DHCP server offers 10.0.10.30, but the camera does not appear to accept it. At this point it de-authenticates from the AP because it thinks it wasn’t provided an IP. This could be because of the MAC address mismatch. If it uses an incorrect MAC address in the outbound L2 frame, it would never receive the offer sent by the DHCP server.

Side note: I had a DHCP reservation set up for the correct MAC, which it couldn’t pick up because the incorrect MAC was used in the DHCPDISCOVER. I’ve since removed the reservation for testing purposes.
 
For a period of time, the camera didn’t appear to try and connect at all. I restored it to the configuration backup that I saved before I did a factory reset and it suddenly started to work. You can see the tail end of a successful association as well as a successful DHCP lease:

Code: [Select]
Aug 25 19:11:41: %DOT11-6-ASSOC: Interface Dot11Radio1, Station   b2c5.5428.da32 Associated KEY_MGMT[WPAv2 PSK]
Aug 25 19:11:41: (0000.0000.0000): dot11_aaa: client Associated
Aug 25 19:11:41: (0000.0000.0000): dot11_aaa: accounting not enabled for this client
Aug 25 19:11:41: (0000.0000.0000): dot11_mgmt: bss client assoc/reassoc updated stats curr_assoc 3 cur_bss_assoc 3 cur_rptrs 0 cur_bss_rptrs 0
Aug 25 19:11:41: (0000.0000.0000): dot11_mgmt:lwapp_session_timeout not starting for this client
Aug 25 19:11:41: (0000.0000.0000): dot11_mgmt: decrementing reference count(previous ref=3, sta_ptr=0x9BE67F4)
Aug 25 19:11:43: (0000.0000.0000): dot11_mgmt: Updating the client IP (10.0.10.23) to the controller

Code: [Select]
Aug 25 19:11:16 dhcpd DHCPDISCOVER from b2:c5:54:28:da:32 via igb1_vlan10
Aug 25 19:11:17 dhcpd DHCPOFFER on 10.0.10.23 to b2:c5:54:28:da:32 (DC2) via igb1_vlan10
Aug 25 19:11:41 dhcpd DHCPDISCOVER from b2:c5:54:28:da:32 (DC2) via igb1_vlan10
Aug 25 19:11:41 dhcpd DHCPOFFER on 10.0.10.23 to b2:c5:54:28:da:32 (DC2) via igb1_vlan10
Aug 25 19:11:41 dhcpd DHCPREQUEST for 10.0.10.23 (10.0.10.1) from b2:c5:54:28:da:32 (DC2) via igb1_vlan10
Aug 25 19:11:41 dhcpd DHCPACK on 10.0.10.23 to b2:c5:54:28:da:32 (DC2) via igb1_vlan10

Note that the MAC address has returned to normal.

Today the camera couldn’t connect again. I had another look and found the same handshake issues and successful associations without obtaining a DHCP lease - in this case, no DHCPDISCOVER was sent by the camera at all. It randomly connected after a few attempts with no real explanation. At this point the only constant is that if you reboot it enough times it will eventually work.

I reached out to support yesterday, but did not receive a confirmation e-mail or a response. I purchased the camera on March 25, 2016, so I’m within the one year hardware warranty. Before I seek a replacement or refund, I wanted to reach out to other owners to see if they’ve experienced similar issues, or on the off-chance that someone above the level of consumer support at D-Link may see this and be willing to work with me to resolve it.

If you made it this far, thanks. I know this was a wall.

I like D-Link's cameras; for the price and feature set I don't think they can be beat. In particular I appreciate the ability to configure the camera locally rather than via an app or another controller. I'm not above picking up a DCS-2210L or another similar model. I don't think I'll ever purchase a Wi-Fi only camera again - D-Link or not. I bought and returned a Samsung HD camera because it was a nightmare to operate. This 2630L has been reliable up until now.
« Last Edit: August 26, 2016, 07:33:59 PM by spn183 »
Logged

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2110


So - it sounds like this was working for a while...then completely broke down?

Is it the new F/W?

Did you upgrade anything else?

Logged

spn183

  • Level 1 Member
  • *
  • Posts: 2


So - it sounds like this was working for a while...then completely broke down?

Is it the new F/W?

Did you upgrade anything else?

Yes, it worked fine since purchase - March 2016. A few days ago I noticed I wasn't getting motion notification e-mails and I checked it out - no connection. I upgraded after the problem started; it's persisted through 1.02.02 (I think that's the last version I had) and 1.03.03.

Nothing else has been upgraded, touched, or otherwise molestered in the same time period.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 44593
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology

What wireless and security modes are you using on the WAP?
Logged
Cable:200mb/10Mb>Motorola MB7420>COVR3902>HP 24pt Gb Switch. 3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,865L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

Watcher

  • Level 2 Member
  • **
  • Posts: 25

I started getting the similar problem today.

Code: [Select]
Dec 10 11:28:54 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:54 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:28:57 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:57 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:28:59 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:59 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:02 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:29:02 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:03 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:03 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:32:58 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:32:58 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:25 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:25 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:27 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:27 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:31 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:31 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:37 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:37 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

MAC printed on the card is b0:c5:54:2e:67:2d.
It seems that MAC printed on the card is for 2.4GHz, while 5GHz MAC is different.
I had the camera working fine until this point on 5GHz with the MAC and IP assigned by DHCP above. The router has MAC filtering enabled with one address on 2.4GHz filter and the other on 5GHz.

Today, after surveying the neighbourhood, I decided to move to channel 52 from the over-crowded 36 and 44. At first the camera would not reconnect, broadcasting its internal SSID. It would ignore WPS. I connected to its network and manually reconfigured (10.255.255.1) the wireless to the same 5GHz net as before. After a few reboots the camera now connected, though with a lot of excessive DHCP querying. BUT. It's really slow. Barely loads interface and often times-out on the html page load.
I now tried to switch back to channel 36, but the camera is in a disgruntled mode - would not work.

Tried also disabling MAC filtering. No luck. The camera continues to bobard DHCP server with requests:

Code: [Select]
Dec 10 12:07:38 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:07:38 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:07:40 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:07:40 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:13:37 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:13:37 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:38 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:38 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:13:42 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:42 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:15:28 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:28 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:31 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:31 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:36 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:36 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:15:41 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:41 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

EDIT: Really frustrated. I must have spent a total of 5 days of my life at various points, trying to get this camera to work, and when it finally works, it's impossible to pinpoint what made it work. 960L, which shares the same "easy connect" idea, but was probably coded by a different team using a totally different code base connects fine, and keeps connection. The easiest camera to manage was the discontinued 2332L, where I could even specify a new SSID ahead of time, let the camera disconnect, change SSID on the router and would see the camera reconnect on the new SSID. 2630L cannot even connect to a visible broadcasted SSID! The only stable connection it has is on its own internal network, which is useless!

EDIT2: Did a factory reset (meaning that if I get it to connect to the network, I'll be spending another couple of hours reconfiguring all its settings from scratch). Still cannot consistently connect. Updated router's firmware. Still cannot connect, but now WPS fails too.

I am on the verge of starting to look for wide-angle alternatives to D-Link, But that would mean replacing my whole D-Link camera ecosystem.

EDIT3: connected to the camera's own SSID from mobile phone. Get presented witha useless mobile view on /m/.... Need to manually replace the URI with 10.255.255.1/eng/mainFrame.cgi?nav=Setup Will be trying to configure the cam from a browser on the mobile phone now.

EDIT4: Managed to get it to connect to the wireless router on the 2.4GHz interface with it B2:... MAC. Was I actually clearing the wrong MAC and B0:... was the one for 5GHz. Digging deeper...

On 2.4GHz:
Code: [Select]
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPDISCOVER(br0) b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPOFFER(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPDISCOVER(br0) b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPOFFER(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPREQUEST(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPACK(br0) 192.168.62.107 b2:c5:54:0e:67:2d DCS-2630L
Dec 10 13:52:09 dnsmasq-dhcp[1310]: DHCPREQUEST(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:09 dnsmasq-dhcp[1310]: DHCPACK(br0) 192.168.62.107 b2:c5:54:0e:67:2d DCS-2630L

In any case, the MAC on the printed card starts with B0:...

EDIT5: Oh, there is another difference: b2:c5:54:0e:67:2d vs b0:c5:54:2e:67:2d Back to the drawing board

EDIT6: Connected to 5GHz IF I don't assign a specific IP in the DHCP table. When i try to assign the previous .127 address, the camera starts spamming DHCP server again, while timing out on the IP it receives
Code: [Select]
Dec 10 16:02:44 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:02:44 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:01 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:01 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:03 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:03 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:07 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:07 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:23 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:23 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:25 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:25 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:26 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:26 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:27 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:09:27 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:28 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:28 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:30 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:30 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:33 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:33 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:18 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:10:18 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:19 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:19 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:22 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:22 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:28 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:28 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:29 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:29 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:20:36 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:36 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:20:39 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:39 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:20:44 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:44 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:37 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:37 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:42 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:42 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:50 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:50 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:50:28 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:50:28 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:58:57 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:58:57 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:58:58 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:58:58 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:59:01 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:59:01 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

EDIT7: So, the camera actually has 3 MAC addresses:
B0:C5:54:2E:67:2D (printed on the card and in the Device Info tab)
B2:C5:54:2E:67:2D (5GHz broadcast)
B2:C5:54:0E:67:2D (2.4GHz broadcast)

EDIT8: Barely connected on 5GHz - droppingg in and out. But a new problem - the camera disappeared from the list in mydlink app, and I cannot add it back.

EDIT9: I think I will wrap up the second day of "quick" installation here.
« Last Edit: December 10, 2017, 08:42:53 AM by Watcher »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 44593
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology

  • Link>What Firmware version is currently loaded? Found on the DCSs web page under status.

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?
  • Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
  • Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.26 DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

I started getting the similar problem today.

Code: [Select]
Dec 10 11:28:54 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:54 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:28:57 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:57 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:28:59 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:28:59 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:02 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:29:02 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:03 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:29:03 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:32:58 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:32:58 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:33:01 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:25 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:25 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:27 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:27 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:31 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 11:36:31 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:34 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 11:36:37 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 11:36:37 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

MAC printed on the card is b0:c5:54:2e:67:2d.
It seems that MAC printed on the card is for 2.4GHz, while 5GHz MAC is different.
I had the camera working fine until this point on 5GHz with the MAC and IP assigned by DHCP above. The router has MAC filtering enabled with one address on 2.4GHz filter and the other on 5GHz.

Today, after surveying the neighbourhood, I decided to move to channel 52 from the over-crowded 36 and 44. At first the camera would not reconnect, broadcasting its internal SSID. It would ignore WPS. I connected to its network and manually reconfigured (10.255.255.1) the wireless to the same 5GHz net as before. After a few reboots the camera now connected, though with a lot of excessive DHCP querying. BUT. It's really slow. Barely loads interface and often times-out on the html page load.
I now tried to switch back to channel 36, but the camera is in a disgruntled mode - would not work.

Tried also disabling MAC filtering. No luck. The camera continues to bobard DHCP server with requests:

Code: [Select]
Dec 10 12:07:38 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:07:38 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:07:40 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:07:40 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:13:37 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:13:37 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:38 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:38 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:13:42 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:13:42 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:15:28 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:28 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:31 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:31 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:36 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:36 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:37 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 12:15:41 dnsmasq-dhcp[1165]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 12:15:41 dnsmasq-dhcp[1165]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

EDIT: Really frustrated. I must have spent a total of 5 days of my life at various points, trying to get this camera to work, and when it finally works, it's impossible to pinpoint what made it work. 960L, which shares the same "easy connect" idea, but was probably coded by a different team using a totally different code base connects fine, and keeps connection. The easiest camera to manage was the discontinued 2332L, where I could even specify a new SSID ahead of time, let the camera disconnect, change SSID on the router and would see the camera reconnect on the new SSID. 2630L cannot even connect to a visible broadcasted SSID! The only stable connection it has is on its own internal network, which is useless!

EDIT2: Did a factory reset (meaning that if I get it to connect to the network, I'll be spending another couple of hours reconfiguring all its settings from scratch). Still cannot consistently connect. Updated router's firmware. Still cannot connect, but now WPS fails too.

I am on the verge of starting to look for wide-angle alternatives to D-Link, But that would mean replacing my whole D-Link camera ecosystem.

EDIT3: connected to the camera's own SSID from mobile phone. Get presented witha useless mobile view on /m/.... Need to manually replace the URI with 10.255.255.1/eng/mainFrame.cgi?nav=Setup Will be trying to configure the cam from a browser on the mobile phone now.

EDIT4: Managed to get it to connect to the wireless router on the 2.4GHz interface with it B2:... MAC. Was I actually clearing the wrong MAC and B0:... was the one for 5GHz. Digging deeper...

On 2.4GHz:
Code: [Select]
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPDISCOVER(br0) b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPOFFER(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPDISCOVER(br0) b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPOFFER(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPREQUEST(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:06 dnsmasq-dhcp[1310]: DHCPACK(br0) 192.168.62.107 b2:c5:54:0e:67:2d DCS-2630L
Dec 10 13:52:09 dnsmasq-dhcp[1310]: DHCPREQUEST(br0) 192.168.62.107 b2:c5:54:0e:67:2d
Dec 10 13:52:09 dnsmasq-dhcp[1310]: DHCPACK(br0) 192.168.62.107 b2:c5:54:0e:67:2d DCS-2630L

In any case, the MAC on the printed card starts with B0:...

EDIT5: Oh, there is another difference: b2:c5:54:0e:67:2d vs b0:c5:54:2e:67:2d Back to the drawing board

EDIT6: Connected to 5GHz IF I don't assign a specific IP in the DHCP table. When i try to assign the previous .127 address, the camera starts spamming DHCP server again, while timing out on the IP it receives
Code: [Select]
Dec 10 16:02:44 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:02:44 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:01 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:01 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:03 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:03 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:07 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:07 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:23 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:23 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:25 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:03:25 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:26 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:03:26 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:27 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:09:27 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:28 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:28 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:30 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:30 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:09:33 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:09:33 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:18 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:10:18 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:19 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:19 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:22 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:22 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:28 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:28 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:29 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:29 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:10:37 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:20:36 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:36 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:20:39 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:39 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:20:44 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:20:44 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:37 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:37 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:42 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:42 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:23:50 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:23:50 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:30:05 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:50:28 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:50:28 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:50:31 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:58:57 dnsmasq-dhcp[4327]: DHCPDISCOVER(br0) b2:c5:54:2e:67:2d
Dec 10 16:58:57 dnsmasq-dhcp[4327]: DHCPOFFER(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:58:58 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:58:58 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home
Dec 10 16:59:01 dnsmasq-dhcp[4327]: DHCPREQUEST(br0) 192.168.62.127 b2:c5:54:2e:67:2d
Dec 10 16:59:01 dnsmasq-dhcp[4327]: DHCPACK(br0) 192.168.62.127 b2:c5:54:2e:67:2d DCS-2630L-Home

EDIT7: So, the camera actually has 3 MAC addresses:
B0:C5:54:2E:67:2D (printed on the card and in the Device Info tab)
B2:C5:54:2E:67:2D (5GHz broadcast)
B2:C5:54:0E:67:2D (2.4GHz broadcast)

EDIT8: Barely connected on 5GHz - droppingg in and out. But a new problem - the camera disappeared from the list in mydlink app, and I cannot add it back.

EDIT9: I think I will wrap up the second day of "quick" installation here.
Logged
Cable:200mb/10Mb>Motorola MB7420>COVR3902>HP 24pt Gb Switch. 3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,865L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

Watcher

  • Level 2 Member
  • **
  • Posts: 25

  • Link>What Firmware version is currently loaded? Found on the DCSs web page under status.

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?
  • Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
  • Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.26 DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

[snip]

Thanks for the answer.

I did another go at the quick configuration today:
1. Disable all MAC filters on the router
2. Place Mydlink app on the phone in a signed in state of adding a new camera right at the option of "I don't have WPS"
3. Factory reset and as the camera turned on, connect to its SSID from the phone
4. Run the add camera process from the app - camera got configured and I placed it on teh 2.4GHz network
5. Camera works at full speed - good 6Mbps feed in DCS-100 and very responsive web inteface
6. Enable MAC filtering on 2.4 GHz -> still full speed
7. From the Wireless setup, point the camera to the 5GHz network SSID -> still working fine.
8. Enable MAC filtering on 5GHz -> ground to a halt. No video fed and the Web UI loads slowly or time-outs.
9. Disable MAC filtering on 5GHz -> still slow.
10. Reboot the camera and as it powers on, connect to its internal SSID from the phone, then configure it to go back to 2.4GHz network using the phone browser to access the Wireless setup interface.
11. Camera runs fast again with full video feed and responsive gui.

It is strange, because I have DCS-960L on the same 5GHz network, as well as phone, pad and SmartTV streamer loitering there, and it's only DCS-2630L that has the problem with it.

I have a very small range of 8 addresses excluded from the DHCP pool, and I will try your suggestion (ironically, I went away from statically assigning IPs to the cameras a couple of years ago, opting for letting DHCP server assign a predefined address based on MAC).
I have ASUS RT-N66U router.
2.4 is N-only, 40MHz, Channel 1
5GHz is N-only, 40MHz, Channel 52 (the whole problem started when I switched from using channel 44, but now, I cannot get it to work even when switching back to 44)
And yes, the neighbourhood is quite congested - each house has its own router shipped with the TV box, using both 2.4HGz and 5GHz. On 5 GHz people only seem to use 36 and 44, while 2.4GHz is all over the place. There are about 15 visible networks.

EDIT: Static IP worked as expected, but did not help with the 5GHz problem. I am starting to think that the 5GHz radio on the camera is failing. After switching to 5GHz, the camera would briefly show in the routers log as "associated", and then would drop out. Connected to its SSID again, switched back to the 2.4GHz network, and it was up and running again.

So I am back to 2.4GHz and calling it quits. DCS-960L and 4-5 other devices will have more space on 5GHz for themselves.

What remains to be done, is to reconfigure the camera as it was before the factory resets. Tomorrow.
« Last Edit: December 11, 2017, 11:25:23 AM by Watcher »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 44593
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology

What Mfr and model is the main host router?

Do you need MAC Filtering for your cameras?
Logged
Cable:200mb/10Mb>Motorola MB7420>COVR3902>HP 24pt Gb Switch. 3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,865L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

Watcher

  • Level 2 Member
  • **
  • Posts: 25

What Mfr and model is the main host router?

Do you need MAC Filtering for your cameras?

Asus RT-N66U

I need MAC filtering on the router- not only cameras have access to it.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 44593
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology

What FW version to you have on the router? OEM or RMerlin?

Can you exclude the cameras from the MAC FILTER?
Logged
Cable:200mb/10Mb>Motorola MB7420>COVR3902>HP 24pt Gb Switch. 3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,865L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

Watcher

  • Level 2 Member
  • **
  • Posts: 25

What FW version to you have on the router? OEM or RMerlin?

Can you exclude the cameras from the MAC FILTER?

Merlin 380.68_4 (EDIT: upgraded to 380.69 just now, as changelog has some changes for my router)

When I exclude the camera from the list, it does not even connect in the "slow mode".
Definitely seems to be some disagreement between the 5GHz radio on the router and the camera. All else works, and the camera works fine on the 2.4GHz
« Last Edit: December 14, 2017, 11:09:48 AM by Watcher »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 44593
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology

Can you try this? Temporarily disable WPA on the 5Ghz radio. Don't use any mac filtering on the router for anything. See if the camera will connect to the 5Ghz radio. Re-enable WPA2 settings after testing.

I know Merlin has some issues with some recent builds in wireless. One version I experienced as 380.68 was a good solid built for a router I was demo'g. Something you could try and test with the camera if you want to try. I would test OEM FW as well and see if the camera experiences same issue.

Seems like this is a issue with FW and this model camera. Kinda hard to figure this one out.
Logged
Cable:200mb/10Mb>Motorola MB7420>COVR3902>HP 24pt Gb Switch. 3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,865L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting