I created a custom item for fo

Technical Support
#1

I created a custom item for fortnite using this routing path.

https://pastebin.com/raw/H0nCkFfk

but mudfish didn’t add all CIDR into windows’s route table.

I used route print -4 to check the route table.

here’s the result
https://pastebin.com/raw/kqdLkQQA

it seems mudfish can’t add too much path to the route table?

#2

No idea at this moment because I can’t check the internal log message. When you get this issue again, please show me the log of Mudfish Core found at ‘Status -> Process’ menu.

#3

Here’s the log.
https://pastebin.com/raw/x6yP1C0Z
You can find that some ip ranges are missing.

#4

I think making your own Custom Item may can help to fulfill what you
want

Please download and install latest Mudfish at mudfish.net/download then Create Custom
Item

  1. Take a look and find the daemon process what you want to apply
    Mudfish in Status → Memory
    image

  2. Then create a Custom Item as input the process name like

P:[name].exe

#5

Is this the WFP feature?

#6

image

It seems like there has a length limitation.
After I save the custom item, the last “e” is disappearing.

#7

Ooops… :frowning: I’d fixed this issue on our DB. Please test and let me know if it doesn’t work properly.

#8

Yes it works properly.
But it doesn’t fit my demand.
I set these rules in routing path.
P:FortniteClient-Win64-Shipping.exe
P:FortniteLauncher.exe
P:FortniteClient-Win64-Shipping_BE.exe
P:FortniteClient-Win64-Shipping_EAC.exe
P:EpicGamesLauncher.exe
But the ping is still high though.
So please, can you fix the initial problem?

#9

Please send us some
game packets using Packet Capture with
Mudfish
link while playing the game with Full VPN
mode.

We need some packets to update a Mudfish item. image

image

image

#10

I spent three days to analyzing the packet dump.

here’s the result https://pastebin.com/raw/H0nCkFfk

Works fine on AS matchmaking region.

#11

The question is, I can’t add these CIDR into routing table through your custom item feature.

#12

I simplified the CIDR to this (https://pastebin.com/raw/thXARAnu).

This time it works fine, all ip ranges are added to routing table.

And guess what, my ping gets 20~30ms.

image

But some ip ranges result in Twitch malfunction.

It’s because the simplified CIDR is covering twitch’s ip.
So I need to use the non-simplified version.

#13

If you don’t want to use Windows Filtering Platform via Custom Item then I think it’ll be super-complicated problem to solve

CDN and Mudfish

A way to mitigate this problem I can imagine is blocking every single mal-routing-rules on your system

wf.my.com/forums/showthread.php?t=88107

#14

I want to use WFP but it just dont work properly…

So the answer is you cant solve the ip ranges miss adding problem?

#15

So the answer is you cant solve the ip ranges miss adding problem?

Sorry for this belated response. However could you please send me Problem Report again to analyze this issue? It seems I need to check the routing table and the internal log at the same time.