Fortinet FortiWiFi 50E-2R
Fortinet FortiWiFi 50E-2R (FWF-50E-2R) is a UTM with 2x WLAN, based on Armada 385 (88F6820).
Hardware Highlights
Installation
Flash Layout
Find out flash layout, then add the flash layout table here (copy, paste, modify the example).
Please check out the article Flash layout. It contains examples and explanations that describe how to document the flash layout.
OEM installation using the TFTP method
Before you can install OpenWrt on this router, you need to have a TFTP server ready to serve the initial firmware. As of this writing, OpenWrt for FWF-50E-2R is available only in snapshots, so the initial firmware image can be downloaded from here:
https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/openwrt-mvebu-cortexa9-fortinet_fwf-50e-2r-initramfs-kernel.bin
You need to remember (or write down) TFTP server's IP address and the file name for the firmware. By default, the router will look for a file named image.out, but you can change that (read on to see how).
Before you begin, while your router is still turned off, connect the router's console port to your management computer and start your console program using connection speed 9600 bps. Next, turn on your router. You will see output similar to this:
FortiGate-50E (17:37-01.31.2017) Ver:05000016 Serial number: CPU(00): 1600MHz Total RAM: 2GB Initializing boot device... Initializing MAC... Please wait for OS to boot, or press any key to display configuration menu.
When you see that last line, press Enter. The boot process will stop, and you will be shown a menu:
[C]: Configure TFTP parameters. [R]: Review TFTP parameters. [T]: Initiate TFTP firmware transfer. [F]: Format boot device. [I]: System information. [B]: Boot with backup firmware and set as default. [Q]: Quit menu and continue to boot. [H]: Display this list of options. Enter C,R,T,F,I,B,Q,or H:
From here, you have several options. One is to use option [R]: Review TFTP parameters to check the current settings and then, go back to your TFTP server and set it up as the router expects. Another option is to change TFTP settings on the router to match the settings on the TFTP server (the ones you have written down) by using option [C]: Configure TFTP parameters. Regardless of which option you chose, when everything is ready, use option [T]: Initiate TFTP firmware transfer to download and run the initial firmware. Note that one of the TFTP settings is the port the router will use for the TFTP connection, so be sure to connect the TFTP server to the port on the router on which the router expects a connection. But before you do that, let's discuss yet another option.
There is option G not shown on the menu, which allows you to specify TFTP parameters interactively. In the opinion of this writer, this is the easiest path, so let's walk through it.
At the boot menu, press G. You will be shown current TFTP settings, one by one, and asked to confirm them by pressing Enter or enter different ones. The interaction will look something like this:
Please connect TFTP server to Ethernet port 'WAN1'. Enter TFTP server address [192.168.1.168]: Enter local address [192.168.1.188]: Enter firmware image file name [image.out]: image50E2R.out
In the example above, the user agreed to default settings for TFTP server IP address and local (meaning, router's) IP address, but specified a different name for the firmware image file (this can be handy if you keep firmware files for several Fortinet devices, so you can tell which file to use with which device). Note that first thing you have been asked to do is to connect the TFTP server to port WAN1, so don't forget to do this.
When you enter (or confirm) all settings, the router will attempt to retrieve firmware from the TFTP server. If successful, it will ask you how you want to run the firmware:
Connect to tftp server 192.168.1.168 ... ########### Image Received. Checking image... OK Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?
Choose option R; this will tell the router to boot into OpenWrt but not to save it to storage. You will see the familiar OpenWrt boot sequence. When the boot sequence is complete, press Enter to gain OpenWrt command prompt.
At this point, OpenWrt is running in-memory, so you need to write it to the persistent storage. To do that, you need to perform a sysupgrade. Disconnect your router from the TFTP server and connect one of the router's WAN ports to your upstream device. Test your Internet connection, for example, by pinging Google:
ping -c 3 google.com
If the connection is active, perform sysupgrade. As of this writing, OpenWrt for FWF-50E-2R is available only in snapshots, so your sysupgrade command will look like this:
sysupgrade https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/openwrt-mvebu-cortexa9-fortinet_fwf-50e-2r-squashfs-sysupgrade.bin
Sysupgrade will commence. After firmware is written to persistent storage, the router will reboot, most likely, into OpenWrt. Why most likely? Because this router has dual firmware layout, so OpenWrt occasionally gets written as backup firmware rather than default firmware. If that happens, the device will boot with stock firmware following sysupgrade. So if you notice that the device is booting with stock firmware, reboot the device, interrupt the boot to gain access to the boot menu, and use option [B]: Boot with backup firmware and set as default; this will tell the device to boot with OpenWrt and set OpenWrt as the default firmware.
For Reference Only
Default TFTP parameters (may have been changed by the previous owner of your router):
Image download port: Port 5 DHCP status: Disabled Local VLAN ID: <NULL> Local IP address: 192.168.1.188 Local subnet mask: 255.255.255.0 Local gateway: 192.168.1.254 TFTP server IP address: 192.168.1.168 Firmware file name: image.out
Upgrading OpenWrt
These are generic instructions. Update with your router's specifics.
LuCI Web Upgrade Process
- Browse to
http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/LuCI Upgrade URL - Upload image file for sysupgrade to LuCI
- Wait for reboot
Terminal Upgrade Process
If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:
sysupgrademtd
Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.
sysupgrade
- Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc sysupgrade /tmp/xxx.abc
mtd
If sysupgrade does not support this router, use mtd.
- Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc mtd write /tmp/xxx.abc linux && reboot
Debricking
Failsafe mode
Basic configuration
→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.
Specific Configuration
Please fill in real values for this device, then remove the EXAMPLEs
Network interfaces
The default network configuration is:
| Interface Name | Description | Default configuration |
|---|---|---|
| br-lan | EXAMPLE LAN & WiFi | EXAMPLE 192.168.1.1/24 |
| vlan0 (eth0.0) | EXAMPLE LAN ports (1 to 4) | EXAMPLE None |
| vlan1 (eth0.1) | EXAMPLE WAN port | EXAMPLE DHCP |
| wl0 | EXAMPLE WiFi | EXAMPLE Disabled |
Switch Ports (for VLANs)
Please fill in real values for this device, then remove the EXAMPLEs
Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.
| Port | Switch port |
|---|---|
| Internet (WAN) | EXAMPLE 4 |
| LAN 1 | EXAMPLE 3 |
| LAN 2 | EXAMPLE 2 |
| LAN 3 | EXAMPLE 1 |
| LAN 4 | EXAMPLE 0 |
Buttons
→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.
Please fill in real values for this device, then remove the EXAMPLEs
The @@Brand@@ @@Model@@ has the following buttons:
| BUTTON | Event |
|---|---|
| EXAMPLE Reset | reset |
| EXAMPLE Secure Easy Setup | ses |
| EXAMPLE No buttons at all. | - |
Hardware
Info
- This table is automatically generated, once the correct filters for Brand and Model are set.
- If you see “Nothing.” instead of a table, please edit this section and adjust the filters with the proper Brand and Model. Just try, it's easy.
- If you still don't see a table here, or a table filled with '¿': Is there already a Techdata page available for @@Brand@@ @@Model@@ @@Version|@@? If not: Create one.
- If you see a table with the desired device data, everything is OK and you can delete this text and the
<WRAP>that encloses it. - If it still doesn't work: Don't panic, calm down, take a deep breath and contact a wiki admin (tmomas) for help.
Photos
Front:
Insert photo of front of the casing
Back:
Insert photo of back of the casing
Backside label:
Insert photo of backside label
Opening the case
Note: This will void your warranty!
Describe what needs to be done to open the device, e.g. remove rubber feet, adhesive labels, screws, ...
- To remove the cover and open the device, do a/b/c
Main PCB:
Insert photo of PCB
Serial
→ port.serial general information about the serial port, serial port cable, etc.
How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port
Replace EXAMPLE by real values.
| Serial connection parameters for Fortinet Fortiwifi 50e-2r | 9600, 8N1 |
|---|
JTAG
→ port.jtag general information about the JTAG port, JTAG cable, etc.
How to connect to the JTAG Port of this specific device:
Insert photo of PCB with markings for JTAG port
Bootloader mods
Hardware mods
None so far.
Bootlogs
OEM bootlog
ortiWiFi-50E-2R (14:48-02.21.2017) Ver:05000007 Serial number: <serial> CPU(00): 1600MHz Total RAM: 2GB Initializing boot device... Initializing MAC... egiga1 Please wait for OS to boot, or press any key to display configuration menu.......... Booting OS... Reading boot image... 4318720 bytes. Initializing firewall... System is starting... FortiWiFi-50E-2R login:
OpenWrt SNAPSHOT bootlog
Of note is I have repeatable issues with serial console out on boot. With a hardware serial port and a USB serial port. Bootlog below is what I have on output and is missing newlines / corrupted in spots?
FortiWiFi-50E-2R (14:48-02.21.2017) Ver:05000007 Serial number: <serial> CPU(00): 1600MHz Total RAM: 2GB Initializing boot device... Initializing MAC... egiga0 Please wait for OS to boot, or press any key to display configuration menu.......... Booting OS... Reading boot image... 4099072 bytes. Initializing firewall... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.6.58 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r27917-3cdab2ad44) 13.3.0, GN4 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Fortinet FortiWiFi 50E-2R [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff] [ 0.000000] HighMem [mem 0x0000000030000000-0x000000007fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x000000007fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff] [ 0.000000] percpu: Embedded 12 pages/cpu s19348 r8192 d21612 u49152 [ 0.000000] Kernel command line: [ 0.000000] Bootloader command line not present [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 522560 [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 2063492K/2097152K available (9216K kernel code, 669K rwdata, 2248K rodata, 1024K init, 247K bss, 33660K reserved, 0K ) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x06070000 -> 0x16070000 [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 D prefetch enabled, offset 1 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000001] sched_clock: 64 bits at 800MHz, resolution 1ns, wraps every 4398046511103ns [ 0.000012] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0xb881274fa3, max_idle_ns: 440795210636 ns [ 0.000026] Switching to timer-based delay loop, resolution 1ns [ 0.000152] Ignoring duplicate/late registration of read_current_timer delay [ 0.000155] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns [ 0.000317] Calibrating delay loop (skipped), value calculated using timer frequency.. 1600.00 BogoMIPS (lpj=8000000) [ 0.000324] CPU: Testing write buffer coherency: ok [ 0.000341] CPU0: Spectre v2: using BPIALL workaround [ 0.000345] pid_max: default: 32768 minimum: 301 [ 0.003416] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003423] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.006188] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.006553] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1. [ 0.006612] Setting up static identity map for 0x100000 - 0x100060 [ 0.006684] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4 [ 0.006757] mvebu-pmsu: Initializing Power Management Service Unit [ 0.006824] rcu: Hierarchical SRCU implementation. [ 0.006827] rcu: Max phase no-delay instances is 1000. [ 0.006974] smp: Bringing up secondary CPUs ... [ 0.007152] Booting CPU 1 [ 0.007274] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.007280] CPU1: Spectre v2: using BPIALL workaround [ 0.007339] smp: Brought up 1 node, 2 CPUs [ 0.007343] SMP: Total of 2 processors activated (3200.00 BogoMIPS). [ 0.007347] CPU: All CPU(s) started in SVC mode. [ 0.010221] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.010279] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.010288] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.011902] pinctrl core: initialized pinctrl subsystem [ 0.012741] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.013220] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.013689] thermal_sys: Registered thermal governor 'step_wise' [ 0.013855] cpuidle: using governor ladder [ 0.013974] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling [ 0.013980] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling [ 0.019222] cryptd: max_cpu_qlen set to 1000 [ 0.020616] SCSI subsystem initialized [ 0.020871] usbcore: registered new interface driver usbfs [ 0.020895] usbcore: registered new interface driver hub [ 0.020912] usbcore: registered new device driver usb [ 0.021659] clocksource: Switched to clocksource arm_global_timer [ 0.025111] NET: Registered PF_INET protocol family [ 0.025214] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.026077] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 0.026090] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.026106] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.026143] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 0.026258] TCP: Hash tables configured (established 8192 bind 8192) [ 0.026482] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 0.026611] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.026635] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.026879] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.026899] PCI: CLS 0 bytes, default 64 [ 0.027460] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 0.031589] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.031594] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.035357] bounce: pool size: 64 pages [ 0.035541] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 0.036671] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver [ 0.037371] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.037475] debugfs: Directory 'f1018100.gpio' with parent 'regmap' already present! [ 0.037717] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.037808] debugfs: Directory 'f1018140.gpio' with parent 'regmap' already present! [ 0.038042] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges: [ 0.038064] mvebu-pcie soc:pcie: MEM 0x00f1080000..0x00f1081fff -> 0x0000080000 [ 0.038078] mvebu-pcie soc:pcie: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000 [ 0.038090] mvebu-pcie soc:pcie: MEM 0x00f1044000..0x00f1045fff -> 0x0000044000 [ 0.038110] mvebu-pcie soc:pcie: MEM 0x00f1048000..0x00f1049fff -> 0x0000048000 [ 0.038121] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 0.038132] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 0.038143] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 0.038153] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 0.038164] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 0.038174] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 0.038184] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 0.038192] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 0.038489] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00 [ 0.038495] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.038502] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff]) [ 0.038508] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff]) [ 0.038513] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff]) [ 0.038518] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff]) [ 0.038522] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff] [ 0.038526] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff] [ 0.038583] pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400 [ 0.038736] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400 [ 0.039662] PCI: bus0: Fast back to back transfers disabled [ 0.039667] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.039674] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.039745] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000 [ 0.039764] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 0.039790] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] [ 0.039855] pci 0000:01:00.0: supports D1 D2 [ 0.039859] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.039963] PCI: bus1: Fast back to back transfers disabled [ 0.039967] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.040039] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 [ 0.040058] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 0.040084] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] [ 0.040150] pci 0000:02:00.0: supports D1 D2 [ 0.040153] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.040265] PCI: bus2: Fast back to back transfers disabled [ 0.040269] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02 [ 0.040287] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff] [ 0.040294] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0400000-0xe06fffff] [ 0.040301] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit] [ 0.040311] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref] [ 0.040317] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.040322] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe02fffff] [ 0.040336] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0400000-0xe05fffff 64bit] [ 0.040346] pci 0000:02:00.0: BAR 6: assigned [mem 0xe0600000-0xe060ffff pref] [ 0.040351] pci 0000:00:02.0: PCI bridge to [bus 02] [ 0.040355] pci 0000:00:02.0: bridge window [mem 0xe0400000-0xe06fffff] [ 0.040660] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.102183] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.102367] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.162163] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.162362] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled [ 0.163665] printk: console [ttyS0] disabled [ 0.183867] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 40, base_baud = 15625000) is a 16550A [ 0.183889] printk: console [ttyS0] enabled [ 12.696841] loop: module loaded [ 12.737358] spi-nor spi1.0: mx66l1g45g (131072 Kbytes) [ 12.799145] 12 fixed-partitions partitions found on MTD device spi1.0 [ 12.876391] Creating 12 MTD partitions on "spi1.0": [ 12.934854] 0x000000000000-0x0000001c0000 : "u-boot" [ 12.994595] 0x0000001c0000-0x0000001d0000 : "firmware-info" [ 13.061603] 0x0000001d0000-0x0000001e0000 : "dtb" [ 13.118239] 0x0000001e0000-0x0000001f0000 : "u-boot-env" [ 13.182197] 0x0000001f0000-0x000000200000 : "board-info" [ 13.246073] OF: Bad cell count for /soc/spi@10680/flash@0/partitions [ 13.322356] 0x000000200000-0x000000800000 : "kernel" [ 13.382051] 0x000000800000-0x000002000000 : "rootfs" [ 13.441802] mtd: setting mtd6 (rootfs) as root device [ 13.502437] 1 squashfs-split partitions found on MTD device rootfs [ 13.576528] 0x000000b60000-0x000002000000 : "rootfs_data" [ 13.641510] 0x000002000000-0x000002600000 : "kn2" [ 13.698173] 0x000002600000-0x000003e00000 : "rfs2" [ 13.755867] 0x000003e00000-0x000005000000 : "part1" [ 13.814647] 0x000005000000-0x000006200000 : "part2" [ 13.873389] 0x000006200000-0x000008000000 : "config" [ 13.991791] hwmon hwmon0: temp1_input not attached to any thermal zone [ 14.121756] hwmon hwmon1: temp1_input not attached to any thermal zone [ 14.211921] mv88e6085 f1072004.mdio-mii:02: switch 0x1760 detected: Marvell 88E6176, revision 1 [ 14.370148] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled [ 14.460528] mvneta f1070000.ethernet eth0: Using device tree mac address <redacted> [ 14.560916] mvneta f1030000.ethernet eth1: Using device tree mac address <redacted> [ 14.661274] mvneta f1034000.ethernet eth2: Using device tree mac address <redacted> [ 14.760823] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 14.824522] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 1 [ 14.914366] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000000010 [ 15.024960] xhci-hcd f10f0000.usb3: irq 46, io mem 0xf10f0000 [ 15.093939] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 15.157619] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2 [ 15.247371] xhci-hcd f10f0000.usb3: Host supports USB 3.0 SuperSpeed [ 15.323899] hub 1-0:1.0: USB hub found [ 15.368978] hub 1-0:1.0: 1 port detected [ 15.416214] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 15.513478] hub 2-0:1.0: USB hub found [ 15.558411] hub 2-0:1.0: 1 port detected [ 15.605671] usbcore: registered new interface driver usb-storage [ 15.678184] armada38x-rtc f10a3800.rtc: registered as rtc0 [ 15.744012] armada38x-rtc f10a3800.rtc: setting system clock to 2024-10-28T04:05:02 UTC (1730088302) [ 15.853778] i2c_dev: i2c /dev entries driver [ 15.905345] pca953x 0-0024: supply vcc not found, using dummy regulator [ 15.984709] pca953x 0-0024: using no AI [ 16.034070] orion_wdt: Initial timeout 171 sec [ 16.087563] sdhci: Secure Digital Host Controller Interface driver [ 16.161670] sdhci: Copyright(c) Pierre Ossman [ 16.213985] sdhci-pltfm: SDHCI platform and OF driver helper [ 16.292089] marvell-cesa f1090000.crypto: CESA device successfully registered [ 16.378400] NET: Registered PF_INET6 protocol family [ 16.438701] Segment Routing with IPv6 [ 16.482606] In-situ OAM (IOAM) with IPv6 [ 16.529656] NET: Registered PF_PACKET protocol family [ 16.590232] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you nee. [ 16.745724] 8021q: 802.1Q VLAN Support v1.8 [ 16.795902] Registering SWP/SWPB emulation handler [ 16.881823] mv88e6085 f1072004.mdio-mii:02: switch 0x1760 detected: Marvell 88E6176, revision 1 [ 17.038242] hwmon hwmon3: temp1_input not attached to any thermal zone [ 17.130867] hwmon hwmon4: temp1_input not attached to any thermal zone [ 17.228201] hwmon hwmon5: temp1_input not attached to any thermal zone [ 17.325363] hwmon hwmon6: temp1_input not attached to any thermal zone [ 17.433028] hwmon hwmon7: temp1_input not attached to any thermal zone [ 18.275314] mv88e6085 f1072004.mdio-mii:02: configuring for fixed/rgmii-id link mode [ 18.375032] mv88e6085 f1072004.mdio-mii:02: Link is Up - 1Gbps/Full - flow control off [ 18.526176] mv88e6085 f1072004.mdio-mii:02 lan5 (uninitialized): PHY [mv88e6xxx-0:00] driver [Marvell 88E1540] (irq=62) [ 18.750633] mv88e6085 f1072004.mdio-mii:02 lan4 (uninitialized): PHY [mv88e6xxx-0:01] driver [Marvell 88E1540] (irq=63) [ 18.980507] mv88e6085 f1072004.mdio-mii:02 lan3 (uninitialized): PHY [mv88e6xxx-0:02] driver [Marvell 88E1540] (irq=64) [ 19.210612] mv88e6085 f1072004.mdio-mii:02 lan2 (uninitialized): PHY [mv88e6xxx-0:03] driver [Marvell 88E1540] (irq=65) [ 19.436152] mv88e6085 f1072004.mdio-mii:02 lan1 (uninitialized): PHY [mv88e6xxx-0:04] driver [Marvell 88E1540] (irq=66) [ 19.570320] mvneta f1070000.ethernet eth0: entered promiscuous mode [ 19.645480] DSA: tree 0 setup [ 19.681365] clk: Disabling unused clocks [ 19.750532] VFS: Mounted (squashfs ystem) readon device 3 [ 19.815864] Freeing unusernel image mem) memory4K [ 19.872416] Run /sbin/ini init proce[ 20.869730] init: Consolealive [ 20.905047] init: - watc- [ 22.642733] kmodloader: lng kernel ms from /etcles-boot.d/[ 22.931622] gpio_button_hug: loadingof-tree modaints kerne[ 22.991198] kmo* [ 23.070244] init: - prein [ 27.541664] random: crng done Cannot parse config file '/etc/fw_env.config': No such file or directory Failed to find NVMEM device [ 28.401823] mvneta f10700thernet ethnfiguring fxed/rgmii-ik mode [ 28.472840] mv88e6085 f14.mdio-mii:n1: configufor phy/gmiik mode [ 28.544140] mvneta f1070thernet ethnk is Up - /Full - flowtrol off Press the [f] key and hit [enter] to enter failsafe mode Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level [ 33.261389] jffs2: notice72) jffs2_bxattr_subsy complete bng xattr subem, 8 of xd(0 uncheckeorphan) and xref (2 de orphan) fo [ 33.3986y [ 33.454349] overlayfs: upfs does notort tmpfile[ 33.520946] urandom-seed:ding with /random.seed[ 33.859010] procd: - earl [ 33.88940- [ 34.581642] procd: - watc - [ 34.845636] procd: - ubus[ 35.219644] procd: - initPlease press Enter to activate this console. [ 36.568850] kmodloader: lng kernel ms from /etcles.d/* [ 36.833830] urngd: v1.0.2rted. [ 37.037764] Loading modulackported finux versio11.2-0-g7aa187b [ 37.107707] Backport gened by backpoit v6.1.110-gc61f71fe0[ 37.692473] PPP generic dr version 2 [ 37.734791] NET: RegisterF_PPPOX pro y [ 37.797793] ath10k 6.10 dr, optimize CT firmwarobing pci d: 0x3c. [ 37.868515] pci 0000:00: enabling d (0140 -> 0 [ 37.922958] ath10k_pci 001:00.0: ena device (01 0142) [ 38.448904] ath10k_pci 001:00.0: qcahw2.0 targe100016c chi0x043222ff s000:0000 [ 38.531117] ath10k_pci 01:00.0: kcodebug 0 deb1 tracing 0 1 testmode [ 38.605337] ath10k_pci 01:00.0: fir ver 10.1-c__fW-022-eca8 api 2f [ 38.859067] ath10k_pci 001:00.0: boale api 1 bmN/A crc32 b08 [ 39.775663] ath10k_pci 001:00.0: 10. init: vdev peers: 12d: 256 [ 39.855496] ath10k_pci 001:00.0: wmit 'P 128 V 10' [ 39.912943] ath10k_pci 001:00.0: wmit 'msdu-des24 sw-crypct-sta: 0' [ 39.983362] ath10k_pci 01:00.0: wmit 'alloc re984 iram: 38 [ 40.196844] ath10k_pci 01:00.0: NOTirmware DBGutput disabln debug_mas10000000o 1 [ 40.561955] ath10k 6.10 dr, optimize CT firmwareobing pci d: 0x3c. [ 40.633955] pci 0000:00: enabling d (0140 -> 0 [ 40.688176] ath10k_pci 002:00.0: ena device (01 0142) [ 40.749344] ath10k_pci 002:00.0: pcimsi oper_ire 2 irq_modeeset_mode 0[ 41.091375] ath10k_pci 002:00.0: qcahw2.0 targe100016c chi0x04320 [ 41.173569] ath10k_pci 02:00.0: kcodebug 0 deb1 tracing 0 1 testmode [ 41.247829] ath10k_pci 02:00.0: fir ver 10.1-c__fW-022-eca8 api 2f [ 41.500681] ath10k_pci 002:00.0: boale api 1 bmN/A crc32 b08 [ 42.417130] ath10k_pci 002:00.0: 10. init: vdev peers: 12d: 256 [ 42.496982] ath10k_pci 002:00.0: wmit 'P 128 V 10' [ 42.554433] ath10k_pci 002:00.0: wmit 'msdu-des24 sw-crypct-sta: 0' [ 42.624849] ath10k_pci 02:00.0: wmit 'alloc re984 iram: 38 [ 50.382005] mvneta f10700thernet ethnfiguring fxed/rgmii-idk mode.282252] mvneta f10700thernet ethnk is Down [ 50.452832] mvneta f1070thernet ethnk is Up - 1/Full - flotrol off [ 50.610265] mv88e6085 f104.mdio-mii:n1: configufor phy/gmiik mode [ 50.764438] br-lan: portn1) enteredbled statee [ 50.816529] mv88e6085 f14.mdio-mii:n1: entered ulticast mo[ 50.879646] mvneta f1070thernet ethtered allmust mode [ 51.017000] mv88e6085 f104.mdio-mii:n1: entered iscuous mod[ 51.165791] mv88e6085 f104.mdio-mii:n2: configufor phy/gmiik mode [ 51.380476] mv88e6085 f14.mdio-mii:n2: enteredulticast mod[ 51.468514] mv88e6085 f104.mdio-mii:n2: enterediscuous mod[ 51.611351] mv8e [ 51.817813] mv88e6085 f14.mdio-mii:n3: enteredulticast mod[ 51.906140] mv88e6085 f104.mdio-mii:n3: enterediscuous mod[ 52.045466] mv8e [ 52.118487] br-lan: port n4) enteredking state [ 52.217679] mv88e6085 f14.mdio-mii:n4: entered ulticast mo[ 52.321784] mv88e6085 f104.mdio-mii:0n4: enterediscuous mode[ 52.477426] me [ 53.044785] mvneta f1030thernet ethnfiguring fy/sgmii linke 52.747320] mv88e6085 f104.mdio-mii:n5: enterediscuous mod[ 52.962096] mvn) [ 53.215846] mvneta f1030thernet ethtered allmust mode [ 53.278875] mvneta f1030thernet ethtered promis mode [ 53.564395] mvneta f1034thernet ethnfiguring fy/sgmii linke[Marvell 88] (irq=42) [ 53.735715] mvneta f1034thernet ethtered allmust mode [ 53.798591] mvneta f1034thernet ethtered promis mode BusyBox v1.36.1 (2024-10-27 13:25:24 UTC) built-in shell (ash) _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- OpenWrt SNAPSHOT, r27917-3cdab2ad44 ----------------------------------------------------- === WARNING! ===================================== There is no root password defined on this device! Use the "passwd" command to set up a new password in order to prevent unauthorized SSH logins. -------------------------------------------------- root@OpenWrt:~#
Notes
Space for additional notes, links to forum threads or other resources.
At least on my unit, due to the way that the antennas/filters are set up:
'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
Should be on 5ghz.
Whilst
option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
Should be on 2.4ghz to get max wireless power out of the antennas.
Both radios can do both bands and be configured as such.
Regarding the power supply. The pinout is the pin closest to the locking tab is positive 12V. The one below is the negative “return”. To double check you can look on theh side of the included power supply it gives the pinout there. Or check with a multimeter.
- ...
Tags
Add tags below, then remove this fixme.