Some complaints to firmware [NEDS SERIOUS IMPROVEMENT]

Routers
1

Hi.

I see this already mentioned here, but i wanna be direct and put all problems i found into one post.

Clients recording

Seriously? First complaint i found 1y ago!

Why i need to chattr +i /etc/oui-tertf/client.db just to stop clients that randomize MACs from shitting in my LOG? It is like use nuke to kill fly!

I use Flint (1) to share my internet via my neighbors too (guest network) to split internet costs. And i have almost hundred of random gibberish each several days.

Why not just add "do not record" toggle?!

Lease time

Same issue as above. Many clients randomize their MACs, leading to LAN pool being overfilled with "ghosts" that disconnected. I fixed this manually decreasing lease time, but i think you should decrease lease time at least in half by default in firmware.

2

Hi

Regarding the first point, we plan to add an “automatically remove offline devices” feature in version 4.9, which should meet your needs.

Regarding the second point, thank you for your suggestion.
Considering that a 12-hour DHCP lease is the widely used default in the OpenWRT community, and that there are currently ways to modify it, we will log this as a request.
However, unless there are sufficient cases showing that it causes issues, we are unlikely to change it.

1 Like
4

Why not just mount it in RAM? Why workarounds and loopholes?

Constant deletion will make flash suffer. 128 mb flash will be killed with this write quantity.

The problem appeared not because regular 2-3 device usage. It appeared because i have from 20 to 30 devices online. Each randomise MAC.

Or just add toggle to disable recording.

Super strange. Maybe legacy, since now almost no clients have stable mac and this leads to "DoS" of DHCP

5

If you not satisfied with GL.Inet firmware, you have the luxury position with GL.Inet routers that you can choose to use vanilla OpenWRT (the original openwrt, with no GL.Inet webinterface but only Luci)

6

:clown_face:

How should i init it, if it will not activate wifi on setup? Via LAN? But FYI there is not many people with so legacy hardware that still have LAN port.

And where i will get BSSID and MAC randomization? You are saying that i should script it? FYI not all people are computer programmers.

7

The data is first stored in RAM and only written to flash afterward, so it does not affect the flash lifespan.

Let us discuss this with the product team and see whether we can add this feature in a future version.

8

Tbh, this is an issue with the config of those devices then.
For example, iOS will not generate a new MAC just because there is a new DHCP address. Ghosts are no problem at all because as soon as the lease time is over, the address is free to use. By selecting a higher lease time, you even caused the problem to get worse.

1 Like
9

I know, but...

I use Flint (1) to share my internet via my neighbors too (guest network) to split internet costs. And i have almost hundred of random gibberish each several days.

I cannot fix not my devices. Plus i think it is good to have MAC flip-flop all times if system supports it. It will prevent network to know that this is same person between sessions, not only networks.

So fix is the easiest. We need a toggle. Because using ln -s /dev/null (as on other forum recommended) approach or mine with chattr +i is like nuke against mosquito