OP24 install on a GL.iNET Flint 2 (GL-MT6000) with keeping/copying some settings

Hello :waving_hand:t2:
I want to try the full OpenWRT version for my Flint2.
I love the GL UI but it’s still on an old OpenWRT and there is some missing package I want to use…
So that’s why I’m willing to switch to the pure OpenWRT.

But I need to keep some settings I don’t want to loose or I don’t want to set up manually again…
Example : all my LAN IP reservation with MAC address, IP and name (a hundredth or so) and the DHCP settings.
Another thing I want to keep because I’m not sure I can reconfigure it : the network lan/wan1 port set up to LAN
and the lan/wan0 set up to wan.

The Firewall - Zone Settings too.

My fear is to loose bandwidth with full OpenWRT from wan to lan and for the WiFi.

It seems that this custom build will feat my needs : MT6000 custom build with LuCi and some optimization - kernel 6.6.x

But how can I installed it ?

Thanks for your help :blush:

As the doc page says you just flash sysupgrade and select do not keep settings. You don't want to keep settings from a custom fork and official openwrt, not a good idea on any target. Once you're on OpenWrt you can usually keep your configs for life (unless major changes like nftables or dsa happens again, apk will be next but that will only change install scripts).

Hello :waving_hand:t2:
I understand that is not a good idea to keep anything from a custom build especially when it’s older…

But I want to keep dhcp reservation…
If it can’t be done, is it possible to edit manually a file where data is stored?
If yes , where can I find this file ?
Is somebody have this file without any modifications ?

My goal is to quietly edit the said file in VSCode before making the change to OpenWRT and then copy this file instead of the one delivered by default with the newly installed OpenWRT. This way, my servers (NAS, NUC, VM including Home Assistant, etc.) which require specific IP addresses will always work without major interruption.

Do you think it is possible to do this?

Yes to all your questions, that's the point of /overlay. For reserving static IPs for a bunch of devices just do that based on their mac address in /etc/config/dhcp. e.g.:

config host
        option name 'nas'
        list mac 'XX:XX:XX:XX:XX:XX'
        option ip '192.168.1.XXX'
        option leasetime 'infinite'

Read the doc pages for OpenWrt there are explanations for all that stuff like network and dhcp. You can probably keep those configs going over to official OpenWrt, just not positive it'll be without issue I'm not sure what Glinet changes on their end. I would take it as an opportunity to config fresh that's what I did 16 months ago when I got this router.

1 Like

Ok ! Nice ! It should be possible :smiley:

Here the begining of the /etc/config/dhcp file :

root@GL-MT6000:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option filterwin2k '0'
	option localise_queries '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option nonegcache '0'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option nonwildcard '1'
	option localservice '1'
	option ednspacket_max '1232'
	option rebind_protection '0'
	option filter_aaaa '1'

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option dhcpv4 'server'
	option ra_slaac '1'
	option force '1'
	option dhcpv6 'disabled'
	option ra 'disabled'
	option ignore '0'
	option leasetime '720m'
	option limit '21'
	list dhcp_option '6,192.168.2.141'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'

config domain
	option name 'console.gl-inet.com'
	option ip '192.168.2.1'

config domain
	option name 'console.gl-inet.com'
	option ip '::ffff:192.168.2.1'

config dhcp 'guest'
	option interface 'guest'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv6 'disabled'
	option ra 'disabled'

config dhcp 'secondwan'
	option interface 'secondwan'
	option ignore '1'

config host
	option mac '00:E0:4C:00:00:AA'
	option ip '192.168.2.30'
	option tag 'MBA M2 - LAN : 2,5 GbE'

config host
	option mac 'F8:E5:CE:00:00:AA'
	option ip '192.168.2.24'
	option tag 'iPhone'

config host
	option mac 'A0:CE:C8:00:00:AA'
	option ip '192.168.2.201'
	option tag 'Syno-DS920+ ETH2 USB 2,5GbE'

config host
	option mac '00:11:32:00:00:AA'
	option ip '192.168.2.200'
	option tag 'Syno-DS920+ ETH0 1Gb'

Following the link in the OpewnWRT Wiki, I see that hte only missing option is option leasetime 'infinite'. Maybe it is by default infinite??

For the first part of the file, I'm not sure it will be the same with pure OP24. So I'll just copy/pasgte the end of the file, starting with the first config host.

Do yoi think there is another file I need to "keep"?

You don't need to use infinite it's just what I use since why not have static leases never expire. Your file looks good to me. I don't want to hijack this thread though if it's a more complex discussion about config files open a new thread under "Installing and Using".

1 Like

indeed... I agree

Hello :waving_hand:t2:
Ok, I'll open a new thread :slightly_smiling_face:, here : OP24 install on a GL.iNET Flint 2 (GL-MT6000) with keeping/copying some settings

Hello :waving_hand:t2:
I was prompted to create a new topic because I want to install OpenWRT 24 on my Flint2 (MT6000) while keeping/copying some settings.
Here my initial post : GL.iNET Flint 2 (GL-MT6000) discussions - #2501

In summary, I can copy most of the /etc/config/dhcp file from GL.iNet installation to the new OpenWRT 24, thus preserving the IP address assignments I really want to keep (more than a hundredth).

Another thing I want to keep because I’m not sure I can reconfigure it : the network lan/wan1 port set up to LAN and the lan/wan0 set up to wan, and also the Firewall - Zone Settings too.

Do you think this is possible? What file is needed?

My fear is to loose bandwidth with full OpenWRT from wan to lan and for the WiFi.
Thanks for your help :innocent:

PS : be kind, I'm not used to using this kind of OS... I'm not afraid using CLI, but I must understand what commands I use. And the little I've seen of LUCI using my Flint2 is quite disconcerting.

PPS : I already made a backup from the Luci UI on my Flint2 currently on GL.iNet Firware 4.7.4 OpenWrt 21.02-SNAPSHOT r15812+1084-46b6ee7ffc.

Thanks again

Generally speaking, the config files from GL-inet's custom fork are not compatible with official OpenWrt. My recommendation would be to not attempt to keep any of the existing files and start from scratch.

Obviously, your dhcp file with over a hundred entries would be very painful to recreate manually, so the best option would be to copy/paste just the DHCP reservations from the dhcp file, first verifying that the syntax is the same as for the official OpenWrt firmware.

Beyond that, I wouldn't try to keep anything else unless you can be certain that the syntax is compatible. Do not just copy the files over -- copy/paste only individual stanzas as needed.

If you'd like, you could provide a sample of the DHCP reservation stanzas (just one or two would be sufficient) and any other selected items you wish to preserve -- we will likely be able to tell you if they will work or not (and if not, we can probably advise about how to edit or recreate the items).

2 Likes

Hello :waving_hand:t2:
Thanks for tour reply and for meging my posts here.

I understand just copy/paste config files from GL.iNET OP21 to the OP24 isn’t a good idea. And I concur to not do it at all.
As I try to explain, I just want to extract config data from the CL files and paste with adapting if necessary into the OP config files.

In my previous post here I pasted the beginning of the dhcp file.
@phinn seems to be confident to the fact my dhcp file is compatible with OP24.

Is there anything elsewhere for the dhcp ?

My fear is that I can’t set the configuration the same as I have now.
I use the WAN port 2,5G for WAN (connected to my ISP box (=router)), and I use the second 2,5G port WAN/LAN1 to connected a 2,5G switch for my LAN.

My ISP gave me a 2 000 Mbps / 800 Mbps for DL / UP.

Do I need to configure something to get my Flint2 to works as I intend to ?

Thanks for your answer.
Have a nice day :innocent:

For 2Gbit down (damn that’s fast) I would skip using any sort of SQM, you would need something like an N100 box for that anyway. Just enable hardware flow offloading on the firewall page and you’ll be good to go.

If you do other services on the router (like I use ksmbd, adblock, etc.) also enable packet steering and irqbalance. These are common tweaks and again the doc pages list those please skim them. At the very least the one for our target MT6000.

2 Likes

Yeah :high_speed_train:
In France, ISP offers super speed :slight_smile: My previous ISP gave me 5 Gbps, but, only one 2,5 Gbps port, and some old wifi 5 :sweat_smile: I could however use the 2.5Gbps fully on one port with the Flint2 :smiley:

Ok for SQM, what I read agrees with your advice :wink:
What do you mean with you would need something like an N100 box for that anyway. ?

I may use AdGuard Home, but more surely I'll use Crowdsec and fail2ban. and maybe BanIP if I understand how to use it to block incoming request from all IP except FR ones.
So, OK fot that too: packet steering and irqbalance.

I already read that page :slight_smile:

And I see the custom build: MT6000 custom build with LuCi and some optimization - kernel 6.6.x
It may be interresting to use it, but I don't know how to install it :sweat_smile:

Installation of a custom build is the same as a regular official one, just flash the sysupgrade image. Pesa explains it all in his thread.

N100 is an Intel x86-64 box… more expensive higher performance high power consumption.

1 Like

The N150 is a newer and faster design, but slightly more expensive and energy-intensive.

Cool but point remains the same.

1 Like

Hello :waving_hand:t2:

He explains how to compile it :blush:
But I lack the time to do so. I’m note sure he provides an already compiled version.
But maybe this file is what I look for: -snapshot-r29721-5111451803-mediatek-filogic-glinet_gl-mt6000-squashfs-sysupgrade.bin
It’s present here: https://github.com/pesa1234/MT6000_cust_build/tree/main/2025-04-19_r29721-5111451803_next-r4.5.34.rss.mtk/targets/mediatek/filogic

Is this .bin the file I need to flash into my Flint2?
I read in the wiki page that snapshots build doesn’t came with LuCI.
Is it installed with the custom build of @pesa1234 ?
He said in his thread that LuCI is indeed installed so great :grinning_face:

Ha ok! It’s a miniPC :blush: I have one , not with N100, but an intel 13th Gen for hosting ProxmoxVE and some VM and LXC.

Ok so if the .bin previously mentioned is the one I need , I may try the adventure of pure OpenWRT :blush:

Thanks to all for your help :innocent:

The sysupgrade bin looks good, I don't use pesa's builds though so can't confirm exactly what build you should be flashing that's all explained on his thread.

Correct snapshots don't come with luci but that takes 5 seconds to install. I don't recommend that for you though stick to 24.10.1 or pesa's until you know what you're getting yourself into with apk and other new features.

1 Like

OK, I can try the .bin :wink:

I don't really understood what you mean with that...
Are you telling me that you can't recommend the custom build of pesa over the stable release of 24.10.1 ?

What's about the apk?
What packet manager is embedded with both version?

Just saying I don't recommend snapshots as a new user, stick with official builds or pesa's depending on the route you want to go.

3 Likes