On 11/9/06, Oliver J. Morais <[EMAIL PROTECTED]> wrote:
* Jen Spinney <[EMAIL PROTECTED]> [061107 18:34]:
> while running ethereal/wireshark, it shows me that the TCP checksums
> coming from my requests are always incorrect (the IP checksums are
> fine).
Just a thought:
Maybe you're TCP-Checksu
* Jen Spinney <[EMAIL PROTECTED]> [061107 18:34]:
> while running ethereal/wireshark, it shows me that the TCP checksums
> coming from my requests are always incorrect (the IP checksums are
> fine).
Just a thought:
Maybe you're TCP-Checksum-Offloading on the box running ethereal, so you'll
never
Hi,
If your server is Linux kernel 2.6,then it has a already known bug about the
uncorrect checksum.
If it's not 2.6 kernel,then you maybe want to use tcpdump for a try.I give most
trust to tcpdump than other sniffers.
>
>Nah, I get incorrect checksums without the \n as well. This may be an
>
On 11/7/06, Jeff Pang <[EMAIL PROTECTED]> wrote:
>
>use strict;
>use warnings;
>
>use IO::Socket;
>
>my $sock = IO::Socket::INET->new
>(PeerAddr => 'www.google.com',
> PeerPort => 7,
> Proto=> 'tcp') or die "$!";
>
>print $sock "This is a test\n";
>close $sock;
>__END__
>
Hello,
>
>use strict;
>use warnings;
>
>use IO::Socket;
>
>my $sock = IO::Socket::INET->new
>(PeerAddr => 'www.google.com',
> PeerPort => 7,
> Proto=> 'tcp') or die "$!";
>
>print $sock "This is a test\n";
>close $sock;
>__END__
>
Hello,your script itself has no problems unless the "\n"
Hello.
If I run the following code:
use strict;
use warnings;
use IO::Socket;
my $sock = IO::Socket::INET->new
(PeerAddr => 'www.google.com',
PeerPort => 7,
Proto=> 'tcp') or die "$!";
print $sock "This is a test\n";
close $sock;
__END__
while running ethereal/wireshark, it sh
