I’ve just had my first disconnect on this FLINT2 router. Prior to this using the Sky router, we’ve had zero issues over the years.
I am using Sky FTTP and the router had been running solid for the fifth day until this afternoon.
The logs did not pin-point why it failed to connect but looking online, lots of people suggest manually setting the WAN Port from 2.5Gbps to 1Gbps due to compatibility with my ISP.
Unfortunately, my router doesn’t have any option to do this, can someone please let me know if this is possible?
Is your ONT actually a 2.5Gbps ONT though? Good chance it’s already running at 1Gbps as depending on the ONT it may not be capable of 2.5Gbps anyway.
Do you have IPv6 enabled on the Flint and the DHCP client ID specific in Luci for both WAN (IPv4) and WAN6 (IPv6)? Sky authenticate by default with DHCP6 and DHCP4 is a fallback but you need to specify a client ID for both.
In addition, the Sky router will detect when the internet link fails and retry within a few seconds, on a 3rd party router like the Flint 2 this can take much longer as it does not support the method the Sky router uses to detect a failure, and need to wait for the DHCP lease to timeout before it tries to reconnect, so dropouts will be much more noticeable.
I want to force the WAN port on my FLINT2 to be 1Gbps same as my ONT, which does not naturally support 2.5Gbps.
Yes, IPV6 is enabled and I have set my CLIENT ID 61 following advice found online.
I didn’t have client ID specific in Luci for both WAN (IPv4) and WAN6 (IPv6) but I now do.
This is only really a problem for some devices when both sides are 2.5Gbps, its extremely unlikely forcing the Flint 2 side will make any difference as it will not be trying to negotiate anything higher than 1Gbps anyway due to the ONT limitations.
If you want to try anyway, if you SSH into the Flint you should be able to do something like the following to force it, where ethX is the name of the WAN interface in question
ethtool -s ethX speed 1000 duplex full autoneg off
You can validate the state before and after the above command using the following, which will show the link speed and what speeds are advertised by each side
ethtool ethX
These will not persist a reboot so you can rollback any changes by rebooting the router so will give you a chance to test before you try and make it permanent