Hi, ever since updating to 4.5.3, I get constant ping spikes. No matter which NODE I choose, I cannot get a stable connection.
My connection is stable when not running Mudfish, however my ping is too high to play ESO. Usually when I run Mudfish, I can decrease my ping by 100.
However since the update, I get ping spikes every 30 seconds up to 600-1000+ and then it decreases.
Hi I have tried the above as well as full VPN mode. Are you experiencing issues with servers currently?
Please download and install mudfish.net/releases/mudfish-4.5.4-x86_64-win2k-setup.exe then try it again.
This also did not fix the issue, I have no idea why it’s continuing to spike when if I use other VPN’s I do not get this issue
Please let us know what contains in
* Status - Process - Core
and
mud _std .txt
files in
C:\Program Files (x86)\Mudfish Cloud VPN
https://docs.mudfish.net/en/docs/mudfish-cloud-vpn/tech-support-problem-report/#manual-mode
and
setupapi. .log
files in
C:\Windows\INF
https://docs.mudfish.net/en/docs/mudfish-troubleshooting/errorcodes/#workaround-3
Sent an email to support@loxch.com with the subject 'Tremors - Core/API/INF Troubleshooting' with files as requested
Have you got any problem with nvidia programs?
Not that I have noticed - I only play 1 game and that's the Elder Scrolls Online NA server. Usually my connection is perfect with mudfish, only having issues since about 4 weeks ago now.
In my humble opinion, I think it'd be valuable if we test MTR to see your network status. Please check details at How to use WinMTR and try to test against to 198.20.200.73 (this is the game server IP). If you can show me the result, it'd be more helpful.
Without mudfish active-
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mygateway.gateway - 0 | 82 | 82 | 0 | 1 | 10 | 0 |
| 172.18.212.104 - 0 | 82 | 82 | 2 | 4 | 13 | 4 |
| 172.18.91.117 - 0 | 82 | 82 | 2 | 3 | 7 | 5 |
|bundle-ether4.woo-edge902.brisbane.telstra.net - 0 | 82 | 82 | 3 | 4 | 15 | 3 |
|bundle-ether6.woo-core1.brisbane.telstra.net - 0 | 82 | 82 | 3 | 6 | 15 | 6 |
|bundle-ether20.chw-core10.sydney.telstra.net - 0 | 82 | 82 | 13 | 16 | 27 | 16 |
|bundle-ether8.exi-core10.melbourne.telstra.net - 0 | 82 | 82 | 24 | 26 | 32 | 25 |
|bundle-ether2.way-core10.adelaide.telstra.net - 0 | 82 | 82 | 37 | 38 | 41 | 41 |
|bundle-ether3.pie-core10.perth.telstra.net - 0 | 81 | 81 | 64 | 66 | 68 | 67 |
|gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com - 0 | 81 | 81 | 63 | 66 | 69 | 65 |
| i-15053.sgpl-core02.telstraglobal.net - 0 | 81 | 81 | 113 | 115 | 125 | 114 |
| i-25250.hkth-core02.telstraglobal.net - 0 | 81 | 81 | 136 | 138 | 151 | 139 |
| 202.84.153.58 - 0 | 81 | 81 | 136 | 138 | 153 | 148 |
| unknown.telstraglobal.net - 0 | 81 | 81 | 135 | 137 | 150 | 137 |
| po110.bs-b.sech-hkg2.netarch.akamai.com - 0 | 81 | 81 | 258 | 260 | 271 | 260 |
| Request timed out. - 100 | 16 | 0 | 0 | 0 | 0 | 0 |
|ae121.access-a.sech-hkg2.netarch.akamai.com - 0 | 81 | 81 | 265 | 267 | 278 | 267 |
| Request timed out. - 100 | 16 | 0 | 0 | 0 | 0 | 0 |
|a72-52-29-88.deploy.static.akama
WITH MUDFISH ACTIVE-
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| Request timed
Is it working fine with a previous version?
https://mudfish.net/releases/mudfish-4.5.3-x86_64-win2k-setup.exe
4.5.3 is when it started not working properly.
I just re-installed 4.5.2 and its working perfectly fine. Was there a change from then that could make it interfere with something?
I didn't change anything going from 4.5.2 up to 4.5.3.
Both 4.5.3 and 4.5.4 do not work for me.
However reinstalling 4.5.2 seems to work fine.
Good to heat that it works fine. Sorry for this inconvenience but could you please test WinMTR again with mudfish after turning off FastConnect mode? It's hard to say why this issue happens with current latest version. :-(
EDIT: However which Windows version are you using?
This is with Fast Connect mode turned off with 4.5.2
I'm also running windows 10
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.254.140.1 - 0 | 27 | 27 | 0 | 0 | 0 | 0 |
| 10.254.254.1 - 0 | 27 | 27 | 7 | 28 | 43 | 43 |
| 10.255.240.150 - 0 | 27 | 27 | 7 | 24 | 39 | 39 |
| 45.248.77.1 - 0 | 27 | 27 | 8 | 28 | 39 | 13 |
| 45.248.77.198 - 0 | 27 | 27 | 10 | 29 | 39 | 37 |
| 103.52.118.76 - 0 | 27 | 27 | 10 | 30 | 42 | 41 |
| ae1.tr1.b1.qld.au.coloau.net.au - 0 | 27 | 27 | 158 | 171 | 193 | 188 |
| xe-1-3-0.cr2.s1.nsw.au.coloau.net.au - 0 | 27 | 27 | 158 | 182 | 211 | 165 |
| xe-0-0-47.tr1.s1.nsw.au.coloau.net.au - 45 | 9 | 5 | 0 | 857 | 3246 | 208 |
| xe-0-0-0.tr1.pad1.nsw.au.coloau.net.au - 25 | 12 | 9 | 0 | 640 | 3779 | 179 |
| telia.1wlt.ca.us.coloau.net.au - 0 | 27 | 27 | 159 | 168 | 238 | 215 |
| po111.bs-a.sech-sjc.netarch.akamai.com - 0 | 27 | 27 | 164 | 170 | 226 | 184 |
|a72-52-1-159.deploy.static.akamaitechnologies.com - 0 | 26 | 26 | 165 | 195 | 259 | 195 |
|ae120.access-a.sech-sjc.netarch.akamai.com - 0 | 26 | 26 | 166 | 205 | 324 | 203 |
|a72-52-29-88.deploy.static.akamaitechnologies.com - 0 | 26 | 26 | 198 | 239 | 334 | 228 |
| 198.20.192.4 - 0 | 26 | 26 | 197 | 243 | 324 | 314 |
| 198.20.200.73 - 0 | 26 | 26 | 197 | 232 | 296 | 281 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
4.5.4 continues to spike when I play, 4.5.2 does not do this. Not sure if the MTR tests show this or not.
Yesterday I'd updated the version to v4.5.5 with fixing this ping spike issue. When you get a chance, please test but I think it's okay to keep use v4.5.2 because there's no big changes between two.
EDIT: When I checked your MTR result, it seems there's a problem at hop 1 ~ 2 (10.254.254.1) because it avg is relatively high and jitter (between best and worst) is unstable. It'd be valuable if we can compare the result between each release versions. Thank you for information!
