Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:d-link:d-link_dap_series_of_business_access_points [2021/01/20 23:04] – add wrgg03 flag field description s_2 | toh:d-link:d-link_dap_series_of_business_access_points [2022/07/17 17:58] – [Model Overview] Add further devices by Alpha Networks s_2 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| ==== Model Overview ==== | ==== Model Overview ==== | ||
| - | ^ Model ^ Wireless | + | ^ Model ^ Wireless |
| - | | [[toh: | + | | [[toh: |
| - | | [[toh: | + | | [[toh: |
| - | | [[toh: | + | | [[toh: |
| - | | [[toh: | + | | [[toh: |
| - | | [[toh: | + | | [[toh: |
| - | | [[toh: | + | | DAP-2682* |
| - | | DAP-3662 | + | | [[toh: |
| + | | [[toh: | ||
| + | | [[toh: | ||
| + | | DAP-X2810* | ||
| + | | DAP-X2850* | ||
| + | |||
| + | *not yet supported | ||
| [[toh: | [[toh: | ||
| Line 22: | Line 28: | ||
| ==== Power Supply ==== | ==== Power Supply ==== | ||
| - | All devices can be supplied via 802.11af PoE (.at for DAP-2680 and DAP-2695). | + | All devices can be supplied via 802.3af PoE (.3at for DAP-2680 and DAP-2695). |
| - | Alternatively, | + | Alternatively, |
| DAP-2695 can be powered from a 48V supply, using a special plug with center pin, the same as the PSU that comes with the DPE-101GI injector. | DAP-2695 can be powered from a 48V supply, using a special plug with center pin, the same as the PSU that comes with the DPE-101GI injector. | ||
| Line 58: | Line 64: | ||
| Factory image can be flashed via the regular update procedure from the ' | Factory image can be flashed via the regular update procedure from the ' | ||
| - | After initially flashing the device to OpenWRT, flash a sysupgrade image again. This is not required, but allows you to use more space from the flash. See the next section for more technical details. | + | After initially flashing the device to OpenWrt, flash a sysupgrade image again. This is not required, but allows you to use more space from the flash. See the next section for more technical details. |
| ==== Factory Images ==== | ==== Factory Images ==== | ||
| Line 69: | Line 75: | ||
| Thus, the factory image contains the kernel padded to 6 MiB + squashfs, so that jffs2 will always be outside of the memory region covered by the wrgg checksum. | Thus, the factory image contains the kernel padded to 6 MiB + squashfs, so that jffs2 will always be outside of the memory region covered by the wrgg checksum. | ||
| - | As soon as the device is running | + | As soon as the device is running |
| So, when more flash space is required, a sysupgrade image can be flashed right after factory, to allow for using of all the available flash memory. | So, when more flash space is required, a sysupgrade image can be flashed right after factory, to allow for using of all the available flash memory. | ||