Turris MOX blinks twice for first run setup but is not available at 192.168.1.1

After patching newest fw with rescue mode 6 my mox will start and double blinking shows me it is in 1st config mode.
So i managed my ethernet port to add an static adress at 192.168.1.202/24.
But the mox is not available on any of the hw ports with ip 192.168.1.1.
I found with tcpdump the mox is reqesting ip with dhcp. After connected my computer and the mox to my network it gains a ip from my old router an was available on the given address. But I wonder me that another dhcp server is needed to connect the mox 1st time.

This depends on your MOX configuration: MOX - Turris Documentation .

Yea, I know. I have tried also only use the base module although with 8 port lan extension and with full config with sfp module.
With base only module I connected my workstation to the base lan port, with 8port lan extenison to different of the extension and with sfp to both, but on all there is the same problem: no 192.168.1.1 is available. Only if I connect them to a dhcp serviced network the mox gains a ip from the dhcp so i can access the router so I wonder me why it is not acting as like described in the manual?

If MOX has just one Ethernet port it is LAN
If MOX has SFP, SFP is WAN and the rest of ports is LAN (including Ethernet port next to the power supply on MOX A)
If it has switch(es) and no SFP, then all ports in switch are LAN and the port next to the power source on MOX A is WAN

Here is a tcpdump after fresh restarting the mox only connected to my workstations ether port on mox 8-port-LAN extension which is blinking twice:

12:33:15.162840 IP6 fe80::127b:44ff:fe93:ad96 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:15.658839 IP6 fe80::127b:44ff:fe93:ad96 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:26.618856 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:26.642915 IP6 fe80::127b:44ff:fe93:ad96 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:26.918940 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:26.922837 IP6 fe80::127b:44ff:fe93:ad96 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:27.168880 IP6 :: > ff02::1:ff00:c3eb: ICMP6, neighbor solicitation, who has fe80::da58:d7ff:fe00:c3eb, length 32
12:33:27.178862 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
12:33:28.249102 IP6 fe80::da58:d7ff:fe00:c3eb > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
12:33:28.278981 IP6 fe80::da58:d7ff:fe00:c3eb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
12:33:28.759069 IP6 fe80::da58:d7ff:fe00:c3eb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
12:33:29.057015 IP6 fe80::da58:d7ff:fe00:c3eb > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
12:33:30.009114 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:33.079444 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:36.179767 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:39.270056 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:42.350325 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
12:33:44.746997 IP6 fe80::127b:44ff:fe93:ad96 > ff02::2: ICMP6, router solicitation, length 16
12:33:45.440542 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from d8:58:d7:00:c3:eb, length 300
…

It looks for me that the mox is asking for a IP via dhcp request on the 8- lan port extension.

Also I checked the LAN port on base module which not shows such dhcp requests.

If I check the SFP 1GB port there is no connection possible for the moment so maybe there is a more serious problem on this extension. I will remov it to make sure that this is not the base of all problems.

Hello, I’m not further sure what I did by the way it was possible for me to configure the mox with help to the ttl port.
It looks like I have bricked my MOX E 8 port lan extension. The Problem was the antenna cable from my second wlan card which was layed through the mox e extension has to been broken from the antenna so it free floated to the E extension and made some short cuts with there leaded end.
After removing the mox e extension the most configure problems are gone.

After configuring most of my mox I registred that the mox is still blinking twice like I mean the first config was not finished succesfully. Is this normal? How can I change it so the led will show the router is acting normal?