IGNITION Design Labs Portal


 * • 1733 Mbps - 4SS 5GHz 802.11ac (80MHz chan.),
 * • 450 Mbps - 3SS 2.4GHz 802.11n (40MHz chan.) = 2200 Mbps class



"SAP102 V1.2A" is silkscreened on the board in the FCC photos.
 * Model name might be Portal-PCW-110-COM


 * Ignition Design Labs Portal Reviewed on SmallNetBuilder
 * Monitor: Contains a Mini PCIe module with the following chips:
 * QCA QCA9887 (1x1 Dual-Band MIMO) 802.11abgn/ac
 * QCA QCA4531 (2x2 2.4GHz) 802.11b/g/n WiSoC
 * (QCA9531 on some revisions)
 * Winbond W971GG6SB-25 128MB RAM
 * Winbond W25Q128FVPQ 16MB Flash
 * CSR CSR8811 Bluetooth 4.1 SoC

"The empty connector between the two radios holds Portal's 'secret sauce' module (my term, not IDL's).
 * One of the photos in the FCC internal pictures file identifies this module as '2.4G/BT/BLE Module',
 * but it's much more than that.

The composite photo below shows both sides of the board, which are packed with interesting goodies.
 * In addition to a CSR8811 Bluetooth 4.1 SoC, it also holds the Qualcomm dual-band monitor radio and
 * dedicated Qualcomm "SpectrumBoost" co-processor that enables Portal's 'zero-wait' DFS switching."

Software
Portal device software was build using OpenWRT 15 chaos calmer (using GPLv2 license). The device was released but manufacturer never released the source code of its product (according to GPLv2 you need to release your product with the sources using GPLv2 license if you decide to release it and you have based on GPLv2 product to create your release).

Ingition Labs engineers removed several key packages from the product (probably to secure it and slim it down). It still has telnetd (not started by default) and ssh/dropbear (running but manufacturer has not revealed the password).

Device is meant to be configured using dedicated applications for android and iPhone. Applications are still being updated.

Once you gain root privileges on the device, it is a fully functional OpenWRT 15 Chaos Calmer box.

Logs
Device has dedicated web page with "support" tab allowing logs gathering and storing it onto a connected USB storage. Logs are stored in encrypted form meant for the support team only:

openssl enc -aes-256-cbc -in /tmp/logread_$logname.tar -out /mnt/usb-.../portal_log/logread_$logname.tar.en -pass pass:K5x48vZ3`