Sending S->C Packet || Filter & DLL Communication

09/12/2018 20:02 #HB#1

Hey there,

So, recently I was trying make a communication between my filter and the DLL file.

Simply, I used the known SroPP library's packet handling, which receives S->C only afaik.

And I tried to send a unknown packet like 0xA987 from my filter to the client, so when the DLL receive file receive that 0xA987, it will do some work.

While trying to send the packet from my filter to the client:

Code:

                    Packet packet = new Packet(0xA987);
                    packet.WriteInt32(1);
                    user.m_LocalSecurity.Send(packet);
                    user.Send(false);

The client got crashed, and it's ofc not my DLL file. Also, as far as I am not blind, my code of the packet sending is fine.

Have anyone got an idea about this?

Spoiler

09/13/2018 02:43 athena1410#2

Because you must use packet in list original packet of sro. Choose the packet in original list for yourself and transfer data through it. Contact me if you can't make for yourself!

09/13/2018 17:27 #HB#3

Why can't I use a new packet which doesn't exist?

09/13/2018 20:45 B1Q#4

Quote:

Originally Posted by #HB

Why can't I use a new packet which doesn't exist?

i suppose each client has a list of "AVAILABLE" opcodes (structs)
upon receiving a header the client checks if the opcode matches any and then checks the size

09/14/2018 01:00 #HB#5

#Request_Close