WatchGuard Firebox T15 (MS1AE3)

From TechInfoDepot
Jump to navigationJump to search
WatchGuard Firebox T15
WikiDevi.wi-cat.ru WatchGuard Firebox T15 (MS1AE3)
3rd Party Firmware
dd-wrt Status Unknown
OpenWrt Supported
Tomato any flavor Incompatible
Gargoyle Status Unknown
Platform
BrandModelRev WatchGuard Firebox T15
Model Part Number MS1AE3
Board ID 7016A1393004
Type security appliance
CPU1 checkY Freescale (NXP) P1010
CPU1 Type Power QorIQ
CPU1 Speed 533 MHz
Flash1 Chip Macronix MX60LF8G18AC-TI
Flash1 Size 1 GiB 1,024 MiB <br />1,073,741,824 B <br />8,388,608 Kib <br />1,048,576 KiB <br />8,192 Mib <br /> (NAND)
Flash2 Chip Macronix MX25L8006EM2I-12G
Flash2 Size 1 MiB1,048,576 B <br />8,192 Kib <br />1,024 KiB <br />8 Mib <br />9.765625e-4 GiB <br /> (SPI)
RAM1 Size 1 GiB 1,024 MiB <br />1,073,741,824 B <br />8,388,608 Kib <br />1,048,576 KiB <br />8,192 Mib <br /> (DDR3)
RAM1 Chip ProMOS V73CBG04168RAJJ11 x 2
ETH chip1 Freescale (NXP) P1010
ETH chip2 Atheros AR8033
ETH chip3 Atheros AR8033
ETH chip4 Atheros AR8033
Ethernet Port Count 1-1GbE-WAN
2-1GbE-LAN
Wired Standard IEEE 802.3i/3u/3ab

Ethernet OUI: 00:90:7F (24 E, 18 W)

Stock bootloader U-Boot 2011.03
Stock FW OS Linux 3.12.19-rt30
Expansion IF types USB 2.0
USB ports 1
USB Hub Compatible Untested
Power 12 VDC, 1.25 A
Connector type barrel
5.5 mm (OD)
2.1 mm (ID)
9.5 mm (LEN)
Serial Port (UART) yes, console port, RJ45, (115200 8N1)

Flags:
RTC w/ battery, power switch, heatsink

Additional chips
2-Wire RTC;Seiko;S-35390A;;1;
Multichannel RS-232 Line Driver;TI;MA3232C;;1;
Trusted Platform Module;Atmel;AT97SC3204T;;1;
2A Bus Termination Regulator;Fitipower;FP6137E;;1;
30V 4.4A P-Channel MOSFET;Sinopower;SM3095;;2;
4 Output PCIe Gen 1/2 Synthesizer;Renesas;IDT5V41186;;1;

Other

Default IP address: 10.0.1.1
the IP 10.0.1.1 is used by 21 additional devices
of which 19 are WatchGuard devices
Default login user: admin
Default login password: readwrite
admin:readwrite credentials used by 25 additional devices
of which 25 are WatchGuard devices

Manuf/OEM/ODM Senao
3rd Party Firmware Support OpenWrt • (List | Dev | DLs)
Retail
Availability EoS
End of Life date 01 March 2022
(Est.) release date November 2017
ASIN B0777S7F1J
Country of manuf Taiwan

For a list of all currently documented Atheros (QCA) chipsets with specifications, see Atheros.
For a list of all currently documented Freescale (NXP) SoC's with specifications, see Freescale.

For a list of all currently documented WatchGuard devices with specifications, see WatchGuard.

Overview

Hardware specification

  • CPU: Freescale P1010 PowerPC (@533MHz)
  • Memory: 1GB (SDRAM) DDR3
  • Storage: 1MB SPI Flash, 1GB NAND Flash
  • Network: 3x Gigabit Ethernet ports
  • USB: 1x USB 2.0 ports
  • Power: 12V, 1.25A via barrel

Links of Interest

Hardware Guide  • Quick Start Guide

Flashing

Flashing OpenWrt

Target: mpc85xx
Subtarget: p1010
Package architecture: powerpc_8548
Supported Since Commit
Support started version: 25.12.0
Current supported version: 25.12.0
LAN Hardware: 3x Atheros AR8033 Phy
WLAN Comment: No WLAN
Installation method(s):
see git-commit
git • >>
mpc85xx: add support for Watchguard Firebox T10-W, T15(-W)
This commit adds support for the Watchguard Firebox models
T10-W, T15 and T15-W.

CPU:      Freescale P1010
RAM:      512MB (T10) / 1024MB (T15)
Flash:    1MB SPI-NOR, 512MB NAND (T10) / 1024MB NAND (T15)
WiFi:     802.11abgn 2T2R AR9582 based Mini-PCIe card (-W models only)
Ethernet: 3x GBE (via AR8033 PHY)
LEDs:     7x hard-wired (6x LAN, 1x Power)
          4x GPIO single-colored (Attn/Status/Mode/Failover)
          1x GPIO dual-colored (2.4/5G WiFi, -W models only)
Serial:   RJ45, Cisco pinout, 115200/8N1
Other:    Battery backed RTC
          Atmel TPM 1.2 chip (unsupported)

Based on 35f6d79, which introduced Watchguard Firebox T10 support.

The T10 and T15 are identical hardware, with the exception of the T15
having twice the flash and RAM size.

The T10-W and T15-W models have their Mini-PCIe slot populated with an ath9
(AR9582) based WiFi card. The slot is either unpopulated or empty for
non-WiFi models. All required drivers are present by default on the mpc85xx
target, so T10/T10-W resp. T15/T15-W can use the same OpenWrt image.

This commit also introduces the zImage loader from 7d768a9 to boot the
kernel. This is required, since the U-Boot version used in these devices
appears to have a hard limit of 16MB for the kernel size it can handle. The
current kernel size is around 17MB, though, due to kernel page alignment
required for memory protection.

Installation (replaces previous instructions for T10):

1. If the U-Boot password is known, proceed with step 2.

   If the U-Boot password is unknown, dump the NOR flash using a SPI
   programmer and patch the unknown password to a known one. You can use
   blocktrron's Python script:

   https://github.com/blocktrron/t10-uboot-patcher/

   This script will patch the password to '1234' (without quotes).

   Alternatively, you can search for the hashed password in the NOR dump
   yourself and overwrite it with a known one. The SHA1 hash is:

   E597301A1D89FF3F6D318DBF4DBA0A5ABC5ECBEA

   Write the patched NOR dump back to the device.

2. Connect the device via serial cable, power it on and interrupt
   the boot process by pressing Ctrl+C. Enter the U-Boot password to access
   the CLI.

3. (Optional) Populate the uboot-env partition by entering:

   saveenv

   This will allow you to use uboot-envtools from within OpenWrt later,
   e.g. to increase the loadable kernel size.

   The default loadable kernel size is 5MB, the compressed kernel size at
   the time of this commit is 3.1MB.

4. Serve the initramfs OpenWrt image from a TFTP server at 10.0.1.13/24,
   connected to eth0 (WAN) of the device. File name must be 'uImage'. Boot
   with:

   tftpboot; bootm;

   Make sure to use the correct image for your device (T10 resp. T15)!

5. After booting, connect to OpenWrt on eth1 (LAN) via SSH. Verify
   that the UBI partiton is mtd7, format it and install the sysupgrade
   image.

   $ cat /proc/mtd
   $ ubiformat /dev/mtd7 -y
   $ sysupgrade -n <path to sysupgrade.bin>

6. The device should now boot OpenWrt from NAND flash. Enjoy.

Back to stock:

Use the vendor recovery procedure.

Stock recovery might also be necessary in case you have accidentally used
the fw_setenv command from within OpenWrt without using saveenv in U-Boot
first.

In order to use the vendor firmware recovery procedure, the NAND partitions
mtd3 to mtd6 must remain intact. Make sure not to overwrite them, or keep
dumps of them for later recovery.

Please insert instructions here

Pictures

User Images