in reply to Network Reliability Testing, problems with buffered sockets?

While not a perl solution, how about using a linux box and using tcpdump? Or a real packet analyzer? There are free ones available on the net.

As a complete stab in the dark, I have run across something like this ages ago, turned out to be an email message that kept getting bounced back and forth between two email servers, each adding a "he's on vacation" message to the end. We found it about 3 days after it had started, and it was gigantic.

Good luck

-Scott

  • Comment on Re: Network Reliability Testing, problems with buffered sockets?

Replies are listed 'Best First'.
Re^2: Network Reliability Testing, problems with buffered sockets?
by naxxtor (Initiate) on Mar 21, 2007 at 16:14 UTC

    Oddly enough I've come across something similar before, except it was with a spam filter labelling something as spam, then the server rejecting the unknown header and sending it back to the spam filter, which labelled it as spam and returned it again.

    I did think about using packet sniffing/logging to analyse the flow, but unfortunately it wouldn't give me enough information, and I'd need to work out how to track the connection.

    Thanks for the idea :)

[reply]
      I think maybe you're in tunnel vision mode with the problem. It sounds like you're assuming there's something wrong with a single application's packet flows. I'm betting there's a better chance that there is other traffic that is using enough bandwidth to keep the one application from responding well. A sniffer would allow you to see all the traffic, not just the one application you're having issues with.

      -Scott

[reply]

In Section Seekers of Perl Wisdom