No response from any ethernet port (flint2)

My setup is:

xfinity modem/router (bridge mode) –> flint2 (v4.8.2)

All the clients are wifi.

On Sunday I noticed that the drive in the USB port wasn’t responding so I SSH’d in and saw I/O errors. I couldn’t unmount (# umount /dev/sda1) so rebooted.

The router rebooted but I had no internet connection. The status page said ‘no cable connected’ - the internet was working up until I rebooted.

I powered everything off, then powered the modem on, then the router but got the same ‘no cable connected’ response.

I tried WAN and LAN/WAN port - same problem

I connected my laptop to one of the other LAN ports and it didn’t serve out an IP. My phone could connect with wifi though. Tried the other LAN ports and none of them would give an IP.

I tried factory reset - same problem.

I tried a uboot reload but I couldn’t reach 192.168.1.1 after setting my laptop IP to 192.168.1.2 so I let it boot up and then downgraded to 4.7.7

Same problem with 4.7.7. It won’t serve out an IP from any LAN port. It’s like all the ports are totally dead but everything else is OK (wifi, GUI, SSH)

Is there anything else to try before I request an RMA replacement?

Isn’t the Flint 2’s default IP 192.168.8.1 after a factory reset? that would cause the Uboot issue, only thing that comes straight to mind

It is normally 192.168.8.1 but I wasn’t sure if uboot ran its own stripped down web server. The directions specifically said to use 192.168.1.2 and to connect to 192.168.1.1

I’ll try 192.168.8.1 tomorrow.

You can try a other network cable.

For u-boot you first hold reset and then you put in the power coord, then you need to specify on the 192.168.1.1/24 range for a static ip, where 192.168.1.1 is gateway.

Make sure to do this on a non 2.5gb port, lan2-lan5.

also remove any network switch and any other connected network cables, you want to try a direct connection to ensure no unexpected effects of stp version flavours/mixing occurs, this can also make a router unaccessible and a network slow.

Otherwise it sound to me it is broken.

Hi

You can refer to our debrick guide, which provides specific steps for flashing firmware from U-boot.
What should I do if my router is bricked - GL.iNet Router Docs 4

Yes, U-boot runs its own simple HTTP server, and you should use 192.168.1.2 to access 192.168.1.1.

If flashing the firmware via u-boot also doesn't help, please email [email protected] to get after-sales support.

I know my original cable was working because it’s now being used with my old router connecting to the modem. Tested the new cable by SSHing into the replacement router (running openwrt 24.10) and saw the physical connection reported in dmesg.
When I boot up on the flint2 I can SSH in via the wifi connection but plugging a cable in registers nothing in dmesg so I’m pretty sure now that this is a hardware issue.

That debrick guide is the one I followed. I saw the 6 flashes followed by solid LED but just can’t get anything from any of the LAN ports (and to confirm, I was using 2 through 5)
I’ll send the email - thanks.