OpenWrt on FritzBox WLAN 3370

Installing and Using OpenWrt
1

Hello,
i am trying to install OpenWrt on a FritzBox WLAN 3370 as described on https://openwrt.org/toh/avm/fritz.box.wlan.3370.

After figuring out, that i have one with a Hynix Flash, i downloaded openwrt-19.07.2-lantiq-xrx200-avm_fritz3370-rev2-hynix-squashfs-eva-filesystem/kernel.bin from here:
http://downloads.openwrt.org/releases/19.07.2/targets/lantiq/xrx200/
Although the related device page is saying that 18.06.8 is the current release i think that's the right one, because in the release folder of 18.06.8 there is only a sysupgrade file.

But then in the installation routine (with LAN cable) i stumbled across some things, i'm not really sure how to deal with. I resetted to factory settings before.

  1. I wasn't able to connect to the device within 5 seconds after powering up. I had to wait longer, but the box doesn't seem to reset after 30 seconds, so i ignored this one.
  2. When issuing the first command (quote USER adam2) in ftp the response is "230 User @SkipAuthFromHomenetwork logged in." Consequently the command "quote PASS adam2" also failed: "503 Login with USER first." I decided to keep this in mind, but go further. At least it seems that i'm already authenticated, so not that bad.
  3. When issuing "quote SETENV linux_fs_start 0" the output is: "500 'SETENV linux_fs_start 0': command not understood." I don't know what this means. Should i proceed or is there something wrong in the sequence before?

I'm doing all this on Kubuntu 18.04.4.

2

I suspect you are not talking to the bootloader, but to the FTP server in a running FritzOS.
The FTP command transcript should reveal if this is the case. Look for

220 ADAM2 FTP Server ready
1 Like
3

Thanks, yes, you are right. Finally i was able to flash OpenWrt with the help of a script called eva_discover (found the link here: https://forum.openwrt.org/t/serial-with-fritzbox-3370-how-to-install/39640/6 ).
I'm sure that it was successfull, because yesterday i was in the graphical configuration interface.

But today i'm not able to access it for whatever reason. I'm quite sure, but i can't guarantee that i didn't make a mistake while configuring the device, it was late.
So today, i try to enable failsafe mode. I press the "WLAN" button during startup and the power led is flashing red and fast. Do you know if this is really the failsafe mode? The device should open up an ssh server listening on 192.168.1.1 when in failsafe mode, right?

4

Sounds good. Now set your PC to the static address 192.168.1.2/24 and try to connect with ssh.

5

This is not working. This is what i've done.

blackknight@apollo:~$ sudo service network-manager stop
blackknight@apollo:~$ ifconfig
enp0s10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::bfc2:c43c:5a5d:2be9  prefixlen 64  scopeid 0x20<link>
        ether 00:23:54:38:19:f4  txqueuelen 1000  (Ethernet)
        RX packets 11050  bytes 9422422 (9.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8016  bytes 1516987 (1.5 MB)
        TX errors 36  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 853  bytes 70645 (70.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 853  bytes 70645 (70.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

blackknight@apollo:~$ sudo ifconfig enp0s10 192.168.1.2
blackknight@apollo:~$ ifconfig
enp0s10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.2  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::bfc2:c43c:5a5d:2be9  prefixlen 64  scopeid 0x20<link>
        ether 00:23:54:38:19:f4  txqueuelen 1000  (Ethernet)
        RX packets 11050  bytes 9422422 (9.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8032  bytes 1519881 (1.5 MB)
        TX errors 36  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 866  bytes 71526 (71.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 866  bytes 71526 (71.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

blackknight@apollo:~$ ssh 192.168.1.1
ssh: connect to host 192.168.1.1 port 22: No route to host
blackknight@apollo:~$ ssh 192.168.1.1
ssh: connect to host 192.168.1.1 port 22: No route to host
blackknight@apollo:~$ ssh 192.168.1.1
ssh: connect to host 192.168.1.1 port 22: No route to host
blackknight@apollo:~$ ssh 192.168.1.1
ssh: connect to host 192.168.1.1 port 22: No route to host

I tried it with every LAN port of the device, therefore four ssh commands. The cable is OK, i've tested it with two other devices.The cable is connected directly between my computer and the FritzBox.

Do you have any idea why this is not working? Even pinging is not possible.

blackknight@apollo:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=3 Destination Host Unreachable
From 192.168.1.2 icmp_seq=4 Destination Host Unreachable