http://mudfish.net/docs/en/policy/pricing.html

AUD shall support Google Play InApp Payment

:-( Sorry for this issue because the documentation wrote wrong because Google Play InApp Payment only supports USD. However did you pay it for mudfish credit already?

Not yet. Will the payment be convert to AUD automatically?

Will USD & AUD make any difference?

> Not yet. Will the payment be convert to AUD automatically? Yes it should. :-) If there's any problem or issue please let me know. > Will USD & AUD make any difference? Nop. :-)  However please note that traffic charge is working based on KRW (Korea Won) so depending on the currency status between USD <-> KRW or AUD <-> KRW, its amount of charge could be little different.

Why I have lots of domestic traffic going through vpn? in my pc's routing table, I see:      203.213.33.0    255.255.255.0     10.254.226.1    10.254.226.13    331     198.20.192.0    255.255.224.0     10.254.226.1    10.254.226.13    331      198.20.198.0    255.255.255.0     10.254.226.1    10.254.226.13    331 I have only enabled ESO item. why 203.213.33.x is also going through vpn? It doesn't make sense. Regards,

In my opinion, it's related with CDN and Mudfish link.  In ESO game item, it includes some hostnames whose CNAME are pointing the cache server of CDN company (at here specially Akamai).  I think it affects your credits. :-(

For ESO it's not required to go through vpn for these CDN. I removed the route to 203.213 manually, all works fine.Can you update the ESO item to not include CDN? from my point of view, eso only need 198.20.192.0/24 198.20.198.0/24 for NA server

Okay.  I'd updated the game item based on your information again to avoid CDN company.  :-) I think now it should be safe from it but please test and let me know if there's something it's not working properly.

thanks, will test today

works perfectly for me

Cool! :-) I hope now everything goes well with mudfish. Please let me know if there are any other problems.

I just found Calculated Routing path and expected RTT has big difference with real data. I have to test connect a few to see which one is better. Today just bad luck, cannot find anyone better then no vpn.

When I checked your account, it seems you're using TCP protocol for Connection Protocols.  Is there a reason why you're using TCP Port 443 instead of UDP?

Normally I will use UDP, but sometimes I have to use mudfish behind a firewall, which only TCP_433 works. I understand when behind firewall these calcuated routing path won't work, but the problem I reported was when I was using UDP and not behind a firewall.

One more suggestion here. I found mudfish change it's default gateway's MAC address every time. I understand we don't want to run into MAC collision and this works fine in Linux/mac.. But in Windows 10, it confused OS to create new network profile every single time. Can we have it fixed to one MAC or give us an option to choose from fixed MAC/random MAC? Thanks a lot.

> Normally I will use UDP, but sometimes I have to use mudfish behind a firewall, which only TCP_433 works. I understand when behind firewall these calcuated routing path won't work, but the problem I reported was when I was using UDP and not behind a firewall. Then are you meaning that you're using Mudfish at different locations?  Not sure why but I could guess that this difference could confuse a RTT calculation server calculate the RTT information wrong if RTT isn't updated properly by Mudfish program. However please check http://ko.loxch.com/userrtt/?uid=206151 link too for your RTT stddev to mudfish nodes.  It seems your ISP has some stablilty issue because it's relatively high to most of mudfish nodes meaning that your ISP has a issue.

> Can we have it fixed to one MAC or give us an option to choose from fixed MAC/random MAC? Please check Merge network profiles and try to use `-I` option for this issue. :-)

I have tried -I option, now windows cannot identify network thus no new profile created. Such a genius way to get around this problem, lol.