Yes I understand because it's one of highest priority task items on my plate. I'm currently working on it so you can see a *button* sonner or later. :-) Thank you for opinion!

At current implementation of Mudfish v4.3.14, it only updates RTT information when at least 3 times tests are completed. The problem was that it takes more times than before whenever no. of mudfish nodes are increased. (currently Mudfish has 130 nodes world wide though in the past it was less than 90 nodes).

I see! Thank you :D

:-) I'm not sure that you checked UI change of Mudfish which made yesterday. I'd added a button to forcibly update the RTT information at the popup window. If it's not working for you, please let me know.

I've been testing for about a day or so, I have not gotten a successful refresh yet, only "Updated. However please note that your score could be inaccurate because **1** entry (or entries) of RTT information are updated only. It'll be more accurate when more RTT information are collected."

Usually 1 entry or 2 entries max is refreshed.

Did you try to wait more longer? Normally "1 entry" means that 1 RTT test against all mudfish nodes are completed. So at this moment it means around 130 RTT tests. Sometimes it takes more longer than expected to finish "1 entry" test. Please try to press a RTT update button after waiting more longer then see the number is increased or not.

@loxch As of 2/12 the refresh RTT button is working perfectly now! Just load page, click, wait 3-5 second and my RTT is delivered properly. Thanks for your hard work!

Looking forward to see your implementation on ignoring unneeded nodes by default!

> Looking forward to see your implementation on ignoring unneeded nodes by default!

It's already out from my hands; please test with v4.1.15 because it's already implemented. :-) However please note that it's unstable version though most of bugs are addressed.

Greetings again, I have currently installed 4.1.15 dev version, but I do not see the option to choose what nodes are ignored and what nodes should be checked when checking RTT.

Edit: I have also noticed that in Node Status page, nodes are not connected by default and I am given a choice to do it. Which might be why RTT checking speed seems to be increased.

Is this the intended implementation? Or have I missed a place to configure it?

> Greetings again, I have currently installed 4.1.15 dev version, but I do not see the option to choose what nodes are ignored and what nodes should be checked when checking RTT.

Ooops it seems I misunderstood your question at above comment. What a feature I mentioned at my previous comment was that from mudfish v4.3.15, as default mudfish doesn't connect to all mudfish nodes anymore. So it means no longer unintend traffic usages to other mudfish nodes which you're not using.

> Edit: I have also noticed that in Node Status page, nodes are not connected by default and I am given a choice to do it. Which might be why RTT checking speed seems to be increased.

However I'm not expecting that this change of behaviours affect to RTT checking speed. I need to do double check again not to break any features.

> Is this the intended implementation? Or have I missed a place to configure it?

Yes. However you don't need to enable a node manually at all because it'll be automatically enabled whenever you changed a item configuration or Full VPN mode's node.

I appreciate that Mudfish isn't making connection to unused nodes, thanks!

Yeap, what I meant was to filter away nodes from RTT checking completely, because I only use about 10 nodes around Asia, but RTT checking all nodes can take 4-8~second for me. Just a small quality-of-life thing, nothing high priority or too important, don't worry!

However, node only connecting when an item have been configured through Mudfish seems to break Proxifier support by a little. I need to manually open Node list and click connect before Proxifier can route traffic through selected node now, if I am using Proxifier mode. Perhaps its worth updating the Proxifier with Mudfish FAQ for other user.

P.S.: I've been trying to do Packet Dump through Mudfish, but upload is stuck every time (no more upload traffic after a minute or so) and once I cancel upload, status in Packet Dump is "Internal Error", any advice?

> Yeap, what I meant was to filter away nodes from RTT checking completely, because I only use about 10 nodes around Asia, but RTT checking all nodes can take 4-8~second for me. Just a small quality-of-life thing, nothing high priority or too important, don't worry!

No problem. :-) I'd created a ticket internally to track your feature request. Thank you for your opinion.

> However, node only connecting when an item have been configured through Mudfish seems to break Proxifier support by a little. I need to manually open Node list and click connect before Proxifier can route traffic through selected node now, if I am using Proxifier mode. Perhaps its worth updating the Proxifier with Mudfish FAQ for other user.

Yes you're correct and that's a reason why "Connect" button added not to break Proxifier users. But I think it seems it's not clear and handy for users; I need to improve it little bit.

> P.S.: I've been trying to do Packet Dump through Mudfish, but upload is stuck every time (no more upload traffic after a minute or so) and once I cancel upload, status in Packet Dump is "Internal Error", any advice?

Need to investigate more. However if it's not working, the packet dump file would be found under your mudfish installation directory (normally `C:\Program Files (x86)\Mudfish Cloud VPN`). The file name is `mudfish_pcap_msk0.pcap` so you can send it to support@loxch.com though.

Thanks a lot! Really appreciate the conversation for the past week :D Love Mudfish.
Addendum for the feature: When node selection are possible, I would like to choose "Auto choose best node within these selection of nodes" for items. For example, I would like Mudfish to auto choose ONLY "Selected KR Asia nodes" nodes. This is due to some game's Region IP blocking, and auto sometime would choose good node that cannot connect to the game.

Sorry for the feature requests! Always love to see program that I use daily and love gets better and better.

(Extra: "SD Gundam Capsule Fighter Online" is discontinued worldwide, feel free to remove it from the game list. Game is replaced with SD Gundam Next, which is already in the system :D)

> Thanks a lot! Really appreciate the conversation for the past week :D Love Mudfish.

:-) Me too and it was very productive.

> Addendum for the feature: When node selection are possible, I would like to choose "Auto choose best node within these selection of nodes" for items. For example, I would like Mudfish to auto choose ONLY "Selected KR Asia nodes" nodes. This is due to some game's Region IP blocking, and auto sometime would choose good node that cannot connect to the game. Sorry for the feature requests! Always love to see program that I use daily and love gets better and better.

I'd created a internal ticket to trace this request. :-) However I think some parts of this request are what I'm already developing actively because I'm currently enhancing RTT calculation feature to suggest a better routing path smartly. So it seems I can combine your feature request and one what I'm currently developing. Thank you for your opinion. When I get a chance, I'll try to implement it.

> (Extra: "SD Gundam Capsule Fighter Online" is discontinued worldwide, feel free to remove it from the game list. Game is replaced with SD Gundam Next, which is already in the system :D)

Got it. :-) I'll handle it carefully. Thank you for information