Fortinet FortiAP-210B (FAP-210B)
From TechInfoDepot
Jump to navigationJump to search
| abgn (AN600) | |
|---|---|
| 300Mbps Wireless Access Point | |
 | |
| WikiDevi.wi-cat.ru | Fortinet FortiAP-210B (FAP-210B) |
| 3rd Party Firmware | |
| dd-wrt | Status Unknown |
| OpenWrt | Supported |
| Tomato any flavor | Incompatible |
| Gargoyle | Status Unknown |
| Platform | |
| Brand • Model • Rev | Fortinet FortiAP-210B |
| Model Part Number | FAP-210B |
| FCC ID | TVE-220103 |
| IC ID | 7280B-220103 |
| Type | access point |
CPU1  | Atheros AR7161 |
| CPU1 Type | MIPS 24K |
| CPU1 Speed | 680 MHz 32-bit |
| Flash1 Chip | Macronix Model? |
| Flash1 Size | ? MiB |
| RAM1 Size | ? MiB |
| RAM1 Chip | SK hynix Model? x 2 |
| ETH chip1 | Atheros AR7161 |
| ETH chip2 | Atheros Model? |
| Ethernet Port Count | 1-1GbE-LAN |
| Wired Standard | IEEE 802.3i/3u/3ab |
| Expansion IF types | USB 2.0 |
| USB ports | 1 |
| USB Hub Compatible | Untested |
| Power | 12 VDC, 1.5 A |
| Connector type | barrel |
| Serial Port (UART) | yes, internal, 4-pin header, 3.3V TTL, console port |
|
| |
|
| |
| Other | |
|
Default IP address: 192.168.1.2 | |
| Manuf/OEM/ODM | Gemtek WAPA-250N |
| 3rd Party Firmware Support |
OpenWrt • (List | Dev | DLs) |
| Retail | |
| FCC approval date | 18 October 2010 |
| UPC |
700112949890 (UPC DB, On eBay) |
| ASIN |
B008XNDMI8  |
| Country of manuf | China |
| Radio 1 | |
| Chip1 | Atheros AR9220 |
| Wireless interface OUI | 00:09:0F |
| Antenna Connector Type | U.FL |
| MIMO status | 2x2:2 |
| Wireless Standard | IEEE 802.11a/b/g/n |
| 802.11n | up to 300 Mbps |
| 802.11g | up to 54 Mbps |
| 802.11b | up to 11 Mbps |
| 802.11a | up to 54 Mbps |
| WiFi Operating Frequency | 2.4 or 5 GHz |
For a list of all currently documented Atheros (QCA) chipsets with specifications, see Atheros.
For a list of all currently documented Fortinet devices with specifications, see Fortinet.
Overview
"WAPA-250N_V01" and "ESX-X00-9701R" is silkscreened on the board in the FCC photos.
- AR7161 is presumably used by this device
The OUI used (00:09:0F [Fortinet]) is per the FCC EUT's MAC label.
Flashing
 | NOTE: During configuration or flashing a device, the only things that should be hooked to the device is the computer and power. |
Flashing OpenWrt
Target: ath79
Subtarget: generic
Package architecture: mips_24kc
Supported Since Commit
Support started version: 24.10.0
Current supported version: 25.12.0
Subtarget: generic
Package architecture: mips_24kc
Supported Since Commit
Support started version: 24.10.0
Current supported version: 25.12.0
WLAN Hardware: Atheros AR9220, Atheros AR9223
Installation method(s):
see git-commit
Recovery method(s):
see git-commit
Installation method(s):
see git-commit
Recovery method(s):
see git-commit
| git • >> |
|---|
ath79: support Fortinet FAP-220-B
Fortinet FAP-220-B is a dual-radio, dual-band 802.11n enterprise managed
access point with PoE input and single gigabit Ethernet interface.
Hardware highlights:
Power: 802.3af PoE input on Ethernet port, +12V input on 5.5/2.1mm DC jack.
SoC: Atheros AR7161 (MIPS 24kc at 680MHz)
RAM: 64MB DDR400
Flash: 16MB SPI-NOR
Wi-Fi 1: Atheros AR9220 2T2R 802.11abgn (dual-band)
Wi-Fi 2: Atheros AR9223 2T2R 802.11bgn (single-band)
Ethernet: Atheros AR8021 single gigabit Phy (RGMII)
Console: External RS232 port using Cisco 8P8C connector (9600-8-N-1)
USB: Single USB 2.0 host port
LEDs: Power (single colour, green), Wi-Fi 1, Wi-Fi 2, Ethernet, Mode, Status
(dual-colour, green and yellow)
Buttons: reset button hidden in bottom grill,
in the top row, 2nd column from the right.
Label MAC address: eth0
FCC ID: TVE-220102
Serial port pinout:
3 - TxD
4 - GND
6 - RxD
Installation: The same methods apply as for already supported FAP-221-B.
For both methods, a backup of flash partitions is recommended, as stock firmware
is not freely available on the internet.
(a) Using factory image:
1. Connect console cable to the console port
2. Connect Ethernet interface to your PC
3. Start preferred terminal at 9600-8-N-1
4. Have a TFTP server running on the PC.
5. Put the "factory" image in TFTP root
6. Power on the device
7. Break boot sequence by pressing "Ctrl+C"
8. Press "G". The console will ask you for device IP, server IP, and filename.
Enter them appropriately.
The defaults are:
Server IP: 192.168.1.1 # Update accordingly
Device IP: 192.168.1.2 # Update accordingly
Image file: image.out # Use for example: openwrt-ath79-generic-fortinet_fap-220-b-squashfs-factory.bin
9. The device will load the firmware over TFTP, and verify it. When
verification passes, press "D" to continue installation. The device
will reboot on completion.
(b) Using initramfs + sysupgrade
1. Connect console cable to the console port
2. Connect Ethernet interface to your PC
3. Start preferred terminal at 9600-8-N-1
4. Have a TFTP server running on the PC.
5. Put the "initramfs" image in TFTP root
6. Power on the device.
7. Break boot sequence by pressing "Ctrl+C"
8. Enter hidden U-boot shell by pressing "K". The password is literal "1".
9. Load the initramfs over TFTP:
> setenv serverip 192.168.1.1 # Your PC IP
> setenv ipaddr 192.168.1.22 # Device IP, both have to share a subnet.
> tftpboot 81000000 openwrt-ath79-generic-fortinet_fap-220-b-initramfs-kernel.bin
> bootm 81000000
10. (Optional) Copy over contents of at least "fwconcat0", "loader", and "fwconcat1"
partitions, to allow restoring factory firmware in future:
# cat /dev/mtd1 > /tmp/mtd1_fwconcat0.bin
# cat /dev/mtd2 > /tmp/mtd2_loader.bin
# cat /dev/mtd3 > /tmp/mtd3_fwconcat1.bin
and then SCP them over to safety at your PC.
11. When the device boots, copy over the sysupgrade image, and execute
normal upgrade:
# sysupgrade openwrt-ath79-generic-fortinet_fap-220-b-squashfs-sysupgrade.bin
Return to stock firmware:
1. Boot initramfs image as per initial installation up to point 9
2. Copy over the previously backed up contents over network
3. Write the backed up contents back:
# mtd write /tmp/mtd1_fwconcat0.bin fwconcat0
# mtd write /tmp/mtd2_loader.bin loader
# mtd write /tmp/mtd3_fwconcat1.bin fwconcat1
4. Erase the reserved partition:
# mtd erase reserved
5. Reboot the device
Quirks and known issues:
- The power LED blinking pattern is disrupted during boot, probably due
to very slow serial console, which prints a lot during boot compared
to stock FW.
- "mac-address-ascii" device tree binding cannot yet be used for address
stored in U-boot partition, because it expects the colons as delimiters,
which this address lacks. Addresses found in ART partition are used
instead.
- Due to using kmod-owl-loader, the device will lack wireless interfaces
while in initramfs, unless you compile it in.
- The device heats up A LOT on the bottom, even when idle. It even
contains a warning sticker there.
- Stock firmware uses a fully read-write filesystem for its rootfs.
- Stock firmware loads a lot of USB-serial converter drivers for use
with built-in host, probably meant for hosting modem devices.
- U-boot build of the device is stripped of all branding, despite that
evidence of it (obviously) being U-boot can be found in the binary.
- The user can break into hidden U-boot shell using key "K" after
breaking boot sequence. The password is "1" (without quotes).
- Telnet is available by default, with login "admin", without password.
The same is true for serial console, both drop straight to the Busybox
shell.
- The web interface drops to the login page again, after successfull
login.
- Whole image authentication boils down to comparing a device ID against
one stored in U-boot.
- And this device is apparently made by a security company.
Big thanks for Michael Pratt for providing support for FAP-221-B, which
shares the entirety of image configuration with this device, this saved
me a ton of work.
|
Categories:
- Fortinet
- Embedded system/access point
- Embedded System Atheros
- Embedded System AR7161
- Atheros
- Embedded System MIPS 24K
- Embedded System
- Manuf Gemtek
- OpenWrt Supported
- Embedded System AR9220
- Has Mimo Status
- Embedded System IEEE 802.11a/b/g/n
- Single-Radio Wireless Embedded System
- Wireless Embedded System
- Dual-Band
- English Documentation
