From: "Navin Boppuri" <nboppuri@trinetcommunication.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Neighbour Table Overflow on NFS Server
Date: Fri, 29 Dec 2000 09:47:23 -0000 [thread overview]
Message-ID: <001f01c0717c$58183a00$4a1f76d8@washington> (raw)
Hello everyone,
Thank you very much for all your replies. From all the answers, I can
understand that there can be two main reasons,
1) The connection to the server is messy due to either physical
connectivity issues or server issues
2) Ethernet driver is messy.
Taking into account the first problem, I tried changing ethernet cables, hub
etc. but it did not help. The network is working just fine. We are able to
connect to the Internet, and to other machines in our network. Everything
else works fine. The funny thing is that I do a tftp of the zImage and that
part of it works just fine. It seems to be the NFS Server that fails. Now, I
did not change any settings in the NFS server from the last time it worked,
which was just a day back.
The strangest thing is that none of the NFS Server's I tried setting up on
my other linux machines seem to be working.
I am sure the ethernet driver is fine since the tftp works just fine. It's
been doing well from quite some time.
With all these factors, it has become very difficult to pinpoint to a
particular cause of failure. I am in the process of testing an important
driver till this popped up.
Thank you,
Navin Boppuri
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-29 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 9:47 Navin Boppuri [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-28 14:54 Neighbour Table Overflow on NFS Server Navin Boppuri
2000-12-28 22:06 ` Cal Erickson
2000-12-29 6:03 ` Mark S. Mathews
2000-12-29 12:46 ` Chris Hallinan
2000-12-29 9:53 ` Navin Boppuri
2000-12-29 12:33 ` Navin Boppuri
2000-12-29 1:33 ` clark
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='001f01c0717c$58183a00$4a1f76d8@washington' \
--to=nboppuri@trinetcommunication.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).