Print

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

[igtoth]

Hi just upgraded my DAP-1360 H/W: B1 from original 2.10EN to 2.14. After that WIFI don't work anymore. And I can't find 2.10EN download file to rollback firmware.

[FurryNutz]

Link>Welcome!

• What Hardware version is your DAP? Look at the sticker under the DAP.
• Link>What Firmware version is currently loaded? Found on the DAPs web page under status.
• What region are you located?

How are you using the DAP? AP or extender?

Is there a main host router?

Follow this process to do any FW updates:
Link> >FW Update Process

[igtoth]

• What Hardware version is your DAP? Look at the sticker under the DAP.

Model: DAP-1360, H/W: B1

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

Hardware Version: B1  Firmware Version: 2.14

• What region are you located?

Brazil

How are you using the DAP? AP or extender?
Wireless client

Is there a main host router?
Yes, ASUS GT-AC5300


I downgraded firmware to 2.11 (still same issue), upgraded again to 2.14 (still same issue).

I have another DAP-1360 working fine with "2.10EN" firmware version.

Both were working ok, just first one stop working after firmware upgrade.

[GreenBay42]

Try resetting and set up from scratch.

[FurryNutz]

Was a factory reset performed after applying the FW update then set up from scratch?

[igtoth]

Try resetting and set up from scratch.

I did that, same results

[igtoth]

Was a factory reset performed after applying the FW update then set up from scratch?

yeap, same results...

[igtoth]

Wifi LED not turning on...


LOGs:
Dec 31 16:27:08   br0: port 3(wlan0) entering disabled state
Dec 31 16:27:11   br0: port 2(eth1) entering disabled state
Dec 31 16:27:11   br0: port 1(eth0) entering disabled state
Dec 31 16:27:11   device eth0 left promiscuous mode
Dec 31 16:27:11   br0: port 1(eth0) entering disabled state
Dec 31 16:27:11   device eth1 left promiscuous mode
Dec 31 16:27:11   br0: port 2(eth1) entering disabled state
Dec 31 16:27:12   device wlan0 left promiscuous mode
Dec 31 16:27:12   br0: port 3(wlan0) entering disabled state
Dec 31 16:27:17   device eth0 entered promiscuous mode
Dec 31 16:27:18   device eth1 entered promiscuous mode
Dec 31 16:27:18   device wlan0 entered promiscuous mode
Dec 31 16:27:19   fw_version: 7030(48.30), fw_EMEM_len: 49616, fw_IMEM_len: 43016, fw_DMEM_len: 48
Dec 31 16:27:23   br0: port 3(wlan0) entering learning state
Dec 31 16:27:23   br0: port 2(eth1) entering learning state
Dec 31 16:27:23   br0: port 1(eth0) entering learning state
Dec 31 16:27:23   br0: topology change detected, propagating
Dec 31 16:27:23   br0: port 3(wlan0) entering forwarding state
Dec 31 16:27:23   br0: topology change detected, propagating
Dec 31 16:27:23   br0: port 2(eth1) entering forwarding state
Dec 31 16:27:23   br0: topology change detected, propagating
Dec 31 16:27:23   br0: port 1(eth0) entering forwarding state
Dec 31 16:27:23   br0: port 3(wlan0) entering disabled state
Dec 31 16:27:23   br0: port 2(eth1) entering disabled state
Dec 31 16:27:23   br0: port 1(eth0) entering disabled state

[FurryNutz]

How is the main host router configured on 2.4ghz?

Can you temporarily disable WPA on the 2.4Ghz radio on the main host router and see if the DAP connects? Then test with WPA and TPIK set...

[GreenBay42]

How are you setting it up? WPS or are you logging into the web UI?

Is the 1360 near your router or in the same spot as it was before?

The 2.10 firmware can be found at http://tsd.dlink.com.tw/  it is labeled 2.10 WW

[igtoth]

How is the main host router configured on 2.4ghz?

Can you temporarily disable WPA on the 2.4Ghz radio on the main host router and see if the DAP connects? Then test with WPA and TPIK set...

yes if you can explain why, it was working before w/ the topology I have now. Also, the other DAP is working fine with the original fw (which I can't find anywhere in the internet to download).

[FurryNutz]

Possible new FW has some security fixes or implementations that could be a problem. Trying with out security would be one step, then try with WPA and TPIK to see if it connects, then try WPA2 and AES to see as well...

If it fails at any configuration, there would be a problem between the new FW and your main host router. D-link will need to review this...

[igtoth]

How are you setting it up? WPS or are you logging into the web UI?

Is the 1360 near your router or in the same spot as it was before?

The 2.10 firmware can be found at http://tsd.dlink.com.tw/  it is labeled 2.10 WW

[igtoth]

How is the main host router configured on 2.4ghz?

Can you temporarily disable WPA on the 2.4Ghz radio on the main host router and see if the DAP connects? Then test with WPA and TPIK set...

same results...

[igtoth]

More logs:

Jan 1 00:00:23   Linux version 2.6.19 (root@brent-ubuntu) (gcc version 3.4.6-1.3.6) #2090 Mon Aug 13 15:09:42 CST 2012
Jan 1 00:00:23   CPU revision is: 0000ff00
Jan 1 00:00:23   Determined physical RAM map:
Jan 1 00:00:23   memory: 02000000 @ 00000000 (usable)
Jan 1 00:00:23   User-defined physical RAM map:
Jan 1 00:00:23   memory: 02000000 @ 00000000 (usable)
Jan 1 00:00:23   On node 0 totalpages: 8192
Jan 1 00:00:23   DMA zone: 64 pages used for memmap
Jan 1 00:00:23   DMA zone: 0 pages reserved
Jan 1 00:00:23   DMA zone: 8128 pages, LIFO batch:0
Jan 1 00:00:23   Normal zone: 0 pages used for memmap
Jan 1 00:00:23   IPv6 over IPv4 tunneling driver
Jan 1 00:00:23   NET: Registered protocol family 17
Jan 1 00:00:23   VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 00:00:23   Freeing unused kernel memory: 136k freed
Jan 1 00:00:23   mount /proc file system ok!
Jan 1 00:00:23   SQUASHFS error: Can't find a SQUASHFS superblock on mtdblock2
Jan 1 00:00:23   mount /lang file system fail! error code=-22
Jan 1 00:00:23   mount /var file system ok!
Jan 1 00:00:23   device eth0 entered promiscuous mode
Jan 1 00:00:23   device eth1 entered promiscuous mode
Jan 1 00:00:23   device wlan0 entered promiscuous mode
Jan 1 00:00:25   write RF 0 offset 0x30 val [0x0300], read back [0x0300]
Jan 1 00:00:29   eth1: no IPv6 routers present
Nov 16 17:17:46   br0: no IPv6 routers present