Cant update from the latest snapshot 4.8.5 to the newest beta 4.9 on my flint 3 be93000.
Is this a bug or to be expected?
1 Like
checksum is correct and is always checked by me
No issue here updating from 4.8.4, try a back flashing to stable 4.8.4 first.
I've been having connection issues with my Flint 3… I don't use MLO, Adguard or any other app, just plain simple PPPoE settings and that's it. I'm connecting primarily on wifi, and it gets really bad after 2-3 days since a power cycle - pages won't fully load, videos buffer, and I can't even test speed on speedtest.net (it won't find a server and even when it finds one, the test fails). I wonder if wifi 7 is the culprit of all that then… if that's the case, disabling the 6ghz band could help? Essentially using the router like it was a Flint 2 with only the 2.4 and 5 bands. I mean, if the issue is the software that is not mature yet, I would gladly keep my Flint 3 and just disable what's not working well at the moment. I still have time to return it, but I'd rather not if there's any workaround. Tips? Btw I already have a ticket with support, provided logs, and now waiting for them to get back to me.
Flint 2 is pretty great. It runs vanilla OpenWRT really well. The HW acceleration and MediaTek drivers work quite well on vanilla OpenWRT these days. Agree with you 100%.
1 Like
Totally agree with you and based on tons of user feedback, I actually skipped Flint 3, hoping that Flint 4 would be the next beast like Flint 2 is!
1 Like
Flint 2 is what 2.5 years old now but still a great router. The hardware and passive heat sinking are amazing on Flint 2. The Qualcomm IPQ5332 on the Flint 3 runs 10 - 15 degrees C hotter than Mediatek on Flint 2.
After the 4.9.0 update, I can no longer have multiple SSIDs on the same radio.
My configuration:
wireless.wifi0=wifi-device
wireless.wifi0.type='qcawificfg80211'
wireless.wifi0.channel='auto'
wireless.wifi0.macaddr='REDACTED'
wireless.wifi0.hwmode='11beg'
wireless.wifi0.noscan='1'
wireless.wifi0.country='REDACTED'
wireless.wifi0.random_bssid='1'
wireless.wifi0.band='2g'
wireless.wifi0.htmode='HT40'
wireless.wifi0.legacy_rates='0'
wireless.wifi0.txpower='30'wireless.wifi2g1=wifi-iface
wireless.wifi2g1.device='wifi0'
wireless.wifi2g1.network='lan'
wireless.wifi2g1.mode='ap'
wireless.wifi2g1.ssid='REDACTED'
wireless.wifi2g1.encryption='psk2+ccmp'
wireless.wifi2g1.disablecoext='1'
wireless.wifi2g1.macaddr='REDACTED'
wireless.wifi2g1.factory_macaddr='REDACTED'
wireless.wifi2g1.key='REDACTED'
wireless.wifi2g1.wds='1'
wireless.wifi2g1.isolate='0'
wireless.wifi2g1.ifname='wlan2g1'
wireless.wifi2g1.ieee80211k='1'
wireless.wifi2g1.bss_transition='1'
wireless.wifi2g1.sae='0'
wireless.wifi2g1.no_beacon_rsnxe='1'
wireless.wifi2g1.random_bssid='1'
wireless.wifi2g1.disabled='0'
wireless.wifi2g1.init='1'wireless.wifi2g2=wifi-iface
wireless.wifi2g2.device='wifi0'
wireless.wifi2g2.network='iot'
wireless.wifi2g2.mode='ap'
wireless.wifi2g2.ssid='REDACTED'
wireless.wifi2g2.encryption='psk2+ccmp'
wireless.wifi2g2.disablecoext='1'
wireless.wifi2g2.macaddr='REDACTED'
wireless.wifi2g2.factory_macaddr='REDACTED'
wireless.wifi2g2.key='REDACTED'
wireless.wifi2g2.wds='1'
wireless.wifi2g2.isolate='0'
wireless.wifi2g2.ifname='wlan2g2'
wireless.wifi2g2.ieee80211k='1'
wireless.wifi2g2.bss_transition='1'
wireless.wifi2g2.sae='0'
wireless.wifi2g2.no_beacon_rsnxe='1'
wireless.wifi2g2.random_bssid='1'
wireless.wifi2g2.disabled='0'
wireless.wifi2g2.init='1'
Both interfaces do show up in the GLiNet UI and I can seemingly enable them both, but only one of them will actually work. This is quite annoying, because it breaks my setup. Due to this, I’m forced to downgrade to a past firmware.
You shouldn’t really keep your settings when upgrading to 4.9 based on many comments I have read here. You should be able to recreate this after the clean upgrade.
I am new to the Flint 3 router. I got excited with the MLO as a separate setting and on 4.9 firmware the content filtering and initially when I saw AdGuard. I like the IoT feature too.
It is disappointing to see there is a restriction on the number of filter list you can have for AdGuard….. far too few IMHO. It looks like I will have to continue with AdGuard on the RasPi 5.
MESH is a bit disappointing too but I think an acceptable workaround will be using 802.11r + Access point - do I really need MESH?
But otherwise I look forward to the Flint 4.
Hello,
Even though the number of ADG filter lists is limited, I think it probably is enough for home scenario. May I know how many rules do you need (the total number in each rule)?
The Mesh feature is already in the dev roadmap. I assume that it will preview first on Flint3 and Slate7, and the preview activity will be held in our forum.
2 Likes
Thanks Bruce, Just to clarify I use the FritzBox as my main internet router and I have a separate AdGuard + Unbound running on a dedicated Raspi 5 so all my comparisons are based upon the way I use that ad blocking.
On a separate test network I play with the settings and features on the (wonderful) Flint 3 (did I say I can’t wait for the Flint 4?) before I implement and use it as the main router / internet connection - I have an adult son that gets annoyed with my aggressive ad blocking but we can usually work through it.
So, as I absolutely detest ads I have all the enable blocks list (on the Pi5 AdGuard)
that I can get away with and still use the internet the way I want to.
Well, all of them? How many do I really need? Probably not as many as I want to block - lol.
This morning I have reset the router and just enabled the recommended list that is in the knowledgebase. I have then aggressivley used the content filter to enhance the ad blocking.
I need to readjust my OCD with ad blocking to a more realistic level.
With my limited tech knowledge, I lack understanding the difference between MESH WiFi and an access point and routers configured for 802.11r. It seems to me that the device would switch to the nearest strongest router anyway when using 802.11r - isn’t that the same for MESH?
Most of my WiFi devices are static anyway so do I really need MESH (other than to satisfy the FOMO)?
I think some of the recommended filter lists in ADG should be able to meet most ad filtering needs, and more, add a few local language rules.
In terms of usage, yep, there is no difference between them.
But in codes, there is a difference. Mesh is much easier and faster to set up.
Another interesting thing is that... (Easter egg, will know in preview stage!)
Thank you very much for your love for Flint4. There is now a beta program of Flint4 on the official website. If you are interested, you can sign up. Good luck to pick up! (Not 100%, some users with the most testing experience and rich usage scenarios will be selected from the list of all applicants)
I can’t wait to be able to use the mesh network between my Flint 3 router and my Slate 7.
It’s a feature I’ve been looking forward to for ages and I can’t wait to try it out!
1 Like
Flint 3 - setting custom IP addresses for clients.
I want to set custom IP addresses for some of my clients & then set as a static IP.
On other routers, I can change the IP in the networking section, and then making it as a static IP, but I cannot see how to do that on the Flint 3.
I have read you need to go to Luci and change IPs there - is that right, is that the only way to do it?
I prefer not to have to set the device / client to a static / custom IP, I much rather leaving them as DHCP.
I do see I can change the routers IP and set it as static, but that is not what I want….. It is the client IP I need to change (and even the connected access point set to a custom IP.
Thanks
For all Flint 3 enthusiasts, perceival is working to get mainline OpenWrt support:
They are currently trying to get another unit dedicated for testing and has made significant progress already!
1 Like
There are two ways to do this:
1 - In the client menu, there are reserved IP address options; the current IP address is automatically reserved
2 - In the Network - LAN menu, scroll down to find the ‘Address Reservation’ option
1 Like
There are two ways to do this:
1 - In the client menu, there are reserved IP address options; the current IP address is automatically reserved.
Yep I found that for the router and DHCP - I can use that later.
2 - In the Network - LAN menu, scroll down to find the ‘Address Reservation’ option
You-beauty! 
That is the one I want!
Thanks!
(I should have properly looked at the screens - I am used to other routers where you can click on the IP and then modify the IP and then reserve)
Are there any issue with changing the router IP and DHCP to the one of my choice?
Because I am rusted on FritzBox user I would like to use the 192.168.178.xxx IP addresses for the Flint 3 (and later the Flint 4 when released) and I have a number of devices for which I want to reserve the IP address of my choice for several devices.
The reason for doing this is I have the perception that using the previous router address range will make the change over to the Flint much smoother. Correct me if I am wrong.
Unless you have set up static IP addresses in the device settings, switching to a different IP address range should be straightforward.
However, changing the pre-configured LAN IP addresses from 192.168.8.xxx to 192.168.178.xxx is both possible and simple; you’ll find this option in the Network/LAN menu, where it’s the first item.
In this case, you must remember that when you reset the router (if you need to do so), this setting will also be reset, so you will need to set it again.