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 22:30] – [Model Overview] 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. | ||
| The recovery also does not have the minimum size requirement, | The recovery also does not have the minimum size requirement, | ||
| + | |||
| + | |||
| + | === Image header format === | ||
| + | < | ||
| + | struct wrgg03_header { | ||
| + | char signature[32]; | ||
| + | uint32_t magic1; | ||
| + | uint32_t magic2; | ||
| + | char version[16]; | ||
| + | char model[16]; | ||
| + | uint32_t flag[2]; | ||
| + | uint32_t reserve[2]; | ||
| + | char buildno[16]; | ||
| + | uint32_t size; | ||
| + | uint32_t offset; | ||
| + | char devname[32]; | ||
| + | char digest[16]; | ||
| + | } | ||
| + | </ | ||
| + | In the wrgg03 image header, there is a 32 bit field called flags at 0x48, which is currently not set (i.e. remains zero) by mkwrggimg. For most devices, this is zero, however few older devices (DAP-2360, DAP-2553, DAP-2590) have the value set to 1. | ||
| + | This field can be used by the manufacturer to release firmware updates that would introduce changes which do not allow for downgrading back to previous versions: While checking the header, the web-based updater will verify the value of this field to be the same or higher than the firmware that is currently installed. If any of the forementioned devices shall be supported, the option to set this flag to 1 needs to be introduced to mkwrggimg, [[https:// | ||