Fritz!Box 7520 doesn't respond to Ping on Install

[owrtjiogjhi]

Hello, i am currently trying to install OpenWRT onto my Fritz!Box 7520, it had OpenWRT installed previously but i have since installed Fritz!OS 8.20 (maybe 8.21) and i wanted to get OpenWRT back on now. I have read all the instructions clearly and i had already done this atleast 4 times on multiple boxes. I have tried everything, like:

• Using my Desktop and Laptop
• Using Linux and Windows on my Desktop, Windows on my Laptop
• Trying both 192.168.178.10/24 and 192.168.1.70/24, of course
• Wireshark and tcpdump trying to capture the ARP response
• Adding a static ARP entry
• Trying LAN1 and LAN4 on the box one after another
• On Linux, adding both 192.168.178.10/24 and 192.168.1.70/24, then constantly pinging both while plugging the power cord in
• Downgrading the box to 7.21, it is currently still on 7.21 and i have tried everything listed above with this version
• watch -n 0.1 to check for ARP entries, and ip link status (up/down)
• The LAN cables definitely work, but I've tested a few just for good measure

Bot nothing seems to work, the main problem seems to be that before the OS boots up the box never responds with an ARP reply, the ping command just keeps saying something along the lines of "host unreachable" in both Linux and Windows, and FTP for eva_ramboot will also not work because there isn't even an ARP entry for the box. Is this problem known of have i missed something completely?

[slh]

Nothing says the bootloader needs to respond to ping.

[owrtjiogjhi]

But the Pings also send an ARP request because it's on the same subnet, but the box never replies to it. So FTP (eva_ramboot) also won't work because it doesn't know how to reach the box because there isn't an ARP entry for the LAN IP. Or am i in the wrong here?

[_bernd]

@owrtjiogjhi

watch -n 0.1 to check for ARP entries, and ip link status (up/down)

ip monitor shows various netlink events, which can also show only neighbor aka arp fdb entries.

[wilsonyan]

Fritzbox 4040 flash: FTP connection refused

I had the same issue after using the AVM rescue utility. There is a variable in the bootloader which specifies which ip address the EVA bootloader should listen on. After EVA it will run the regular firmware and listen at 192.168.178.1 while refusing any connection on the ftp port. The key to this is a magic UDP packet sent by your PC which also the AVM rescue utility uses to modify this variable containing the address EVA should listen on. This can be done using a script which is available as …

???

[owrtjiogjhi]

After watching the traffic of the official AVM Recovery tool (7.21), i set my Local IP to 192.168.178.20/24 and it worked this time. This might need to be added to the Wiki, i recovered it a few times via AVM to check if it was a bug but every time it used 192.168.178.20.