I would like to request the option to select UDP as the protocol for the RTT test server in custom items. Currently, the protocol selector in this section only offers TCP and ICMP for desktop and only ICMP for OpenWRT
The proposed feature would allow users to select UDP and specify a destination port for the test. This would provide a testing option for game servers that use this protocol, provided the destination can return a valid response for measuring RTT.
If UDP testing requires a specific configuration or has limitations, it would be helpful to explain these in the interface so that a lack of response is not mistaken for a connection issue.
Hello! Thank you for your suggestion. We understand that being able to select UDP and specify a destination port for RTT tests in custom items would be useful.
However, implementing this feature isn’t straightforward. UDP-based RTT tests aren’t always reliable, as game servers may or may not respond depending on their protocols. In many cases, a specific payload is also required to receive a valid response.
Therefore, a lack of response doesn’t necessarily indicate a connection issue.
I’ll create an internal ticket to keep track of your suggestion, but unfortunately, supporting this feature may be difficult, and we can’t guarantee its implementation.
Thank you for your feedback and for helping us improve Mudfish!
Hello. I understand the issues this could involve depending on the context, and that it isn’t suitable for every server or every user. That’s why I think it should be an advanced option available only in custom items, with a warning about possible failures, for advanced users who understand its implications and can benefit from it.
Thank you for clarifying your suggestion and sharing the resources!
We understand your proposal to offer UDP RTT testing as an advanced option for custom items, with a configurable destination port and a warning about possible failures. Let me think this a little bit more. I’ll try to check GL.iNet stuff too.
Hello
I’d also like to report that in the latest versions for OpenWRT (Mudfish Pi 2.7.7 and 2.7.10), changing the language has no effect; the interface always stays in Korean. Should I open a separate topic for this, or is it okay to report it here?
It would also be nice to have a dark theme like the desktop version does.
Hello! That’s strange that the interface still appears in Korean. Have you tried changing your language preference from your account settings at the following link?
Could you please check whether this change also applies to Mudfish Pi 2.7.7 and 2.7.10? Regarding the dark theme, I’ve created an internal ticket for your suggestion. I’ll take a look when I get a chance, but I can’t promise when or if it will be implemented.
Hello. I have English selected in the dashboard and Spanish in my account settings, and the Mudfish Pi dashboard is displayed in English. If I change the language in the dashboard, it switches to Korean. It seems that whichever setting is changed last determines the language displayed: if I change the dashboard setting last, the interface appears in Korean. If I change the account setting last, it switches to English rather than Spanish.
Hello, thank you for the detailed information and for testing this issue. It’s strange that Mudfish Pi switches to Korean when changing the language from the dashboard, and displays English instead of Spanish when changing it from the account settings.
I’ll try to reproduce this issue on my end when I get a chance to investigate further. Thank you for your patience and for reporting this issue.