FFXIV MUDEC_00062 Lost packets resulting in DC

Im disconnecting from FFXIV every 30 minutes to an hour, with mudfish citing
[1827.065478] re415: MUDEC_00062: ODR_read() for hdr error from 180.149.230.26: ODR_ECONNRESET
after messages of packet loss after being fine up until the moment it disconnects.

Have tried changing nodes manually, using advanced mode, changing connection protocol, changing my MTU to 1350, using old master server ( -O), resetting my TCP/IP using CMD, resetting all adaptors and kicking connection at my internet DPU and finally, an NCD port reset.

I’ve done a WinMTR capture that shows one of the disconnections

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             10.254.30.1 -    0 | 2684 | 2684 |    0 |    0 |    3 |    0 |
|                            10.254.254.1 -    1 | 2664 | 2660 |  131 |  155 | 3761 |  132 |
|                          10.255.253.106 -    1 | 2664 | 2660 |  131 |  151 | 3761 |  132 |
|                           180.149.230.1 -    1 | 2664 | 2660 |  131 |  155 | 3762 |  139 |
|                            103.97.52.28 -    1 | 2664 | 2660 |  131 |  162 | 3263 |  133 |
|    v400.ae0.cr1.ty8.ty.jp.coloau.net.au -    1 | 2664 | 2660 |  131 |  163 | 3263 |  135 |
|                   17685.tyo.equinix.com -    1 | 2664 | 2660 |  131 |  157 | 3761 |  134 |
|                           61.195.56.161 -    1 | 2664 | 2660 |  131 |  165 | 3263 |  134 |
|                          219.117.144.66 -    1 | 2665 | 2661 |  132 |  157 | 2765 |  183 |
|                          219.117.144.53 -    1 | 2664 | 2660 |  132 |  155 | 3263 |  134 |
|                          219.117.144.41 -    1 | 2664 | 2660 |  132 |  166 | 3264 |  138 |
|                         219.117.147.194 -    1 | 2664 | 2660 |  132 |  158 | 3762 |  136 |
|                         124.150.157.158 -    1 | 2664 | 2660 |  132 |  166 | 3263 |  185 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Any assistance would be greatly appreciated

Im also receiving very erratic ping results from a range of servers

@rawrku Regarding to this MUDEC_00062 error, please check MUDEC_00062 error link for details. It seems the connection is aborted by mudfish nodes in my opinion by getting TCP RST packet. However I’m not sure why at this moment.

And I checked your result of WinMTR, it shows there’s 1% packet loss between your desktop and mudfish node you’d picked. To narrow down this issue little bit more, please test to the public IP of mudfish nodes you picked. The public IP of each mudfish nodes is found at http://mudfish.net/server/status link.

However did you try to change Connection Protocols to UDP based? Or try to use other mudfish nodes?

@Mutantx Did you try to change a mudfish node based on FAQ - Nodes section for your game item? If you’re using the advanced mode, please start with the basic mode.

When I checked your Realtime RTT, it seems it’s quite unstable. If you get a chance, I think it’s also helpful if you can check your ISP too.

I’ve tried going UDP based and encounter the same issue, and swap nodes frequently.
I’ve contacted my ISP and am waiting on a reply currently

Traceroutes without mudfish connected to node AU Oceania (Sydney - Lightsail)

AU Oceania (Sydney - Lightsail)

C:\Users\New>tracert 13.55.48.25

Tracing route to ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com [13.55.48.25]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2     8 ms     8 ms     8 ms  100.65.0.1
  3     7 ms     7 ms     6 ms  gi2-0-3-2501.core1.portmel.aussiebb.net [180.150.0.253]
  4     8 ms     7 ms     8 ms  be10-3999.core1.ia-dcb.portmel.aussiebb.net [180.150.0.254]
  5    20 ms    20 ms    20 ms  be5.core1.equinix-sy1.syd.aussiebb.net [180.150.1.157]
  6    19 ms    20 ms    19 ms  99.82.178.230
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  General failure.

Trace complete.

C:\Users\New>tracert 13.55.48.25

Tracing route to ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com [13.55.48.25]
over a maximum of 30 hops:

  1     2 ms     1 ms     4 ms  192.168.0.1
  2     8 ms     8 ms     9 ms  100.65.0.1
  3     7 ms     7 ms     7 ms  gi2-0-3-2501.core1.portmel.aussiebb.net [180.150.0.253]
  4     8 ms     7 ms     7 ms  be10-3999.core1.ia-dcb.portmel.aussiebb.net [180.150.0.254]
  5    19 ms    19 ms    19 ms  be5.core1.equinix-sy1.syd.aussiebb.net [180.150.1.157]
  6    20 ms    19 ms    19 ms  99.82.178.230
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    21 ms    21 ms    21 ms  52.95.37.189
 10    20 ms    20 ms    19 ms  150.222.112.153
 11    36 ms    37 ms    32 ms  150.222.112.148
 12    25 ms    23 ms    25 ms  52.95.36.57
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    21 ms    21 ms    20 ms  ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com [13.55.48.25]

Trace complete.

Traceroute to node AU Oceania (Sydney - Amazon EC2) - one of my “todays path” options

C:\Users\New>tracert 54.252.112.143

Tracing route to ec2-54-252-112-143.ap-southeast-2.compute.amazonaws.com [54.252.112.143]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 100.65.0.1
3 8 ms 7 ms 7 ms gi2-0-3-2501.core1.portmel.aussiebb.net [180.150.0.253]
4 9 ms 8 ms 8 ms be10-3999.core1.ia-dcb.portmel.aussiebb.net [180.150.0.254]
5 20 ms 20 ms 19 ms be5.core1.equinix-sy1.syd.aussiebb.net [180.150.1.157]
6 20 ms 20 ms 20 ms 99.82.178.230
7 * * * Request timed out.
8 * * * Request timed out.
9 20 ms 20 ms 19 ms 52.95.37.191
10 21 ms 20 ms 20 ms 150.222.112.187
11 21 ms 21 ms 21 ms 150.222.112.180
12 40 ms 21 ms 21 ms 52.95.36.59
13 21 ms 21 ms 21 ms 54.240.192.239
14 21 ms 21 ms 21 ms ec2-54-252-112-143.ap-southeast-2.compute.amazonaws.com [54.252.112.143]

Trace complete.

@rawrku Could you please test to 13.55.48.25 IP with WinMTR and show the result to me? Frankly speaking the result of traceroute doesn’t show where these kind of packet losses are from. It seems we need to test it with WinMTR.

> |------------------------------------------------------------------------------------------|
> |                                      WinMTR statistics                                   |
> |                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
> |------------------------------------------------|------|------|------|------|------|------|
> |                             192.168.0.1 -    1 | 8821 | 8820 |    1 |    1 |  106 |    1 |
> |                              100.65.0.1 -    2 | 8402 | 8294 |    5 |    7 |  223 |    7 |
> | gi2-0-3-2501.core1.portmel.aussiebb.net -    2 | 8374 | 8259 |    5 |    6 |  225 |    6 |
> |be10-3999.core1.ia-dcb.portmel.aussiebb.net -    2 | 8458 | 8364 |    5 |    7 |  139 |    7 |
> |  be5.core1.equinix-sy1.syd.aussiebb.net -    2 | 8358 | 8239 |   17 |   18 |  241 |   19 |
> |                           99.82.178.230 -    2 | 8327 | 8200 |   17 |   18 |  211 |   18 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |                            52.95.37.189 -    2 | 8348 | 8226 |   18 |   20 |  183 |   20 |
> |                         150.222.112.153 -    2 | 8422 | 8319 |   17 |   19 |   71 |   19 |
> |                         150.222.112.148 -    2 | 8442 | 8344 |   18 |   20 |  252 |   20 |
> |                             52.95.36.57 -    2 | 8431 | 8330 |    0 |   20 |  242 |   19 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |                   No response from host -  100 | 1767 |    0 |    0 |    0 |    0 |    0 |
> |ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com -    2 | 8434 | 8334 |   18 |   19 |  266 |   20 |
> |________________________________________________|______|______|______|______|______|______|
>    WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

@rawrku Thank you for sending this packet dump. :slight_smile: As you can see the result, first packet loss is starting from hop #1.

It means your router is dropping packets. And more packets are dropped from your ISP too. So for this case you should check your ISP first. At least I don’t think this issue is from mudfish.

Have got my ISP to do a ping plotter and opt me out of CG-NAT for testing purposes, will let you know how it goes

Currently opted out of CG-NAT,
WinMTR capture of 13.55.48.55 without mudfish running

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  414 |  414 |    1 |    1 |   19 |    2 |
|loop121200160.bng1.ia-dcb.portmel.aussiebb.net -    1 |  407 |  405 |    6 |    7 |   13 |    7 |
|  be5.core1.equinix-sy1.syd.aussiebb.net -    1 |  411 |  410 |   17 |   18 |   42 |   20 |
|HundredGigE0-0-0-8.core1.vdc03.mel.aussiebb.net -    1 |  411 |  410 |   17 |   18 |   46 |   17 |
|HundredGigE0-0-0-16.core1.vdc01.syd.aussiebb.net -    1 |  411 |  410 |   17 |   18 |   32 |   18 |
|                   No response from host -  100 |   83 |    0 |    0 |    0 |    0 |    0 |
|                            52.95.37.197 -    1 |  407 |  405 |    0 |   20 |   38 |   20 |
|                         150.222.112.161 -    1 |  411 |  410 |   18 |   20 |   45 |   19 |
|                         150.222.112.168 -    1 |  407 |  405 |   18 |   20 |   46 |   24 |
|                             52.95.36.89 -    1 |  407 |  405 |   18 |   21 |   49 |   20 |
|                          54.240.192.107 -    1 |  407 |  405 |   18 |   19 |   33 |   19 |
|                   No response from host -  100 |   83 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   83 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   83 |    0 |    0 |    0 |    0 |    0 |
|ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com -    1 |  403 |  400 |   18 |   18 |   43 |   19 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Capture of 13.55.48.25 with mudfish running

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  409 |  409 |    1 |    1 |   66 |    1 |
|loop121200160.bng1.ia-dcb.portmel.aussiebb.net -    1 |  401 |  399 |    6 |    7 |   32 |    6 |
|  be5.core1.equinix-sy1.syd.aussiebb.net -    2 |  381 |  374 |   18 |   18 |   23 |   18 |
|HundredGigE0-0-0-8.core1.vdc03.mel.aussiebb.net -    2 |  381 |  374 |   17 |   18 |   20 |   19 |
|HundredGigE0-0-0-16.core1.vdc01.syd.aussiebb.net -    2 |  382 |  375 |   17 |   18 |   21 |   18 |
|                   No response from host -  100 |   81 |    0 |    0 |    0 |    0 |    0 |
|                            52.95.37.197 -    3 |  373 |  364 |   18 |   20 |   37 |   20 |
|                         150.222.112.161 -    2 |  393 |  389 |   18 |   20 |   65 |   20 |
|                         150.222.112.168 -    2 |  393 |  389 |   18 |   20 |   39 |   19 |
|                             52.95.36.89 -    4 |  357 |  344 |   18 |   19 |   40 |   18 |
|                          54.240.192.107 -    2 |  385 |  379 |   18 |   19 |   38 |   18 |
|                   No response from host -  100 |   81 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   81 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   81 |    0 |    0 |    0 |    0 |    0 |
|ec2-13-55-48-25.ap-southeast-2.compute.amazonaws.com -    2 |  381 |  374 |   18 |   18 |   46 |   19 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

capture of FFXIV JP datacenter 124.150.157.158 with mudfish running

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            10.254.190.1 -    0 |  566 |  566 |    0 |    0 |    1 |    0 |
|                            10.254.254.1 -   18 |  334 |  276 |  122 |  123 |  150 |  122 |
|                          10.255.252.234 -   20 |  318 |  256 |  122 |  124 |  411 |  122 |
|ec2-54-150-128-27.ap-northeast-1.compute.amazonaws.com -   19 |  322 |  261 |    0 |  144 |  424 |  127 |
|                   No response from host -  100 |  113 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  113 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  113 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  113 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  113 |    0 |    0 |    0 |    0 |    0 |
|                             100.65.9.65 -   21 |  307 |  243 |  122 |  125 |  407 |  123 |
|                            52.95.30.217 -   21 |  311 |  248 |  124 |  127 |  415 |  125 |
|                            52.95.31.127 -   21 |  310 |  246 |  125 |  127 |  147 |  132 |
|                             52.95.31.30 -   46 |  199 |  108 |  125 |  128 |  146 |  127 |
|                           100.91.149.34 -   20 |  319 |  258 |  126 |  129 |  412 |  127 |
|                            100.91.3.145 -   22 |  302 |  236 |  126 |  128 |  141 |  129 |
|                           100.91.135.35 -   21 |  314 |  251 |  125 |  128 |  410 |  126 |
|                             52.93.66.94 -   18 |  330 |  271 |  126 |  129 |  155 |  128 |
|                             52.93.66.91 -   19 |  326 |  266 |  126 |  127 |  154 |  127 |
|                   as17685.ix.jpix.ad.jp -   21 |  314 |  251 |  127 |  130 |  191 |  127 |
|                           61.195.56.129 -   21 |  314 |  251 |  127 |  130 |  410 |  128 |
|                          219.117.144.66 -   20 |  318 |  256 |  127 |  131 |  422 |  127 |
|                          219.117.144.45 -   21 |  314 |  251 |  127 |  129 |  383 |  127 |
|                          219.117.144.29 -   24 |  294 |  226 |  127 |  129 |  143 |  127 |
|                         219.117.147.186 -   21 |  307 |  243 |  127 |  129 |  419 |  128 |
|                         124.150.157.158 -   22 |  302 |  236 |  127 |  129 |  419 |  127 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I’m at a loss :sob:

Frankly speaking I’m not what CG-NAT stands for but when I checked your latest result of WinMTR without mudfish, it still points that your packet loss is from your ISP (loop121200160.bng1.ia-dcb.portmel.aussiebb.net). :frowning: