EVA Tools and Fritz!Box 7530 #57

MikeJanto · 2023-02-16T12:46:37Z

MikeJanto
Feb 16, 2023

I tried to recover my 7530 with the stock 7.50 image from AVM using EVA tools ( the recovery tool from AVM did not work).
EVA-Discover found the box:

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-Discover.ps1
EVA_IP=192.168.178.1
True

But setting memory size failed as you can see here:

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { BootDeviceFromImage .\FRITZ.Box_7530-07.50.image }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
GETENV memsize
================
DEBUG: Response:
memsize               0x10000000

200 GETENV command successful

================
DEBUG: Memory size found    : 0x10000000 (256 MB)
DEBUG: Memory size used     : 0x08000000 (128 MB)
DEBUG: Image size found     : 0x0238e800
DEBUG: Set memory size to   : 0x05c71800
DEBUG: Set MTD RAM device to: 0x85c71800,0x88000000
DEBUG: Sent
SETENV memsize 0x05c71800
================
DEBUG: Sent
QUIT
================
Exception calling "Invoke" with "0" argument(s): "Setting the new memory size failed."
At C:\Janto\Privat\Openwrt\FB7530\eva_tools\EVA-FTP-Client.ps1:638 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

Do you have any idea, what I could do to either install the image or install openwrt?
Probably I killed the box already :(

PeterPawn · 2023-02-16T13:45:41Z

PeterPawn
Feb 16, 2023
Maintainer

For 7530 try to avoid memory limitation ... use the second argument for BootDeviceFromImage function:

YourFritz/eva_tools/EVA-FTP-Client.ps1

Line 247 in 2f4f935

    
           [Parameter(Mandatory = $False, Position = 1, HelpMessage = 'limit memory size to 128 MB for the uploaded image')][bool]$limitedMemory = $True

2 replies

MikeJanto Feb 16, 2023
Author

Hi PeterPawn,

Thank you for such a quick response. Really appreciated.
I tried to put 0 as a second argument. But still no luck.

PS C:\janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-Discover.ps1
EVA_IP=192.168.178.1
True
PS C:\janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { BootDeviceFromImage .\FRITZ.Box_7530-07.50.image 0 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
GETENV memsize
================
DEBUG: Response:
memsize               0x10000000

200 GETENV command successful

================
DEBUG: Memory size found    : 0x10000000 (256 MB)
DEBUG: Memory size used     : 0x10000000 (256 MB)
DEBUG: Image size found     : 0x0238e800
DEBUG: Set memory size to   : 0x0dc71800
DEBUG: Set MTD RAM device to: 0x8dc71800,0x90000000
DEBUG: Sent
SETENV memsize 0x0dc71800
================
DEBUG: Sent
QUIT
================
Exception calling "Invoke" with "0" argument(s): "Setting the new memory size failed."
At C:\janto\Privat\Openwrt\FB7530\eva_tools\EVA-FTP-Client.ps1:638 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

MikeJanto Feb 16, 2023
Author

This is some additional information I get from the box:

HardwareFeatures:	nand=0x98F1801572,cpu=0x979
HWRevision:		236
ProductID:		Fritz_Box_HW236
SerialNumber:		N16567830627710
annex:			B
autoload:			yes
bootloaderVersion:	1.11581
firstfreeaddress:	0x882540E8
firmware_info:		164.07.50
firmware_version:	avm
flashsize:			nor_size=0MB sflash_size=0KB nand_size=128MB
maca:			DC:15:C8:CD:B4:86
macb:			DC:15:C8:CD:B4:87
macwlan:			DC:15:C8:CD:B4:88
macwlan2:		DC:15:C8:CD:B4:89
macwlan3:		variable not set
macdsl:			DC:15:C8:CD:B4:83
memsize:			0x10000000
mtd0:			0x0,0x2C00000
mtd1:			0xB00000,0xF00000
mtd2:			0x0,0x2C0000
mtd3:			0x2C0000,0xB00000
mtd4:			0xF00000,0x1300000
mtd5:			0x1300000,0x8000000
my_ipaddress:		192.168.178.1
prompt:			Eva_AVM
usb_rndis_mac:	DC:15:C8:CD:B4:85

Will that help to further troubleshoot? Or is the box already kaputt?

PeterPawn · 2023-02-16T19:28:27Z

PeterPawn
Feb 16, 2023
Maintainer

Looks a bit weird ... there's no response to the SETENV command and I'd guess, the cause of your problem is simply a timeout while waiting for the response to this command.

Are you sure, there's no additional software (any "security suite"?) blocking/analyzing FTP sessions/commands?

What happens, if you try to set any other variable's value? firmware_info should be changeable persistently and you may use the SetEnvironmentValue function with it (

YourFritz/eva_tools/EVA-FTP-Client.ps1

Line 122 in 2f4f935

function SetEnvironmentValue {

).

And how did you get all the values in the second listing? If there's a variable not set response, too, it doesn't look like the results from a ReadFile (

YourFritz/eva_tools/EVA-FTP-Client.ps1

Line 443 in 2f4f935

function ReadFile {

) call for env (beside the additional clue from the extra colon after variable names).

3 replies

MikeJanto Feb 17, 2023
Author

@PeterPawn: I somehow can ftp to the box and get all those information:

PS C:\janto\Privat\Openwrt\FB7530\eva_tools> ftp 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
530 not logged in
User (192.168.178.1:(none)): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
ftp> quote GETENV HardwareFeatures
HardwareFeatures      nand=0x98F1801572,cpu=0x979

200 GETENV command successful
ftp> quote GETENV HWRevision
HWRevision            236

200 GETENV command successful
ftp> quote GETENV ProductID
ProductID             Fritz_Box_HW236

200 GETENV command successful
ftp> quote GETENV fimware_info
501 environment variable not set
ftp> quote GETENV firmware_info
firmware_info         164.07.50

200 GETENV command successful
ftp> quote SETENV firmware_info 164.07.00
Connection closed by remote host.
ftp>

ReadFile returns "551 unknown Mediatype"

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { ReadFile temp.txt }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
P@SW
================
DEBUG: Response:
227 Entering Passive Mode (192,168,178,1,27,119)

================
DEBUG: Sent
RETR env
================
DEBUG: Response:
551 unknown Mediatype

================
True

As you proposed I tried to set the firmware_info to something different. And the box is closing the connection. Probably it is now a "read only" box?

MikeJanto Feb 17, 2023
Author

Oh, wait. I can change the firmware_info:

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { SetEnvironmentValue firmware_info 164.07.00 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
SETENV firmware_info 164.07.00
================
DEBUG: Response:
200 SETENV command successful

================
True

And the check with manual ftp to the box provides the evidence:

PS C:\janto\Privat\Openwrt\FB7530\eva_tools> ftp 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
530 not logged in
User (192.168.178.1:(none)): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
ftp> quote GETENV firmware_info
firmware_info         164.07.00

200 GETENV command successful
ftp>

What next?

MikeJanto Feb 17, 2023
Author

I tried for several times now. The SetEnvironmentValue returns false. The box is directly not available (probably rebooting). And if the box is available again, the value firmware_info is correctly set. That is really odd.
Do you have any idea, what I could do?

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { SetEnvironmentValue firmware_info 164.07.50 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
SETENV firmware_info 164.07.50
================
False

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> 
PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { SetEnvironmentValue firmware_info 164.07.00 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
SETENV firmware_info 164.07.00
================
False

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> 
PS C:\Janto\Privat\Openwrt\FB7530\eva_tools> .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { SetEnvironmentValue firmware_info 164.07.50 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
SETENV firmware_info 164.07.50
================
False

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools>

Trying the BootDeviceFromImage is still not working:

PS C:\Janto\Privat\Openwrt\FB7530\eva_tools>  .\EVA-FTP-Client.ps1 -Verbose -Debug -ScriptBlock { BootDeviceFromImage .\FRITZ.Box_7530-07.50.image 0 }
DEBUG: Response:
220 ADAM2 FTP Server ready

================
DEBUG: Sent
USER adam2
================
DEBUG: Response:
331 Password required for adam2

================
DEBUG: Sent
PASS adam2
================
DEBUG: Response:
230 User adam2 successfully logged in

================
DEBUG: Sent
SYST
================
DEBUG: Response:
215 AVM EVA Version 1.11581 0x0 0x46409

================
DEBUG: Sent
GETENV memsize
================
DEBUG: Response:
memsize               0x10000000

200 GETENV command successful

================
DEBUG: Memory size found    : 0x10000000 (256 MB)
DEBUG: Memory size used     : 0x10000000 (256 MB)
DEBUG: Image size found     : 0x0238e800
DEBUG: Set memory size to   : 0x0dc71800
DEBUG: Set MTD RAM device to: 0x8dc71800,0x90000000
DEBUG: Sent
SETENV memsize 0x0dc71800
================
DEBUG: Sent
QUIT
================
Exception calling "Invoke" with "0" argument(s): "Setting the new memory size failed."
At C:\Janto\Privat\Openwrt\FB7530\eva_tools\EVA-FTP-Client.ps1:638 char:21
+                     $ScriptBlock.Invoke()
+                     ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

PeterPawn · 2023-02-17T16:53:01Z

PeterPawn
Feb 17, 2023
Maintainer

Try another computer/OS ... I still bet, there's some software installed, which leads to this erroneous behavior.

There's no obvious reason, why a box should reboot after issuing a SETENV command to it (neither if the variable name is wrong, nor the new value) - and if it continues to reboot, you'll not be able to use BootDeviceFromImage, 'cause this is a more complex process and NEEDS to use some SETENV commands, before the image data can be uploaded.

You have to solve this SETENV problem first ... and my best guess is (as mentioned above) a problem with the used equipment.

0 replies

PeterPawn · 2023-02-21T16:56:24Z

PeterPawn
Feb 21, 2023
Maintainer

Any news?

2 replies

MikeJanto Feb 22, 2023
Author

I got a raspberry and I'll try to connect the box directly to the raspberry pi. I'll update you shortly here. And sorry for the late answer. I was somehow frustrated and I took some pause. But now I'll try again....

MikeJanto Feb 23, 2023
Author

@PeterPawn: I am afraid that we have no luck. I could connect to the fb and do the ftp to the box:

pi@RASPI2:~/Openwrt $ ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
64 bytes from 192.168.178.1: icmp_seq=1 ttl=250 time=0.434 ms
64 bytes from 192.168.178.1: icmp_seq=2 ttl=250 time=0.360 ms
64 bytes from 192.168.178.1: icmp_seq=3 ttl=250 time=0.421 ms
^C
--- 192.168.178.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2063ms
rtt min/avg/max/mdev = 0.360/0.405/0.434/0.032 ms
pi@RASPI2:~/Openwrt $ ftp 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
Name (192.168.178.1:pi): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
Remote system type is AVM.
ftp> quote GETENV firmware_info
firmware_info         164.07.50
ftp> quote SETENV firmware_info 164.07.00

ftp> quote GETENV firmware_info
200 GETENV command successful
ftp> quote GETENV firmware_info

    

421 Service not available, remote server has closed connection
ftp> 
ftp> 
ftp> 
ftp> open 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
Name (192.168.178.1:pi): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
Remote system type is AVM.
ftp> quote GETENV firmware_info
firmware_info         164.07.00
ftp> quote SETENV firmware_info 164.07.50

ftp> quote GETENV firmware_info
200 GETENV command successful
ftp> quote GETENV firmware_info

421 Service not available, remote server has closed connection
ftp> 
ftp> open 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
Name (192.168.178.1:pi): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
Remote system type is AVM.
ftp> quote GETENV firmware_info
firmware_info         164.07.50
ftp>

Changing firmware_info does work, but not really good. The box seems to restart.

Here is the tcp communication:

pi@RASPI2:~ $ sudo tcpdump -i eth0
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
17:56:35.539213 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
17:56:35.579377 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:56:35.759257 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
17:56:36.315628 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:56:37.384915 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:56:38.602323 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:56:40.318283 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:56:40.605455 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
17:56:40.629280 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
17:56:40.705750 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:56:40.876251 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:56:41.127174 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:56:41.378140 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:56:41.578354 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:56:41.579155 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
17:56:41.705623 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:56:42.607679 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
17:56:42.799434 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:56:43.706084 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:56:44.319370 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:56:45.021099 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:56:47.707750 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:56:48.323695 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:56:55.708579 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:57:05.179257 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:57:05.179562 ARP, Reply 192.168.178.1 is-at dc:15:c8:cd:b4:86 (oui Unknown), length 46
17:57:05.179608 IP 192.168.178.10.54870 > 192.168.178.1.ftp: Flags [P.], seq 3842937322:3842937354, ack 5840, win 64033, length 32: FTP: SETENV firmware_info 164.07.00
17:57:05.182253 IP 192.168.178.1.ftp > 192.168.178.10.54870: Flags [R], seq 5840, win 23040, length 0
17:57:11.709783 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:57:21.517614 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [S], seq 3630096715, win 64240, options [mss 1460,sackOK,TS val 38742096 ecr 0,nop,wscale 7], length 0
17:57:21.517971 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [S.], seq 46083, ack 3630096716, win 23040, options [mss 1440], length 0
17:57:21.518102 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 1, win 64240, length 0
17:57:21.522032 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [.], seq 1:29, ack 1, win 23040, length 28: FTP: 220 ADAM2 FTP Server ready
17:57:21.522095 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 29, win 64212, length 0
17:57:24.985026 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 1:13, ack 29, win 64212, length 12: FTP: USER adam2
17:57:24.985418 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], ack 13, win 23028, length 0
17:57:24.985489 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], seq 29:62, ack 13, win 23028, length 33: FTP: 331 Password required for adam2
17:57:24.985528 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 62, win 64179, length 0
17:57:27.629001 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 13:25, ack 62, win 64179, length 12: FTP: PASS adam2
17:57:27.629400 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], ack 25, win 23028, length 0
17:57:27.629469 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], seq 62:101, ack 25, win 23028, length 39: FTP: 230 User adam2 successfully logged in
17:57:27.629517 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 101, win 64140, length 0
17:57:27.629753 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 25:31, ack 101, win 64140, length 6: FTP: SYST
17:57:27.630052 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], ack 31, win 23034, length 0
17:57:27.630114 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], seq 101:142, ack 31, win 23034, length 41: FTP: 215 AVM EVA Version 1.11581 0x0 0x46409
17:57:27.679189 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 142, win 64099, length 0
17:57:31.139519 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 31:53, ack 142, win 64099, length 22: FTP: GETENV firmware_info
17:57:31.140076 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], ack 53, win 23018, length 0
17:57:31.140143 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [P.], seq 142:208, ack 53, win 23018, length 66: FTP: firmware_info         164.07.00
17:57:31.140179 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [.], ack 208, win 64033, length 0
17:57:43.710522 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:57:53.439717 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:57:53.659202 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:57:54.089212 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:57:54.939195 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:57:56.699204 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:58:00.139197 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:58:07.259226 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:58:12.299197 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:13.339164 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:14.379185 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:21.339226 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:22.379171 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:23.419210 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:34.779276 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:35.819184 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:36.859205 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:47.712187 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:58:48.219255 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:49.259178 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:58:50.299187 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:01.659242 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:02.699184 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:03.739172 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:15.099233 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:16.139180 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:17.179169 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:37.689362 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
17:59:37.739618 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:59:37.817233 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:59:38.699252 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
17:59:38.762406 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:59:40.646459 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
17:59:41.818881 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:59:42.648591 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
17:59:42.679222 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
17:59:42.750420 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:59:42.900861 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:59:43.151904 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:59:43.402589 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
17:59:43.603520 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:59:43.739200 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
17:59:43.750753 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:59:44.651060 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
17:59:44.804429 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:59:45.751767 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:59:45.820287 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:59:46.707626 IP6 fe80::fd24:b53e:14b9:7818.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:59:47.004247 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
17:59:49.753049 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:59:49.824681 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
17:59:55.419243 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:55.419534 15:c8:cd:b4:86:08 (oui Unknown) > 27:eb:6e:dc:ea:dc (oui Unknown), ethertype NS (0x0600), length 60: 
	0x0000:  0108 0006 0400 02dc 15c8 cdb4 86c0 a8b2  ................
	0x0010:  01b8 27eb 6edc eac0 a8b2 0a00 0000 0000  ..'.n...........
	0x0020:  0000 0000 0000 0000 0000 0000 0000       ..............
17:59:56.459183 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
17:59:56.459483 ARP, Reply 192.168.178.1 is-at dc:15:c8:cd:b4:86 (oui Unknown), length 46
17:59:56.459534 IP 192.168.178.10.58200 > 192.168.178.1.ftp: Flags [P.], seq 53:85, ack 208, win 64033, length 32: FTP: SETENV firmware_info 164.07.50
17:59:56.462269 IP 192.168.178.1.ftp > 192.168.178.10.58200: Flags [R], seq 46291, win 23040, length 0
17:59:57.755794 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:00:10.586988 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [S], seq 2886850240, win 64240, options [mss 1460,sackOK,TS val 38911165 ecr 0,nop,wscale 7], length 0
18:00:10.587322 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [S.], seq 47217, ack 2886850241, win 23040, options [mss 1440], length 0
18:00:10.587425 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 1, win 64240, length 0
18:00:10.592806 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [.], seq 1:29, ack 1, win 23040, length 28: FTP: 220 ADAM2 FTP Server ready
18:00:10.592879 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 29, win 64212, length 0
18:00:13.030653 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [P.], seq 1:13, ack 29, win 64212, length 12: FTP: USER adam2
18:00:13.031031 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], ack 13, win 23028, length 0
18:00:13.031104 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], seq 29:62, ack 13, win 23028, length 33: FTP: 331 Password required for adam2
18:00:13.031144 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 62, win 64179, length 0
18:00:13.756168 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:00:14.810635 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [P.], seq 13:25, ack 62, win 64179, length 12: FTP: PASS adam2
18:00:14.811000 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], ack 25, win 23028, length 0
18:00:14.811071 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], seq 62:101, ack 25, win 23028, length 39: FTP: 230 User adam2 successfully logged in
18:00:14.811111 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 101, win 64140, length 0
18:00:14.811309 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [P.], seq 25:31, ack 101, win 64140, length 6: FTP: SYST
18:00:14.811608 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], ack 31, win 23034, length 0
18:00:14.811648 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], seq 101:142, ack 31, win 23034, length 41: FTP: 215 AVM EVA Version 1.11581 0x0 0x46409
18:00:14.859276 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 142, win 64099, length 0
18:00:19.953002 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [P.], seq 31:53, ack 142, win 64099, length 22: FTP: GETENV firmware_info
18:00:19.953591 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], ack 53, win 23018, length 0
18:00:19.953664 IP 192.168.178.1.ftp > 192.168.178.10.51278: Flags [P.], seq 142:208, ack 53, win 23018, length 66: FTP: firmware_info         164.07.50
18:00:19.953709 IP 192.168.178.10.51278 > 192.168.178.1.ftp: Flags [.], ack 208, win 64033, length 0
18:00:45.757281 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

I also try to install openwrt for 7530:

pi@RASPI2:~/Openwrt $ ls
eva_discover.sh  eva_get_environment.sh  eva_ramboot.py  uboot-fritz7530.bin
pi@RASPI2:~/Openwrt $ sudo python eva_ramboot.py --offset 0x85000000 192.168.178.1 uboot-fritz7530.bin 
> SETENV memsize 0x00080000

Traceback (most recent call last):
  File "/home/pi/Openwrt/eva_ramboot.py", line 39, in <module>
    adam('SETENV memsize 0x%08x'%(addr))
  File "/home/pi/Openwrt/eva_ramboot.py", line 32, in adam
    resp = ftp.sendcmd(cmd)
  File "/usr/lib/python3.9/ftplib.py", line 279, in sendcmd
    return self.getresp()
  File "/usr/lib/python3.9/ftplib.py", line 242, in getresp
    resp = self.getmultiline()
  File "/usr/lib/python3.9/ftplib.py", line 228, in getmultiline
    line = self.getline()
  File "/usr/lib/python3.9/ftplib.py", line 210, in getline
    line = self.file.readline(self.maxline + 1)
  File "/usr/lib/python3.9/socket.py", line 704, in readinto
    return self._sock.recv_into(b)
ConnectionResetError: [Errno 104] Connection reset by peer
pi@RASPI2:~/Openwrt $

That does not look good as well. Here is the corresponding tcp dump:

18:03:14.381791 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [.], seq 1:29, ack 1, win 23040, length 28: FTP: 220 ADAM2 FTP Server ready
18:03:14.381819 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [.], ack 29, win 64212, length 0
18:03:14.382037 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 1:13, ack 29, win 64212, length 12: FTP: USER adam2
18:03:14.382281 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [P.], ack 13, win 23028, length 0
18:03:14.382311 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [P.], seq 29:62, ack 13, win 23028, length 33: FTP: 331 Password required for adam2
18:03:14.382417 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 13:25, ack 62, win 64179, length 12: FTP: PASS adam2
18:03:14.382662 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [P.], ack 25, win 23028, length 0
18:03:14.382676 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [P.], seq 62:101, ack 25, win 23028, length 39: FTP: 230 User adam2 successfully logged in
18:03:14.382985 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:14.599178 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:15.029217 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:15.899245 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:17.659218 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:19.419176 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:20.459179 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:21.099181 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:03:21.499181 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:27.899266 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:28.939190 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:29.979181 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:34.619242 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:35.659170 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:36.699175 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:41.339242 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:42.379188 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:43.419177 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:48.059238 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:49.099176 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:50.139185 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:54.779240 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:55.819179 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:56.859188 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:03:57.759633 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:04:01.499231 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:02.539190 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:03.579174 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:08.219245 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:09.259166 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:10.299207 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:14.939231 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:15.979178 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:17.019233 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:21.659238 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:22.699175 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:23.739177 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:28.379262 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:29.419192 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:30.459191 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:35.099274 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:36.139208 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:37.179208 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:41.819254 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:42.859173 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:43.899188 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:04:54.649287 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
18:04:54.679602 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:04:55.419208 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
18:04:55.516997 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:04:55.873648 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:04:57.326283 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:04:59.328698 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
18:04:59.349259 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
18:04:59.430226 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:04:59.461249 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:04:59.518114 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:04:59.710431 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:04:59.960710 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:05:00.161420 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:05:00.299202 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
18:05:00.430740 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:05:01.242035 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:05:01.331132 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
18:05:01.979254 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:02.431669 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:05:03.019171 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:03.322966 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:05:03.519052 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:05:04.059180 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:06.432593 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:05:07.522053 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:05:08.699272 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:09.739168 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:10.779176 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:14.434112 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:05:15.419260 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:16.459209 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:17.499193 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:22.139249 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:23.179226 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:24.219197 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:28.859242 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:29.899209 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:30.434485 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:05:30.939212 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:35.579242 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:36.619190 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:37.659178 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:42.299252 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:43.339177 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:44.379173 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:49.019219 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:50.059214 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:51.099194 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:55.739265 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:56.779169 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:05:57.819204 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:02.435169 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:06:02.459198 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:03.499184 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:04.539172 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:09.179295 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:10.219164 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:11.259210 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:15.899269 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:16.939178 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:17.979146 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:19.941029 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:21.019173 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:22.059171 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:23.099896 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:24.139166 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:25.179160 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:34.489281 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
18:06:34.539686 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:06:35.079187 IP6 fe80::fd24:b53e:14b9:7818 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
18:06:35.339011 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:06:36.289212 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:06:38.025145 ARP, Request who-has 192.168.178.10 tell 0.0.0.0, length 28
18:06:39.340700 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:06:40.027341 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
18:06:40.049248 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
18:06:40.128029 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:06:40.189309 IP 192.168.178.10 > 224.0.0.22: igmp v3 report, 1 group record(s)
18:06:40.273752 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:06:40.523694 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:06:40.774236 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [3q] [4n] ANY (QM)? 8.1.8.7.9.b.4.1.e.3.5.b.4.2.d.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? RASPI2.local. ANY (QM)? 10.178.168.192.in-addr.arpa. (209)
18:06:40.975348 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:06:41.128484 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:06:42.030420 ARP, Request who-has 192.168.178.10 tell 192.168.178.10, length 28
18:06:42.171622 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:06:43.099267 ARP, Request who-has 192.168.178.1 tell 192.168.178.10, length 28
18:06:43.099577 ARP, Reply 192.168.178.1 is-at dc:15:c8:cd:b4:86 (oui Unknown), length 46
18:06:43.099625 IP 192.168.178.10.42614 > 192.168.178.1.ftp: Flags [P.], seq 25:52, ack 101, win 64140, length 27: FTP: SETENV memsize 0x00080000
18:06:43.102482 IP 192.168.178.1.ftp > 192.168.178.10.42614: Flags [R], seq 23656, win 23040, length 0
18:06:43.129487 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:06:43.341201 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:06:44.367522 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0*- [0q] 4/0/0 (Cache flush) PTR RASPI2.local., (Cache flush) A 192.168.178.10, (Cache flush) PTR RASPI2.local., (Cache flush) AAAA fe80::fd24:b53e:14b9:7818 (191)
18:06:47.130712 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
18:06:47.345440 IP6 fe80::fd24:b53e:14b9:7818 > ip6-allrouters: ICMP6, router solicitation, length 16
18:06:55.131943 IP 192.168.178.10.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)

Will that help to locate the issue? I am really lost....

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

EVA Tools and Fritz!Box 7530 #57

{{title}}

Replies: 4 comments 7 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

EVA Tools and Fritz!Box 7530 #57

MikeJanto Feb 16, 2023

Replies: 4 comments · 7 replies

PeterPawn Feb 16, 2023 Maintainer

MikeJanto Feb 16, 2023 Author

MikeJanto Feb 16, 2023 Author

PeterPawn Feb 16, 2023 Maintainer

MikeJanto Feb 17, 2023 Author

MikeJanto Feb 17, 2023 Author

MikeJanto Feb 17, 2023 Author

PeterPawn Feb 17, 2023 Maintainer

PeterPawn Feb 21, 2023 Maintainer

MikeJanto Feb 22, 2023 Author

MikeJanto Feb 23, 2023 Author

MikeJanto
Feb 16, 2023

Replies: 4 comments 7 replies

PeterPawn
Feb 16, 2023
Maintainer

MikeJanto Feb 16, 2023
Author

MikeJanto Feb 16, 2023
Author

PeterPawn
Feb 16, 2023
Maintainer

MikeJanto Feb 17, 2023
Author

MikeJanto Feb 17, 2023
Author

MikeJanto Feb 17, 2023
Author

PeterPawn
Feb 17, 2023
Maintainer

PeterPawn
Feb 21, 2023
Maintainer

MikeJanto Feb 22, 2023
Author

MikeJanto Feb 23, 2023
Author