For that kind of money, you could buy a micro PS with the same Intel chip and use any router as an access point, and this setup would be much more robust than any router! If you want to change the Wi-Fi standard, you only need to replace the access point or the router!!!
Hello,
I would like to ask for your opinion and advice for the best openwrt setup for my flint 2 setup as a pure simple AP only. there are no dhcp, firewall, ppoe samba, usb or any other router functions left and i have stripped it off any other extras as they are not needed. Bridger came pre-installed and i have left it like that. What do i do with WED - leave it off as it was or turn it on? what about packet steering - it was ON, but the advanced part was off. I am on a 1 gb wan and local network and dont utilise 2.5gb. only need good internal reliable wifi with low ping and jitter at list locally.
thanks in advance for your thoughts.
This is all discussed on the doc page.
Thank you very helpful
Maybe a dumb question. I bought Flint 2 a week ago from the official site (US distributor). I wonder why the flash layout is different from "default".
The default documented in the wiki is:
root@OpenWrt:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 7.2G 0 loop /overlay
mmcblk0 179:0 0 7.3G 0 disk
├─mmcblk0p1 179:1 0 512K 0 part
├─mmcblk0p2 179:2 0 2M 0 part
├─mmcblk0p3 179:3 0 2M 0 part
├─mmcblk0p4 179:4 0 2M 0 part
├─mmcblk0p5 179:5 0 2M 0 part
├─mmcblk0p6 179:6 0 32M 0 part
└─mmcblk0p7 179:7 0 7.2G 0 part /rom
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
The layout on the my router is:
root@flint2:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 6.7G 0 loop /overlay
mmcblk0 179:0 0 7.3G 0 disk
├─mmcblk0p1 179:1 0 512K 0 part
├─mmcblk0p2 179:2 0 2M 0 part
├─mmcblk0p3 179:3 0 2M 0 part
├─mmcblk0p4 179:4 0 2M 0 part
├─mmcblk0p5 179:5 0 2M 0 part
├─mmcblk0p6 179:6 0 32M 0 part
└─mmcblk0p7 179:7 0 6.8G 0 part /rom
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0p7 is smaller by 0.4G. Where did it go?
Here I just checked mine, it's still the same as 2 1/2 years ago when I put that on the wiki. So the issue is likely on your end in that you're maybe not running official OpenWrt but the fork provided by Gl-inet with the router.
root@OpenWrt:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 7.2G 0 loop /overlay
sda 8:0 0 1.8T 0 disk
└─sda1 8:1 0 1.8T 0 part /mnt/sda1
mmcblk0 179:0 0 7.3G 0 disk
├─mmcblk0p1 179:1 0 512K 0 part
├─mmcblk0p2 179:2 0 2M 0 part
├─mmcblk0p3 179:3 0 2M 0 part
├─mmcblk0p4 179:4 0 2M 0 part
├─mmcblk0p5 179:5 0 2M 0 part
├─mmcblk0p6 179:6 0 32M 0 part
└─mmcblk0p7 179:7 0 7.2G 0 part /rom
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
I'm running the latest OpenWrt 25.12.5 r33051-f5dae5ece4 / LuCI (HEAD detached at 128a7812) branch 26.180.75667~128a781
It was flashed via Uboot web UI.
Does uploading the firmware actually change partitions on MMC? I assume Uboot itself is in one of those, assuming mmcblk0boot0 and mmcblk0boot1. So you cannot override those, right?
Interesting, I have no idea then, maybe there are slight variations in the hardware since it launched since I have a preorder device? I got a second mt6000 about a year later and just checked that too. One runs 25.12.5 and one runs bleeding edge main branch build I do, but they both have the same lsblk output.
Did a little more digging.
root@flint2:~# sfdisk -l /dev/mmcblk0boot0
Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@flint2:~# sfdisk -l /dev/mmcblk0
The backup GPT table is not on the end of the device.
Disk /dev/mmcblk0: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2BD17853-102B-4500-AA1A-8A21D4D7984D
Device Start End Sectors Size Type
/dev/mmcblk0p1 8192 9215 1024 512K Linux filesystem
/dev/mmcblk0p2 9216 13311 4096 2M Linux filesystem
/dev/mmcblk0p3 13312 17407 4096 2M Linux filesystem
/dev/mmcblk0p4 17408 21503 4096 2M Linux filesystem
/dev/mmcblk0p5 21504 25599 4096 2M Linux filesystem
/dev/mmcblk0p6 25600 91135 65536 32M Linux filesystem
/dev/mmcblk0p7 91136 14254046 14162911 6.8G Linux filesystem
If I read this correctly, there are 15269888 sectors but the last partition ends at 14162911. So there are some 1106977 sectors left, or ~540MB.
Trying fdisk (won't commit), it allows me to add another partition at the end:
Command (m for help): n
Partition number (8-128, default 8):
First sector (34-15269854, default 14254080):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (14254080-15269854, default 15267839):
Created a new partition 8 of type 'Linux filesystem' and of size 495 MiB.
Command (m for help): p
Disk /dev/mmcblk0: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2BD17853-102B-4500-AA1A-8A21D4D7984D
Device Start End Sectors Size Type
/dev/mmcblk0p1 8192 9215 1024 512K Linux filesystem
/dev/mmcblk0p2 9216 13311 4096 2M Linux filesystem
/dev/mmcblk0p3 13312 17407 4096 2M Linux filesystem
/dev/mmcblk0p4 17408 21503 4096 2M Linux filesystem
/dev/mmcblk0p5 21504 25599 4096 2M Linux filesystem
/dev/mmcblk0p6 25600 91135 65536 32M Linux filesystem
/dev/mmcblk0p7 91136 14254046 14162911 6.8G Linux filesystem
/dev/mmcblk0p8 14254080 15267839 1013760 495M Linux filesystem
Also this does not look like a variation of hardware. The total size of /dev/mmcblk0 is the same. It just partitioned the way that leaves about a half of gig at the end unused.
Does flashing a new firmware change mmcblk0 partitions? Or does it only override one?
