From: Fredrik Noring <noring@nocrew.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PAN data corruption
Date: Sat, 24 Jan 2004 12:53:07 +0100 [thread overview]
Message-ID: <1074945187.6007.46.camel@localhost.localdomain> (raw)
In-Reply-To: <1074941532.6007.22.camel@localhost.localdomain>
> - Using scp, copying more than a few megabytes often gives
> "Corrupted MAC on input".
>
> - Using netcat, copying a 53244356 byte source file results
> in a 53243904 byte destination file. It stops 452 bytes short
> of a complete file.
Aborting netcat gives a complete file (with a correct md5sum) so it
didn't trig a problem. The scp error remains.
Fredrik
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-01-24 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 10:52 [Bluez-devel] PAN data corruption Fredrik Noring
2004-01-24 11:53 ` Fredrik Noring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074945187.6007.46.camel@localhost.localdomain \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox