From: "Amit Gupta" <amit.gupta@amd.com>
To: linux-kernel@vger.kernel.org
Subject: arpd not working in 2.4.17 or 2.5.1
Date: Mon, 14 Jan 2002 17:08:02 -0800 [thread overview]
Message-ID: <3C4380F2.292475B9@cmdmail.amd.com> (raw)
Hi All,
I am running 2.5.1 kernel on a 2 AMD processor system and have enable
routing messages, netlink and arpd support inside kernel as described in
arpd docs.
Then after making 36 character devices, when I run arpd, it's starts up
but always keeps silent (strace) and the kernel also does not keep it's
256 arp address limit.
Pls help fix it, I need linux to be able to talk to more than 1024
clients.
Thanks in Advance.
Amit
amit.gupta@amd.com
next reply other threads:[~2002-01-15 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 1:08 Amit Gupta [this message]
2002-01-15 15:02 ` arpd not working in 2.4.17 or 2.5.1 Luigi Genoni
2002-01-15 18:59 ` Amit Gupta
2002-01-15 19:58 ` Alan Cox
2002-01-16 11:48 ` Luigi Genoni
2002-01-16 17:33 ` Amit Gupta
2002-01-17 19:49 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 19:34 Dana Lacoste
2002-01-16 11:50 ` Luigi Genoni
2002-01-16 14:06 Dana Lacoste
2002-01-16 21:15 ` Amit Gupta
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=3C4380F2.292475B9@cmdmail.amd.com \
--to=amit.gupta@amd.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox