Callback doesn't works in TCP socket.

[Mateus Sousa]

Hi,

I'm simulating a simple client-server app, but the tcp socket setRecvCallback isn't working. And there is not TCP packets in the traces/pcaps.

Can someone figure out the problem?

[Konstantinos]

Hi Mateus,

Please read the posting guidelines, particularly the part on how to ask for help.

You haven't provided details for your simulation, whether you created a new application etc.

A minimal working example would be needed.

Regards,

K

[Mateus Sousa]

Sorry Konstantinos,
my mistake.

I'm simulating a simple client-server app in a VANETs environment. Here are the steps of my app:
1º Starts a service discovery by sending broadcasts messages to the neighbours;
2º Listen for replies and choose the best providers;
3º Starts a connection with the providers, one by one, and send the req pkts;
4º Listen for replies; # <- Here is the problem, the RecvCallback doesn't works.

I can't send my code (orders from my guide);

Thanks in advance.

[Matt Anonyme]

Might be that you set the callback only on the original server socket but you need to set the callback on the forked server socket ?

[Tommaso Pecorella]

I'm almost sure that this is the case.

Please check the PacketSink::HandleAccept code.

T.

[Mateus Sousa]

Ok, I will.

Thanks for the support!