Flint2 Ports issue . Linking with 100 mbps

Routers
1

I got less than 2 months ago a Flint 2 and I connected it to my ISP's Switch. First couple of weeks it was linking with 1Gbit to my Gbit devices and then poof it stopped, it could only speed to 100 Mbps. I spent hours going through the forum and tried all the suggestions I could read from staff and members. Renegotiating and forcing links (which makes ports unusuable and have to reboot), trying different cables (bought multiple cables cat6 and cat7) and connecting my Gbit devices directly to router (still showing speeds of 100mbps). Nothing helped. I then couldn't be bothered claiming a warranty claim as I also needed the internet for work, thus I moved to the second port (Lan1) and enabled it as WAN. It connected fine, 1000 mbps and could enjoy my ISPs 1Gbit down and up. So I told myself since it works and I dont need dual wan, no biggie. Fast forward just 1 month later and again the same issue. Now out of nowhere the speed is on second wan(lan1) is also 100 mbps. AGAIN, the same troubleshooting. Nothing helped, I even reset the router itself in case it was a software issue despite not changing anything other than the names of wifi.

I keep seeing posts with similar problems and all i can think is that there's a serious hardware issue with the ports. What else do I need to try? I am tired :expressionless_face:

Running on latest firmware. Version4.7.7

2

Hmm, how do you see the negotiation rate?, is it directly on the Flint 2 or on a device connected to the Flint 2?

Between Flint 2 and isp switch the negotiation rate is normal?

If I read your message, i would think the isp switch is doing bad things, especially since you said you have tried multiple cables.

3

In my case it was a bad cable that forced the WAN on my Slate AX to 100 Mbps. A quick swap fixed that.

It's a bit of a stretch but it could be dust/buildup on the physical ports not keeping a clean electrical signal. I find it your comment more compelling.

@tired100

logread -e netifd should turn up some details when it's happening at least.

4

OP. This might sound crazy, but do have an LED lamp near your router? Or maybe high power draw electronics like a subwoofer or electric fireplace?

I've had experience with those causing massive packet loss on routers, extenders and set top boxes.

1 Like
5

Also having a cable not connected to any device but on the switch could sometimes cause very weird things on other ports.

I see this happening on a Zyxel GS1900-8hp the next port keeps spamming dhcp ACKS and requests.

6

Thank you everyone for your ideas and feedback.

I have bought 5 cables in total since this problem persisted. All of them with shielded pairs, different companies, Cat 6 and 7. I have spent more money than I should. Tried with different power sockets, without any cables connected to the rest of the ports, with and without surge/voltage protector, without any LEDS or any electronics around it etc etc All the ports are very clean, I only got it 2 months ago. The house is not dusty at all.

The cables are fine. I am currently using my older routers which work fine. It's only this Flint2 unfortunately. I have tried forcing the links, turning off renegotiation, ruled out PHY “downshift” or EEE quirks: etc. Nothing helped. I think it's just a defective device at this point.

root@GL-MT6000:~# logread -e netifd
Mon Aug  4 19:12:02 2025 daemon.notice netifd: bridge 'br-lan' link is up
Mon Aug  4 19:12:02 2025 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Aug  4 19:12:04 2025 daemon.notice netifd: Wireless device 'mt798611' is now up
Mon Aug  4 19:12:09 2025 daemon.notice netifd: Network device 'ra0' link is up
Mon Aug  4 19:12:14 2025 daemon.notice netifd: Wireless device 'mt798612' is now up
Mon Aug  4 19:12:14 2025 daemon.notice netifd: Network device 'rax0' link is up
Mon Aug  4 19:12:46 2025 daemon.notice netifd: Network device 'lan3' link is up
Mon Aug  4 19:13:40 2025 daemon.notice netifd: Network device 'lan3' link is down
Mon Aug  4 19:13:43 2025 daemon.notice netifd: Network device 'lan2' link is up
Mon Aug  4 19:14:28 2025 daemon.notice netifd: Network device 'lan2' link is down
Mon Aug  4 19:14:36 2025 daemon.notice netifd: Network device 'lan1' link is up

root@GL-MT6000:~# ethtool lan1
Settings for lan1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 7
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes
root@GL-MT6000:~# ethtool eth0
Settings for lan1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 7
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes


root@GL-MT6000:~# ethtool lan2
Settings for lan2:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

root@GL-MT6000:~# ethtool lan3
Settings for lan3:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

root@GL-MT6000:~# ethtool lan2
Settings for lan2:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes
1 Like
7

I may think what is going on here :wink:

since you mentoid EEE, older op24 firmware may has issues, from what I have seen on github ( I couldn't 123 remember the exact issue at hand but it involved gro and eee ).

can you install ethtool if not installed yet, and use:

ethtool --set-eee lan3 eee off where lan3 is port 3.

^ if this doesn't work, can you try:

ethtool -K lan3 gro off gso off tso off

don't forget to issue a ifdown lan3 && ifup lan3 after using ethtool command.

note the commands don't persist reboot, but it is a fast test we can then report it to the staff :wink:

8

EEE isn't in use. :slight_smile:

root@GL-MT6000:~# ethtool --show-eee eth1
EEE Settings for eth1:
        EEE status: enabled - inactive
        Tx LPI: disabled
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  100baseT/Full
                                    1000baseT/Full
        Link partner advertised EEE link modes:  Not reported
9

Also to note again. Direct connection from Gbit able laptops to WAN ports confirm only 100 mbps links. @bruce any advise would be much appreciated.

10

Try to push the connector on the WAN port very firmly.

11

It doesn't need to be forced; OP is using new cables. That click is all that should be really needed otherwise the physical ports are at fault regardless of the negotiated speeds.

I'm starting to think you're right. IDK the port naming/labels in the GL GUI/LuCI for that model. Is it just on the 2 x 2.5G or is it also along the 4 x 1G ports? The 2.5Gs are on a seperate internal switch/chipset, IIRC.

1 Like
12

Hi,

Sorry for this the user experience.

Given the current technical situation, there may be some compatibility issues with 2.5Gbps in different devices/PHY.

Please make some of the following attempts:

  1. Re-plug the network cable multiple times, (like five times), and then check whether to negotiate 1Gbps.

  2. With this command to fix the rate for WAN1 of Flint2:
    ethtool -s eth1 speed 1000 duplex full autoneg off

13

Hey Bruce thank you for your reply.
This command is the first one trying from reading previous posts. Unfortunately it only breaks the link and makes it unresponsive and a device reboot is required (normal behaviour for Gigabit). Unplugging and plugging the cables multiple times does not do anything as well.

I have also tried to enforce 1 Gbit and keeping the negotiation on to no effect.

ethtool -s eth0 autoneg on advertise 0x800

I believe since the laptops when connected directly to the wan ports now only report 100 mbps links i'd say it would impossible to enforce anything else :frowning:

14

Hello,

Please contact our support team [email protected], and cite this thread

15

@tired100 did you get your issues solve? i have same issues where my ISP Modem is a FritzBox in a Bridge Mode is connected t oFlint2 WAN Port. Somehow the negotiation drops after some time from 1gbit to 100 mbit. for no specific reason. i am not resettings the devices or doing anythind special in the settings

16

I wonder does your issue get fixed if you use the op24 firmware? Or even better the genuine OpenWrt without the gl software?

I guess you already changed the cable for a proper one?

If so, this is my take:

MTK SDK runs on a much older OpenWrt (more ancient and older kernel), some things are ported back and some things are hacked in more or less.

I'm very confident it could be this 1, and 2

which was reported at the linux kernel too and fixed, this is what is going on and yes some gl op24 versions still has this older version so you have to check this carefully, some got hack workarounds by OpenWrt (which are also fine aslong it aren't the ones from MTK SDK) and some have it fixed in the mainline kernel, this is why I suggest to try OpenWrt directly.

^ note my link is not all the PR, this one had some relevance but I have seen much more commits targeting this which also showed links to linux mailing lists, and also including a revert for the hack work around to use linux's approach instead.

As for MTK SDK, maybe there is also a workaround for this, try without hw accerelation, maybe these 2 things won't work nice together, but to me it looks this issue is never fixed in the MTK SDK or atleast never added as official support by linux in this kernel :slight_smile:

This is only about the 2.5G ports.