I mean the DPI feature will be supported on the v4.9 firmware.
The op25 firmware probably will be earlier, it has own separate timeline.
Hello,
Thank you very much for your feedback!
Do you mean that when the MT6000 is using firmware v4.8.99 and it is unable to obtain an IPv6 address from Starlink?
Please try using firmware v4.8.3 first — since v4.8.99 is not a mainline release and may have some issues.
ok glad to hear that. thank you
Yes firmware 4.8.3 works fine on StarLink with IPv6
Received, thanks for the updates and testings, please install v4.8.3 stable first.
suggestion if not suggested yet:
when I go to this page:
I would like there is some more data when I click on gamepc, like which ips and which hostnames are involved.
now for steam this might not be a good example, but for the malware filter one I really want to know more about that, because if my gamepc device is a zombie device sometimes I could identify the kind of malware family I'm looking at by the ip / dns hostname associated.
1 Like
How is your dpi working?
By using a older firmware, it should work only selective versions have it, but the updates you no longer get, if you skim this topic you can learn about those 
I thought the license has expired late December, mine automatically stopped working.
Will the Beryl AX, Beryl 7, and the Mudi 7 get the DPI feature?
They will all be supported in v4.9.
1 Like
This is going to be moving tcpdump to a GUI—just kidding. That’s actually a sensible suggestion: DPI features will head in that direction, but not anytime soon.
1 Like
According to the DPI information page (image) available in Brume 3.
Why is it necessary to keep the device on GoodCloud after 30 days for DPI to continue working?
In my case, I prefer not to have the router connected to GoodCloud because if gl-inet has a security issue on GoodCloud, it could affect me due to the connection established between GoodCloud and my device.
Why is it going to take until late Q2 or Q3 to see V4.9?
Since the DPI program and DPI signature database updated are required to GoodCloud, to fetch updates.
All DPI operations are run locally on the router, and don't upload any data.
That is the R&D plan and depend on the product roadmap..
Thanks for the reply, but I still don't see the need to activate Good Cloud. You could have implemented signature downloads and DPI updates without requiring that activation, or even if it's not activated, instead of automatic updates, you could have provided on-demand updates with a button to download the update.
You still don't get it right? 
I understand. Thank you.