Commonly we expect to see some sample code that is not doing as you expect. Often that will require you to do some research on your own (and maybe ask here: "where can I find info about ... . I've looked 'here', 'there' and 'over there'."). Very often that will involve distilling a script down to just the code that is problematic and providing a sample script demonstrating the problem. Getting to that little stand alone sample script that demonstrates the problem you are having can be a chore (see I know what I mean. Why don't you? for some ideas), but often you will solve the issue yourself in the process.

Anything that hints that you have struggled with the problem for a while and have taken steps to solve it on your own, or at least figure out where it is that you are having trouble, will garner the blessings of the monks.

You could start by doing a search.

The first plain web page (3rd one down) gives a couple of ways to detect syn floods.