CClientSocket.Fetch

Hey,

getting these errors:
CClientSocket.Fetch: ip = , size = 2063597832

Other Cache Connection - IP :

Other Cache Connection - IP :

CClientSocket.Fetch: ip = , size = 790647882

CClientSocket.Fetch: ip = , size = 790647882

CClientSocket.Fetch: ip = , size = 790647882

Other Cache Connection - IP :

..and Core and/or Database Server are dying.
haven't found a solution for it yet, so as i did not find some kind of fix for it online.
There are no other player on the server, just a test server, so not sure what kind of packets those could be.

Does anyone know something about it?
Would appreciate!

Thanks~ !

If I am not mistaken, it is the same problem/error. Just take a look and if I am wrong, just let me know. :)

• [Only registered and activated users can see links. Click Here To Register...]

Regards,
Icetea

secure your port in the server. do not off firewall

I found the same post too @[Only registered and activated users can see links. Click Here To Register...], but i have not much knowledge about the packet encryption tbh.
Thought someone could had the same problems and would share some information in more detail with me.

About the firewall, ports are blocked except flyff ports. Usually the ip i use shouldn't be public so i would be curious if i would be getting attacks or anything

Code:

Quote:

if( dwDataSize > MAX_BUFFER ) // if( uPacketSize > MAX_BUFFER ) // kang: 2008/08/14 { char lpAddr[16] = { 0,}; GetPeerAddr( DPID_UNKNOWN, lpAddr, NULL ); Error( "CClientSocket.Fetch: ip = %s, size = %d", lpAddr, dwDataSize ); WSASetLastError( ERROR_BAD_NET_NAME ); return NULL; }

So the "MAX_BUFFER" is 8192 and you try to fetch 790647882.

What source do you use? there is nothing wrong with the net protocol (NEVER TOUCH THIS!!)

This are corrupted packets.

Possible problems:

- Packet encryption (Just useless..) implemented wrong
- You try to send corrupted packets.
- Someone took his hands on the CAr buffer (NEVER TOUCH THIS TOO!!)

I need more information to help you.

Ps.: Debug that, look in stack.

I believe those are the files that someone called FlyffGuru sells(?). Pretty sure~
I didn't play around with any of the points you listed.
Also AES crypt can't have anything to do with it (can it?). I mean, it wouldn't make sense to me but can't imagine what could even cause the problems.
Ask me anything specific and i'll try to provide you the informations.
Also tell me if there is anything i could test and i will test it!

Need to wait for the next crash as it doesn't come more than once a day.. Sometimes it takes even longer, also when noone's around ~

Thanks for trying to help so far.

Quote:

Originally Posted by XimbaForEver I believe those are the files that someone called FlyffGuru sells(?). Pretty sure~ I didn't play around with any of the points you listed. Also AES crypt can't have anything to do with it (can it?). I mean, it wouldn't make sense to me but can't imagine what could even cause the problems. Ask me anything specific and i'll try to provide you the informations. Also tell me if there is anything i could test and i will test it! Need to wait for the next crash as it doesn't come more than once a day.. Sometimes it takes even longer, also when noone's around ~ Thanks for trying to help so far.

There are so many better variations of sources and even free ones out there.

Instead of these scam files that Jonas Garcia aka Tweeney has been scamming people with for years with his pal Rayjens Code.

I am 100% sure that someone modify the net code.

Guys, just stop using this "packet encryption" nonsense. It is useless.

You have two way's now:

1. Resolve that issue in the netcode.
or
2. Delete the source and use another one without changes in the netcode.


Why using an packet encryption? to be safe? nope, thats just a false information. It is easy to get around this. Just fix the problems on the server side and hey, the "cheater" can send packets, who cares?

I have to agree about him. Those files really aren't great at all and totally not worth it, but i already spend a lot of effort into those files for what reason ever. Thought they might be usable.
Anyways, i am willing to try looking into it and find out where the problem is, do you have any tips for that or even where to start?

Thanks for answering all that!

Quote:

Originally Posted by XimbaForEver I have to agree about him. Those files really aren't great at all and totally not worth it, but i already spend a lot of effort into those files for what reason ever. Thought they might be usable. Anyways, i am willing to try looking into it and find out where the problem is, do you have any tips for that or even where to start? Thanks for answering all that!

Hi @[Only registered and activated users can see links. Click Here To Register...] Have you fix your problem? coz im having the same problem as your's im using k18.3 files can anyone help please? :handsdown:

i have related same issue does anyone know how to fix it?