From: Prasanna Kumar K <kumarkp@knowsys.net>
To: linux-x25@vger.kernel.org
Subject: Blocking write and read on X.25 sockets
Date: Mon, 22 Apr 2002 11:46:23 +0530 [thread overview]
Message-ID: <3CC3AAB7.5000009@knowsys.net> (raw)
Hi Group,
I have a strange problem in using the X.25 under linux. I have a
server listenining on x.25 socket and a x.25 client sending data to the
server. The client writes data in a chunk of 256 bytes in a while loop
and the server stores the data received to a file. Things work fine for
sometime. But, after successfully transferring some data (size varies
from about 50k to 500k) the write call at the client and the read call
at the server both blocks. After certain time, both come out indicating
"Network unreachable" (error number 101).
I also observe that the server has received about 20k data less that
what is successfully written by the client!
Can anyone help me in identifying what's going wrong!? Here are the
details on my environmet:
NET4: LAPB for Linux. Version 0.01 for NET4.0
X.25 for Linux. Version 0.2 for Linux 2.1.15
LAPB Ethernet driver version 0.01
Redhat Linux: 2.4.2-2
X.25 server address: 123451234512345
x.25 client address: 123451234512344
Thanks and regards,
:)Prasanna
reply other threads:[~2002-04-22 6:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CC3AAB7.5000009@knowsys.net \
--to=kumarkp@knowsys.net \
--cc=linux-x25@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.