AVM FRITZ!Box Fon WLAN 7360 (SL)
Warning!
Not all FRITZ!Box 7360 v1 and SL models are properly labeled. Make sure to verify your model with HWRevision
This box is using a Lantiq SoC, see soc.lantiq The box is currently supported as “stable” in LEDE since 17.01 (reboot).
The DECT does not work and is not supported due to missing PIGLET and DECT Driver (AVM driver is closed source). If you need DECT and/ or fully phone support, you should take a look at freetz.
Phone works only via SIP with asterisk or another SIP package and a wifi or ethernet SIP phone.
Supported Versions
Version/Model | Launch Date | S/N | OpenWrt/LEDE Version Supported | Model Specific Notes |
---|---|---|---|---|
v1 | 2010 | D303.400.30.xxx.xxx | L: 17.01, O: WIP | 1&1 (1und1) |
Hardware Highlights
CPU | Flash | Ram | Network | USB | Serial | JTag | DSL |
---|---|---|---|---|---|---|---|
2x MIPS 34Kc 5.6 | 16MB | 128MB | 2x 1000M (eth0, eth1) & 2x 100M (eth2, eth3) | Yes (2x 2.0) | Yes | ? | VDSL2 + ADSL2+ |
Installation
Firmware download
Flashing OpenWrt on the FRITZ!Box 7360 via BOOTLOADER (ADAM2)
Background info see: generic EVA FTP firmware flash
- Basically you enter the bootloader, upload firmware via FTP, bootloader flashes it. As indicated above this OpenWrt firmware works for FRITZ!Box 7360 v1 devices. For v1 devices the version number starts with 111 (v2 starts with 124) under Web Interface/System/Update/FRITZ!OS-Datei.
- While flashing, the FRITZ!Box will indicate the flash progress via the info LED (red light) and turn it off when done.
- It might be tricky to get the 'ftp 192.168.178.1' command working as indicated in the code box below as the router accepts FTP connections only in the first seconds after boot. If the command fails, it may lead to “ftp: connect: Connection refused” or “ftp: connect: Connection timed out” messages. First, try to connect to the router via ethernet cable (try LAN 3 if LAN 1 won't work with FTP). After the connection was established, power off the router for a second, power it on, and while it is re-connecting run the ftp command in the terminal.
Flashing OpenWrt Steps:
1. Download the firmware file avm_fritz7360sl-squashfs-sysupgrade.bin:
wget https://downloads.openwrt.org/releases/18.06.1/targets/lantiq/xrx200/openwrt-18.06.1-lantiq-xrx200-avm_fritz7360sl-squashfs-sysupgrade.bin
2. Use FTP in order to enter the bootloader:
ftp 192.168.178.1
After the connection was successfully established (see hints above) use as Name: adam2 and Password: adam2
3. Verify that you really have a 7360 SL / v1 model:
quote GETENV HWRevision
HWRevision 181 is the “SL” model, HWRevision 183 is the “v1” model (this variant may require you to “quote MEDIA FLSH” *before* entering binary transfer mode, depending on your specific bootloader version).1) If you see HWRevision 196, please follow the instructions on AVM FRITZ!Box 7360 v2.
4. Enter binary transfer mode:
bin
5. Enable passive mode (only necessary for older clients):
passiv
6. Set media:
quote MEDIA FLSH
7. Use the downloaded firmware:
put openwrt-18.06.1-lantiq-xrx200-avm_fritz7360sl-squashfs-sysupgrade.bin mtd1
8. When it's finished:
exit
After OpenWrt ist flashed, the FRITZ!Box IP will change to 192.168.1.1. You should NOT erase mtd3 and mtd4.
* While flashing OpenWrt via ADAM2 onto the SL-variant, you should drive a session like in the code box:
$ ftp 192.168.178.1 Connected to 192.168.178.1. 220 ADAM2 FTP Server ready Name (192.168.178.1:unknown): adam2 331 Password required for adam2 Password: 230 User adam2 successfully logged in Remote system type is AVM. ftp> quote GETENV HWRevision HWRevision 181 ftp> bin 200 Type set to BINARY ftp> passiv Passive mode on. ftp> quote MEDIA FLSH 200 Media set to MEDIA_FLASH ftp> put openwrt-18.06.1-lantiq-xrx200-avm_fritz7360sl-squashfs-sysupgrade.bin mtd1 local: openwrt-18.06.1-lantiq-xrx200-avm_fritz7360sl-squashfs-sysupgrade.bin remote: mtd1 227 Entering Passive Mode (192,168,178,1,12,15) 150 Opening BINARY data connection 226 Transfer complete 5243074 bytes sent in 10.39 secs (492.8278 kB/s) ftp> exit 221 Thank you for using the FTP service on ADAM2
* While flashing OpenWrt via ADAM2 onto the v1-variant, you should drive a session like in the code box:
# ftp adam2@192.168.178.1 Connected to 192.168.178.1. 220 ADAM2 FTP Server ready 331 Password required for adam2 Password: 230 User adam2 successfully logged in Remote system type is AVM. ftp> quote MEDIA FLSH 200 Media set to MEDIA_FLASH ftp> bin 200 Type set to BINARY ftp> passiv Passive mode: off; fallback to active mode: off. ftp> passiv Passive mode: on; fallback to active mode: on. ftp> debug Debugging on (debug=1). ftp> put fw.bin mtd1 local: fw.bin remote: mtd1 ---> EPSV 502 Command not implemented disabling epsv4 for this connection ---> PASV 227 Entering Passive Mode (192,168,178,1,12,6) ---> STOR mtd1 150 Opening BINARY mode data connection 100% |****************************************************************| 7424 KiB 479.16 KiB/s 00:00 ETA 226 Transfer complete 7602790 bytes sent in 00:15 (478.58 KiB/s) ftp> exit ---> QUIT 221 Thank you for using the FTP service on ADAM2
* After flashing you can power cycle the device
WiFi / Wireless / WLAN
If your wireless radio is not working try this:
- press WLAN button on the router for a few seconds (worked for me)
or
- type via ssh: uci set wireless.radio0.disabled='0';uci commit
xDSL Settings
In /etc/config/network use these settings for ADSL
config atm-bridge 'atm' option vpi '1' option vci '32' option encaps 'llc' option payload 'bridged' config dsl 'dsl' option annex 'bdmt' option xfer_mode 'atm' option line_mode 'adsl' config interface 'wan' option proto 'pppoe' option ipv6 'auto' option username 'username' option password 'password' option ifname 'nas0'
Telnet access
call #96*7* to enable telnetd or call #96*8* to disable the telnetd
FRITZ!Box 7360 v1 OpenWrt VDSL Configuration
- The chipset in the FRITZ!Box 7360 v1 supports vectoring, which means this hardware is capable of providing high speed VDSL.
- After OpenWrt is flashed on the device there is an additional (xdsl vectoring enabled) firmware required in order to support vectoring (otherwise if the network supports VDSL vectoring, but the VDSL modem does not support it, the device will be put into a fall back mode using only the lower 2.2 MHz of the band, this results in reduced rates like 13 MBit/s down and 1.4 MBit/s up instead of 50 MBit/s).
- The required firmware can be extracted from the factory FRITZ!Box 7360 v1 image file (as its about the same chipset, it's also possible to get this firmware file e.g. from the FRITZ!Box 7490 image).
Steps for how to get the firmware file with Freetz and use it on OpenWrt:
1. Download the factory image file (in this case ver. 111.06.32 v1 EWE edition image - newer versions without EWE are supposed to have also the same firmware file; check if your country uses AnnexA or AnnexB):
wget http://download.ewe.de/avm/7360/download/FRITZ.Box_Fon_WLAN_7360.AnnexB.111.06.35.image
2. Freetz from the freetz.org project is needed in order to build the required tools. Install the Freetz-dependencies first (tested on Debian Stretch; for other Distros click here):
sudo apt install imagemagick subversion git gcc g++ binutils autoconf automake autopoint libtool-bin make bzip2 libncurses5-dev libreadline-dev zlib1g-dev flex bison patch texinfo tofrodos gettext pkg-config ecj fastjar realpath perl libstring-crc32-perl ruby ruby1.8 gawk python libusb-dev unzip intltool libacl1-dev libcap-dev libc6-dev-i386 lib32ncurses5-dev gcc-multilib lib32stdc++6 libglib2.0-dev
3. Clone the Freetz repo:
git clone https://github.com/Freetz/freetz.git freetz-devel
4. Cd into the directory 'freetz-devel' and run:
make
5. Also run:
make tools
6. Now we have the image and also the tools. Extract the content of the image:
7z e FRITZ.Box_Fon_WLAN_7360.AnnexB.111.06.32.image
NOTE: p7zip version 15.09 or newer is required to extract the image.
7. Amongst the extracted files there will be a file named 'kernel.image'. Copy or move this file into the '/freetz-devel/tools' directory.
8. Cd into that directory and run:
./find-squashfs kernel.image
9. The command above will create two files named kernel.raw and kernelsquashfs.raw. We need kernelsquashfs.raw - run:
./unsquashfs4-avm-be kernelsquashfs.raw
10. The command creates a directory called 'squashfs-root'. The firmware file can be found in “squashfs-root/lib/modules/dsp_vr9/”. It's called 'vr9-B-dsl.bin'.
11. This file 'vr9-B-dsl.bin' will be transferred into the OpenWrt /lib/firmware directory (obviously the FRITZ!Box device should be connected). Cd into the file's directory /squashfs-root/lib/modules/dsp_vr9. Then use the following scp command:
scp vr9-B-dsl.bin root@192.168.1.1:/lib/firmware
Say “yes” and it will ask for your OpenWrt password if you did set one before (what you are supposed to do). After that the file will be transfered to the OpenWrt /lib/firmware directory.
12. One config file needs to be changed. ssh into the FRITZ!Box flashed with OpenWrt:
ssh root@192.168.1.1
13. Cd into the directory /etc/config/ and use vi in order to edit the network file:
vi network
(if you are not familiar with vi, just search for tips how to use it).
14. Add the line option firmware '/path-to-firmware':
option firmware '/lib/firmware/vr9-B-dsl.bin'
to the config dsl 'dsl' section, so it will look like:
config dsl 'dsl' option annex 'b' option tone 'av' option xfer_mode 'ptm' option firmware '/lib/firmware/vr9-B-dsl.bin'
As indicated here the config interface 'wan' section on OpenWrt 18 should look like (change it according to your country and ISP):
config interface 'wan' option proto 'pppoe' option _orig_ifname 'ptm0' option _orig_bridge 'false' option ifname 'dsl0.7' option username 'H1und1/1234-567@online.de' option password 'abcdefghijklm' option ipv6 'auto'
15. After the changes were saved and the file is closed reboot the router:
reboot
16. Wait several minutes in order to establish a VDSL connection (it takes a little time sometimes).
This guide would not be here without the hints and help provided by hippie2000 and rubberduck in the #fritzbox channel.
Hardware
How to use AVM FRITZ!Box Fon WLAN 7360 v1 with 3G/UMTS SIM Card/USB Dongles
It is possible to connect a 3G/UMTS USB dongle (modem) with a SIM Card to the FRITZ!Box, in order to use the mobile internet connection through the router via LAN or a wireless access point.
Basically there are three steps to set up such a configuration:
- Install the necessary packages for your 3G/UMTS Dongle
- Configure the interface in /etc/config/network
- Add the interface to the firewall zone
1. Installing the necessary packages
It depends on the type of the particular 3G/UMTS USB Dongle which packages are required. Read carefully the wwan connection guide here. Make sure all the necessary packages are installed, especially the packages for the protocol used by your modem (qmi, mbim, ncm, rndis), e.g. a Huawei E600 3G card requires mbim packages. There are hints for OpenWrt according to USB Dongle modem types in many blogs and tutorials on the internet (e.g. how to switch to modem-mode via usb-modeswitch, etc.).
2. Interface configuration
Connect to OpenWrt via ssh and cd to the /etc/config directory. You can edit the file called 'network' with vi.
vi network
Add to the WAN section the appropriate configuration required for your ISP and USB Dongle (e.g. if PIN is required, use: option pincode '1234') Here is an example for the Swedish provider tele2 with Huawei E600:
#### WAN configuration config interface wan2 option ifname 'ppp0' option proto '3g' option device '/dev/usb/tts/0' option apn 'internet.tele2.se'
Or for the German provider alditalk (E173):
#### WAN configuration config interface wan2 option ifname 'ppp0' option proto '3g' option device '/dev/ttyUSB0/0' option service 'umts' option mtu '1400' option apn 'internet'
Save changes and reboot the router with the USB Dongle plugged in.
3. Add to firewall zone
- Use the LuCI interface via webbrowser (192.168.1.1)
- Go to Network → Firewall
- Scroll down to WAN, click on 'Edit'
- Under the covered networks go to wan2 and tick the box
- Click “save&apply”
If the configuration is correct (all the required packages are installed and the interface is properly configured), the modem will blink a few times after reboot and then the light will be permanent indicating that the internet connection was established. After adding the interface to the firewall zone, internet connection should be available via LAN (or if configured WLAN).
Serial
JTAG
How to connect to JTAG interface, and how to reflash the device with JTAG tools.
See port.jtag for more JTAG details.
Hardware Unbricking
A common issue with these devices is a hardware brick (LEDs remain off, device drawing current) caused by faulty ceramic capacitors on the 12v input line, near the regulators.
Check these three capacitors for low-impedance (i.e. short-circuit, capacitor becomes very hot when applying power and may even look damaged) and remove / replace:
Troubleshooting
OpenWrt 21.02 switch issues
Starting from the OpenWrt 21.02, there is a nasty bug which renders device switch unusable. Numerous reports show incorrect link speeds on LAN 1&2 and LAN 3&4 and absence of traffic activity. Bug details here
Poor NAT performance
In case of 1 WAN / 3 LAN networking setup there seems to be a poor networking performance on WAN port with speeds around ~30-40 Mbit/sec. This issue is resolved by turning on Software flow offloading. Go to luci -→ Network -→ firewall and enable it in the settings.
Bootlogs
OpenWrt / LEDE bootlog
[ 0.000000] Linux version 4.4.61 (lipkegu@Medice-PC) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3986-e1d433b) ) #0 SMP Fri Apr 21 05:50:55 2017 [ 0.000000] SoC: xRX200 rev 1.2 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU0 revision is: 00019556 (MIPS 34Kc) [ 0.000000] MIPS: machine is FRITZ7360SL - 1&1 HomeServer [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 08000000 @ 00000000 (usable) [ 0.000000] User-defined physical RAM map: [ 0.000000] memory: 07e00000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x0000000007dfffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000007dfffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007dfffff] [ 0.000000] On node 0 totalpages: 32256 [ 0.000000] free_area_init_node: node 0, pgdat 80534e80, node_mem_map 81008480 [ 0.000000] Normal zone: 252 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32256 pages, LIFO batch:7 [ 0.000000] Detected 1 available secondary CPU(s) [ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] PERCPU: Embedded 9 pages/cpu @8110b000 s8112 r8192 d20560 u36864 [ 0.000000] pcpu-alloc: s8112 r8192 d20560 u36864 alloc=9*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32004 [ 0.000000] Kernel command line: console=ttyLTQ0,115200 mem=126M vpe1_load_addr=0x87e00000 vpe1_mem=2M maxvpes=1 maxtcs=1 nosmp [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Writing ErrCtl register=00049ef0 [ 0.000000] Readback ErrCtl register=00049ef0 [ 0.000000] Memory: 120864K/129024K available (4071K kernel code, 164K rwdata, 1184K rodata, 1220K init, 223K bss, 8160K reserved, 0K cma-reserved) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:256 [ 0.000000] Setting up vectored interrupts [ 0.000000] Setting up IPI vectored interrupts [ 0.000000] CPU Clock: 500MHz [ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns [ 0.000012] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns [ 0.007886] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088) [ 0.042410] pid_max: default: 32768 minimum: 301 [ 0.047303] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.053831] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.064064] Brought up 1 CPUs [ 0.072091] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.081790] futex hash table entries: 512 (order: 2, 16384 bytes) [ 0.088090] pinctrl core: initialized pinctrl subsystem [ 0.094087] NET: Registered protocol family 16 [ 0.103777] pinctrl-xway 1e100b10.pinmux: Init done [ 0.109414] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28 [ 0.220140] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV [ 0.337860] PCI host bridge /fpi@10000000/pcie@d900000 ranges: [ 0.372996] usbcore: registered new interface driver usbfs [ 0.378518] usbcore: registered new interface driver hub [ 0.383890] usbcore: registered new device driver usb [ 0.389371] PCI host bridge to bus 0000:00 [ 0.393381] pci_bus 0000:00: root bus resource [mem 0x1c000000-0x1cffffff] [ 0.400295] pci_bus 0000:00: root bus resource [io 0x1d800000-0x1d8fffff] [ 0.407240] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0] [ 0.414095] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff] [ 0.422135] pci 0000:00:00.0: [1bef:0011] type 01 class 0x060000 [ 0.422183] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to pci-pci bridge [ 0.439937] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.440583] pci 0000:01:00.0: [168c:ff1c] type 00 class 0x020000 [ 0.440686] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit] [ 0.440870] pci 0000:01:00.0: supports D1 [ 0.440892] pci 0000:01:00.0: PME# supported from D0 D1 D3hot [ 0.441213] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.441256] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01 [ 0.441317] pci 0000:00:00.0: BAR 8: assigned [mem 0x1c000000-0x1c0fffff] [ 0.448022] pci 0000:01:00.0: BAR 0: assigned [mem 0x1c000000-0x1c00ffff 64bit] [ 0.455391] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.460403] pci 0000:00:00.0: bridge window [mem 0x1c000000-0x1c0fffff] [ 0.467284] ifx_pcie_bios_map_irq port 0 dev 0000:00:00.0 slot 0 pin 1 [ 0.473932] ifx_pcie_bios_map_irq dev 0000:00:00.0 irq 144 assigned [ 0.480287] ifx_pcie_bios_map_irq port 0 dev 0000:01:00.0 slot 0 pin 1 [ 0.486950] ifx_pcie_bios_map_irq dev 0000:01:00.0 irq 144 assigned [ 0.499444] clocksource: Switched to clocksource MIPS [ 0.506326] NET: Registered protocol family 2 [ 0.511614] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.518554] TCP bind hash table entries: 1024 (order: 1, 8192 bytes) [ 0.524912] TCP: Hash tables configured (established 1024 bind 1024) [ 0.531409] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.537266] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.543871] NET: Registered protocol family 1 [ 0.548276] PCI: CLS 0 bytes, default 32 [ 0.551837] gptu: totally 6 16-bit timers/counters [ 0.556784] gptu: misc_register on minor 63 [ 0.560944] gptu: succeeded to request irq 126 [ 0.565435] gptu: succeeded to request irq 127 [ 0.569945] gptu: succeeded to request irq 128 [ 0.574460] gptu: succeeded to request irq 129 [ 0.578977] gptu: succeeded to request irq 130 [ 0.583506] gptu: succeeded to request irq 131 [ 0.588317] phy-xrx200 gphy-xrx200: requesting lantiq/vr9_phy11g_a2x.bin [ 0.595515] phy-xrx200 gphy-xrx200: booting GPHY0 firmware at 7AA0000 [ 0.601875] phy-xrx200 gphy-xrx200: booting GPHY1 firmware at 7AA0000 [ 0.709938] genirq: Flags mismatch irq 0. 00000000 (RTLX) vs. 00000400 (IPI_resched) [ 0.719342] Crashlog allocated RAM at address 0x3f00000 [ 0.751648] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.757494] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.773746] io scheduler noop registered [ 0.777658] io scheduler deadline registered (default) [ 0.783532] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc [ 0.792464] console [ttyLTQ0] enabled [ 0.799784] bootconsole [early0] disabled [ 0.809000] lantiq nor flash device: 01000000 at 10000000 [ 0.813162] ltq_nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x00227e [ 0.822587] Amd/Fujitsu Extended Query Table at 0x0040 [ 0.827716] Amd/Fujitsu Extended Query version 1.3. [ 0.832750] number of CFI chips: 1 [ 0.836185] 4 ofpart partitions found on MTD device ltq_nor [ 0.841716] Creating 4 MTD partitions on "ltq_nor": [ 0.846594] 0x000000000000-0x000000020000 : "urlader" [ 0.855528] 0x000000020000-0x000000f80000 : "firmware" [ 0.877876] 2 eva-fw partitions found on MTD device firmware [ 0.882163] 0x000000020000-0x0000001d0c2d : "kernel" [ 0.889244] 0x0000001e0100-0x000000f80000 : "rootfs" [ 0.895431] mtd: device 3 (rootfs) set to be root filesystem [ 0.899758] 1 squashfs-split partitions found on MTD device rootfs [ 0.905884] 0x0000008c0000-0x000000f80000 : "rootfs_data" [ 0.913796] 0x000000f80000-0x000000fc0000 : "tffs (1)" [ 0.920351] 0x000000fc0000-0x000001000000 : "tffs (2)" [ 1.030704] libphy: lantiq,xrx200-mdio: probed [ 1.106664] eth0: attached PHY [Atheros 8030 ethernet] (phy_addr=0:00, irq=-1) [ 1.174643] eth0: attached PHY [Atheros 8030 ethernet] (phy_addr=0:01, irq=-1) [ 1.243139] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:11, irq=-1) [ 1.311137] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:13, irq=-1) [ 1.420092] ltq-cputemp cputemp@0: Current CPU die temperature: 68.0 °C [ 1.425710] wdt 1f8803f0.watchdog: Init done [ 1.433122] NET: Registered protocol family 10 [ 1.442260] NET: Registered protocol family 17 [ 1.445487] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 1.457964] 8021q: 802.1Q VLAN Support v1.8 [ 1.474943] VFS: Mounted root (squashfs filesystem) readonly on device 31:3. [ 1.482421] Freeing unused kernel memory: 1220K (8054f000 - 80680000) [ 4.454116] eth0: port 4 got link [ 4.772471] init: Can't open /sys/block/zram0/disksize: No such file or directory [ 4.779174] init: Console is alive [ 4.782236] init: - watchdog - [ 4.812562] kmodloader: loading kernel modules from /etc/modules-boot.d/* [ 4.908567] SCSI subsystem initialized [ 5.450802] eth0: port 1 got link [ 5.774822] dwc2 1e101000.ifxhcd: DWC OTG Controller [ 5.778399] dwc2 1e101000.ifxhcd: new USB bus registered, assigned bus number 1 [ 5.785805] dwc2 1e101000.ifxhcd: irq 62, io mem 0x00000000 [ 5.791292] dwc2 1e101000.ifxhcd: Hardware does not support descriptor DMA mode - [ 5.798698] dwc2 1e101000.ifxhcd: falling back to buffer DMA mode. [ 5.806744] hub 1-0:1.0: USB hub found [ 5.809539] hub 1-0:1.0: 1 port detected [ 6.670822] dwc2 1e106000.ifxhcd: DWC OTG Controller [ 6.674444] dwc2 1e106000.ifxhcd: new USB bus registered, assigned bus number 2 [ 6.681786] dwc2 1e106000.ifxhcd: irq 91, io mem 0x00000000 [ 6.687295] dwc2 1e106000.ifxhcd: Hardware does not support descriptor DMA mode - [ 6.694706] dwc2 1e106000.ifxhcd: falling back to buffer DMA mode. [ 6.702705] hub 2-0:1.0: USB hub found [ 6.705550] hub 2-0:1.0: 1 port detected [ 6.714183] usbcore: registered new interface driver usb-storage [ 6.719713] kmodloader: done loading kernel modules from /etc/modules-boot.d/* [ 6.736619] init: - preinit - [ 7.338178] usb 2-1: new high-speed USB device number 2 using dwc2 [ 7.594201] random: procd: uninitialized urandom read (4 bytes read, 33 bits of entropy available) [ 7.602649] usb-storage 2-1:1.0: USB Mass Storage device detected [ 7.627229] scsi host0: usb-storage 2-1:1.0 [ 8.632126] scsi 0:0:0:0: Direct-Access WD My Book 1230 1065 PQ: 0 ANSI: 6 [ 8.644782] scsi 0:0:0:1: Enclosure WD SES Device 1065 PQ: 0 ANSI: 6 [ 8.652355] sd 0:0:0:0: [sda] Spinning up disk... [ 9.658568] . [ 9.904747] mount_root: loading kmods from internal overlay [ 9.944562] kmodloader: loading kernel modules from //etc/modules-boot.d/* [ 9.953371] kmodloader: done loading kernel modules from //etc/modules-boot.d/* [ 10.293822] jffs2_scan_eraseblock(): End of filesystem marker found at 0x20000 [ 10.299705] jffs2_build_filesystem(): unlocking the mtd device... done. [ 10.306209] jffs2_build_filesystem(): erasing all blocks after the end marker... [ 10.662582] .......ready [ 16.870137] sd 0:0:0:0: [sda] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB) [ 16.877538] sd 0:0:0:0: [sda] Write Protect is off [ 16.881324] sd 0:0:0:0: [sda] Mode Sense: 53 00 10 08 [ 16.882309] sd 0:0:0:0: [sda] No Caching mode page found [ 16.886651] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 17.040188] sda: sda1 sda2 sda3 [ 17.047993] sd 0:0:0:0: [sda] Attached SCSI disk [ 26.142603] random: nonblocking pool is initialized [ 43.742719] done. [ 43.743235] jffs2: notice: (466) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 43.759250] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 43.765849] block: unable to load configuration (fstab: Entry not found) [ 43.772541] block: attempting to load /tmp/jffs_cfg/etc/config/fstab [ 43.778984] block: unable to load configuration (fstab: Entry not found) [ 43.785594] block: attempting to load /etc/config/fstab [ 43.791017] block: unable to load configuration (fstab: Entry not found) [ 43.797499] block: no usable configuration [ 43.869202] jffs2: notice: (463) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 44.788584] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 44.794475] block: unable to load configuration (fstab: Entry not found) [ 44.801146] block: attempting to load /tmp/jffs_cfg/etc/config/fstab [ 44.807583] block: unable to load configuration (fstab: Entry not found) [ 44.814149] block: attempting to load /etc/config/fstab [ 44.819502] block: unable to load configuration (fstab: Entry not found) [ 44.826056] block: no usable configuration [ 44.831888] mount_root: overlay filesystem has not been fully initialized yet [ 44.840060] mount_root: switching to jffs2 overlay [ 46.180459] urandom-seed: Seed file not found (/etc/urandom.seed) [ 46.309829] procd: - early - [ 46.311724] procd: - watchdog - [ 46.545111] eth0: port 4 lost link [ 46.548473] eth0: port 1 lost link [ 47.048876] procd: - ubus - [ 47.104625] procd: - init - [ 47.807702] kmodloader: loading kernel modules from /etc/modules.d/* [ 47.821928] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH [ 47.832722] NET: Registered protocol family 8 [ 47.835723] NET: Registered protocol family 20 [ 47.851077] sit: IPv6 over IPv4 tunneling driver [ 47.867991] gre: GRE over IPv4 demultiplexor driver [ 47.876575] ip_gre: GRE over IPv4 tunneling driver [ 47.899325] PPP generic driver version 2.4.2 [ 47.919317] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 47.977826] Lantiq (VRX) DSL CPE MEI driver, version 1.5.17.6, (c) 2007-2015 Lantiq Beteiligungs-GmbH & Co. KG [ 47.977826] [ 47.977826] Lantiq CPE API Driver version: DSL CPE API V4.17.18.6 [ 48.034857] [ 48.034857] Predefined debug level: 3 [ 48.072736] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f [ 48.079423] Backport generated by backports.git backports-20160324-13-g24da7d3c [ 48.122182] ip_tables: (C) 2000-2006 Netfilter Core Team [ 48.139003] Infineon Technologies DEU driver version 2.0.0 [ 48.160944] IFX DEU DES initialized (multiblock). [ 48.183138] IFX DEU AES initialized (multiblock). [ 48.191554] IFX DEU ARC4 initialized (multiblock). [ 48.202862] IFX DEU SHA1 initialized. [ 48.209712] IFX DEU MD5 initialized. [ 48.215739] IFX DEU SHA1_HMAC initialized. [ 48.223603] IFX DEU MD5_HMAC initialized. [ 48.234367] nf_conntrack version 0.5.0 (1907 buckets, 7628 max) [ 48.292844] PCI: Enabling device 0000:00:00.0 (0000 -> 0002) [ 48.297309] PCI: Enabling device 0000:01:00.0 (0000 -> 0002) [ 48.304161] owl-loader 0000:01:00.0: Direct firmware load for ath9k-eeprom-pci-0000:01:00.0.bin failed with error -2 [ 48.313365] owl-loader 0000:01:00.0: Falling back to user helper [ 48.338155] PPP MPPE Compression module registered [ 48.348355] NET: Registered protocol family 24 [ 48.357704] PPTP driver version 0.8.5 [ 48.401587] xt_time: kernel timezone is -0000 [ 48.604281] kmodloader: done loading kernel modules from /etc/modules.d/* [ 69.216243] ATM1.0.26 ATM (A1) firmware version 0.24 [ 69.220123] ifxmips_atm: ATM init succeed [ 72.114611] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 72.158259] device eth0.1 entered promiscuous mode [ 72.161790] device eth0 entered promiscuous mode [ 72.200070] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready [ 72.945650] eth0: port 4 got link [ 72.954937] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 73.073847] br-lan: port 1(eth0.1) entered forwarding state [ 73.078167] br-lan: port 1(eth0.1) entered forwarding state [ 73.262726] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready [ 73.861533] IPv6: ADDRCONF(NETDEV_UP): nas0: link is not ready [ 73.942854] eth0: port 1 got link [ 75.078627] br-lan: port 1(eth0.1) entered forwarding state [ 86.951015] enter showtime, cell rate: 0 - 2716, 1 - 2716, xdata addr: 0xa60f0000 [ 86.989369] enter showtime, cell rate: 0 - 2716, 1 - 2716, xdata addr: 0xa60f0000 [ 87.138667] IPv6: ADDRCONF(NETDEV_CHANGE): nas0: link becomes ready [ 89.353868] pppoe-wan: renamed from ppp0 [ 89.436164] owl-loader 0000:01:00.0: fixup device configuration [ 89.442926] pci 0000:01:00.0: [168c:002e] type 00 class 0x028000 [ 89.443041] pci 0000:01:00.0: reg 0x10: [mem 0x1c000000-0x1c00ffff 64bit] [ 89.443244] pci 0000:01:00.0: supports D1 [ 89.443271] pci 0000:01:00.0: PME# supported from D0 D1 D3hot [ 89.443693] pci 0000:01:00.0: BAR 0: assigned [mem 0x1c000000-0x1c00ffff 64bit] [ 89.449895] PCI: Enabling device 0000:01:00.0 (0140 -> 0142) [ 89.511623] ath: phy0: eeprom contains invalid mac address: 00:00:00:00:00:00 [ 89.517435] ath: phy0: random mac address will be used: 86:18:bf:0a:4d:99 [ 89.525716] ath: EEPROM regdomain: 0x8114 [ 89.525742] ath: EEPROM indicates we should expect a country code [ 89.525759] ath: doing EEPROM country->regdmn map search [ 89.525775] ath: country maps to regdmn code: 0x37 [ 89.525791] ath: Country alpha2 being used: DE [ 89.525805] ath: Regpair used: 0x37 [ 89.539684] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 89.544507] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xbc000000, irq=144 [ 99.054960] pppoe-wan: renamed from ppp0 [ 218.025355] pptp-vpn: renamed from ppp1