Flint 2 wont recognize cabel connection

Hello everyone, I'm stuck and hope to find a solution to my problem here!
My Flint 2 ran with firmware 4.6.2. without any problems, now I have the problem that the devices connected by cable are no longer recognized. The devices and cables work perfectly on another router. The Flint no longer recognizes the devices.
Wifi works.
No changes have been made, the router has been running smoothly since February.
I have already done a reset without success. Went to factory settings, without success.
As vpn I used vyprvpn until now without problems, since the reset this also no longer works.
Fiber optic -router AVM Fritzbox-Flint 2.
I hope that all the important points are there and hope for a solution.
Many thanks in advance.

Translated with DeepL.com (free version)

Hi Paul,

please reboot the router, plug out and plugin the cable to your Fritz!Box again and upload/post the logs then.

Does the Fritz!Box still detect the cable?

still the same problem. the computers connected via lan are not recognized.
Wlan works, the connection to fritzbox works.

Sat Sep  7 17:09:56 2024 daemon.err usbmuxd[9224]: [17:09:56.853][3] usbmuxd shutting down
Sat Sep  7 17:09:56 2024 daemon.info gl-repeater[2693]: (repeater.lua:1011) no saved network
Sat Sep  7 17:09:56 2024 daemon.err usbmuxd[9224]: [17:09:56.953][3] Shutdown complete
Sat Sep  7 17:13:49 2024 kern.info kernel: [  282.959373] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Sat Sep  7 17:13:49 2024 daemon.notice netifd: Network device 'eth1' link is down
Sat Sep  7 17:13:49 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sat Sep  7 17:13:49 2024 daemon.notice netifd: wan (6910): udhcpc: received SIGTERM
Sat Sep  7 17:13:49 2024 daemon.notice netifd: wan (6910): udhcpc: unicasting a release of 192.168.178.39 to 192.168.178.1
Sat Sep  7 17:13:49 2024 daemon.notice netifd: wan (6910): udhcpc: sending release
Sat Sep  7 17:13:49 2024 daemon.notice netifd: wan (6910): udhcpc: entering released state
Sat Sep  7 17:13:49 2024 daemon.notice netifd: wan (6910): Command failed: Permission denied
Sat Sep  7 17:13:49 2024 daemon.notice netifd: Interface 'wan' is now down
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Withdrawing address record for 192.168.178.39 on eth1.
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.178.39.
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Interface eth1.IPv4 no longer relevant for mDNS.
Sat Sep  7 17:13:49 2024 daemon.notice netifd: Interface 'wan' is disabled
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Interface eth1.IPv6 no longer relevant for mDNS.
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::9683:c4ff:fea6:f0cf.
Sat Sep  7 17:13:49 2024 daemon.info avahi-daemon[4128]: Withdrawing address record for fe80::9683:c4ff:fea6:f0cf on eth1.
Sat Sep  7 17:13:49 2024 kern.info kernel: [  283.351918] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY]
Sat Sep  7 17:13:49 2024 kern.info kernel: [  283.361427] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/sgmii link mode
Sat Sep  7 17:13:49 2024 daemon.notice netifd: Interface 'wan' is enabled
Sat Sep  7 17:13:49 2024 daemon.warn dnsmasq[9031]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Sat Sep  7 17:13:49 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Sat Sep  7 17:13:49 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Sat Sep  7 17:13:49 2024 kern.debug kernel: [  283.521140] kmwan: Delete node:wan
Sat Sep  7 17:13:57 2024 kern.info kernel: [  291.398266] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
Sat Sep  7 17:13:57 2024 kern.info kernel: [  291.406723] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Sat Sep  7 17:13:57 2024 daemon.notice netifd: Network device 'eth1' link is up
Sat Sep  7 17:13:57 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Sep  7 17:13:57 2024 daemon.notice netifd: Interface 'wan' is setting up now
Sat Sep  7 17:13:57 2024 daemon.notice netifd: wan (11012): udhcpc: started, v1.33.2
Sat Sep  7 17:13:57 2024 daemon.notice netifd: wan (11012): udhcpc: sending discover
Sat Sep  7 17:13:58 2024 daemon.info avahi-daemon[4128]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::9683:c4ff:fea6:f0cf.
Sat Sep  7 17:13:58 2024 daemon.info avahi-daemon[4128]: New relevant interface eth1.IPv6 for mDNS.
Sat Sep  7 17:13:58 2024 daemon.info avahi-daemon[4128]: Registering new address record for fe80::9683:c4ff:fea6:f0cf on eth1.*.
Sat Sep  7 17:14:00 2024 daemon.notice netifd: wan (11012): udhcpc: sending discover
Sat Sep  7 17:14:00 2024 daemon.notice netifd: wan (11012): udhcpc: sending select for 192.168.178.39
Sat Sep  7 17:14:00 2024 daemon.notice netifd: wan (11012): udhcpc: lease of 192.168.178.39 obtained, lease time 864000
Sat Sep  7 17:14:00 2024 daemon.info avahi-daemon[4128]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.178.39.
Sat Sep  7 17:14:00 2024 daemon.info avahi-daemon[4128]: New relevant interface eth1.IPv4 for mDNS.
Sat Sep  7 17:14:00 2024 daemon.info avahi-daemon[4128]: Registering new address record for 192.168.178.39 on eth1.IPv4.
Sat Sep  7 17:14:00 2024 daemon.notice netifd: Interface 'wan' is now up
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain test
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain onion
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain localhost
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain local
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain invalid
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain bind
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using only locally-known addresses for domain lan
Sat Sep  7 17:14:00 2024 daemon.info dnsmasq[9031]: using nameserver 192.168.178.1#53
Sat Sep  7 17:14:00 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Sat Sep  7 17:14:00 2024 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "eth1", "track_mode": "force", "addr_type": 4, "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Sat Sep  7 17:14:00 2024 kern.debug kernel: [  294.480699] [add_dev_config 287]add node success. iface:wan, dev:eth1, ifindex:3
Sat Sep  7 17:15:59 2024 kern.debug kernel: [  412.943278] entrytb_aid_aquire(): found non-occupied aid:4, allocated from:4
Sat Sep  7 17:15:59 2024 kern.warn kernel: [  412.950336] 7986@C13L2,MacTableInsertEntry() 1577: New Sta:dc:53:60:68:f2:f4
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  412.960292] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714:  Recv Assoc from STA - dc:53:60:68:f2:f4
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  412.969594] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ASSOC Send ASSOC response (Status=0)...
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  412.978652] 7986@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  412.984643] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  413.107265] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  413.222425] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  413.229003] 7986@C15L3,WPABuildPairMsg3() 5595: <=== send Msg3 of 4-way
Sat Sep  7 17:15:59 2024 kern.notice kernel: [  413.235612] 7986@C15L3,PeerPairMsg4Action() 6734: ===>Receive msg 4
Sat Sep  7 17:15:59 2024 kern.warn kernel: [  413.247048] 7986@C15L2,PeerPairMsg4Action() 7098: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=1 from dc:53:60:68:f2:f4
Sat Sep  7 17:15:59 2024 kern.warn kernel: [  413.247048]
Sat Sep  7 17:16:00 2024 daemon.info dnsmasq-dhcp[9031]: DHCPREQUEST(br-lan) 192.168.8.115 dc:53:60:68:f2:f4
Sat Sep  7 17:16:00 2024 daemon.info dnsmasq-dhcp[9031]: DHCPACK(br-lan) 192.168.8.115 dc:53:60:68:f2:f4 DESKTOP-DI2RMUV

Could you please describe a bit more what the issue is about?
The log tells us, that the cable connection itself seems to work and link is given.

The GL gots the IP 192.168.178.39

Ok, I've checked everything again. I have 2 devices connected to my Flint via wifi, everything is ok and there are 2 devices, a computer and a Raspberry connected via lan, this device connection no longer works.
I have tried the cables and devices on my fritzbox, everything works fine there.
the Raspberry shows the following -ethO:Link is down.
I hope it is more understandable now.

Did you try all LAN ports of the Flint?

Yes, I have just reconnected, no connection to the 2 devices on lan 2-3-4-5. I have also just tried the WAN/LAN 1, here it recognizes a connection, but it does not connect the 2 devices.

Could you please try to reset the router using the Uboot method?

Firmware is here: GL.iNet download center

OK I'll do my best but it will take some time.

Hello, it took a while. I have tried everything but without success, I can't connect to Uboot. I have tried 2 different laptops, browser Firefox, chrome and edge, tried every connection always with the same result, no connection timeout. I have searched the internert but have not found anything really helpful. Any idea?

Did you set the correct static IP like described in the article?

Yes, 192.168.1.2 and Use browser to visit http://192.168.1.1, this is the Uboot Web UI.

May I know if the Flint 2 downgrade the firmware to 4.6.2, would the LAN ports work?

Hello everyone, I have tried a few things over the last few days, unfortunately without success. Since I could not establish a connection via Uboot, I first updated to 4.6.4 via the local update, then back to 4.6.2, then to 4.5.8 and finally even to 4.5.4. Unfortunately, the result is always the same. I am now back on 4.6.4
Eth0 link is down, wifi works, internet works, only the devices connected to the flint 2 via lan are not recognized.
Could it be a hardware problem?

Translated with DeepL.com (free version)

Hi may I know how about now? The screenshot you post shows the Eth1 and Eth2 work ok in the v4.6.4