From: Dana Lacoste <dana.lacoste@peregrine.com>
To: "'Luigi Genoni'" <kernel@Expansa.sns.it>,
Amit Gupta <amit.gupta@amd.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: arpd not working in 2.4.17 or 2.5.1
Date: Tue, 15 Jan 2002 11:34:51 -0800 [thread overview]
Message-ID: <B51F07F0080AD511AC4A0002A52CAB445B2AA0@ottonexc1.ottawa.loran.com> (raw)
I have a 2.4 compatible arpd running, but with our
company being bought by a big US software company
I'm having trouble convincing management to allow
the GPL release. It's becoming very important so
I'm hopeful that I'll be successful shortly, but
until then I have to be quiet :)
--
Dana Lacoste - Linux Developer
Peregrine Systems - Ottawa, Canada
(Note that Peregrine acquired Loran, and jlayes@loran.com
is an email address of a former employee, so i'm kind of
the relevant person to talk to for arpd stuff, because that
other address won't work :)
> -----Original Message-----
> From: Luigi Genoni [mailto:kernel@Expansa.sns.it]
> Sent: January 15, 2002 10:03
> To: Amit Gupta
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: arpd not working in 2.4.17 or 2.5.1
>
>
> Latest kernel I saw working with arpd (user space daemon) I
> am manteining
> is 2.2.16, then from 2.4.4 (for 2.4 series), some changes were done to
> kernel so that the kernel does not talk correctly with the device
> /dev/arpd anymore.
> It is not the first time I write about this on lkml, but it
> seems none is
> interested in manteining the kernel space component for arpd support.
> I did some investigation, but the code for arpd support
> itself inside of
> the kernel seems to be ok, something else is wrong with neighour.c.
>
> So at less I can say the user space daemon works well on 2.2.16 I have
> around ;).
>
> Luigi
>
> On Mon, 14 Jan 2002, Amit Gupta wrote:
>
> >
> > 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
> >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next reply other threads:[~2002-01-15 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 19:34 Dana Lacoste [this message]
2002-01-16 11:50 ` Luigi Genoni
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 14:06 Dana Lacoste
2002-01-16 21:15 ` Amit Gupta
2002-01-15 1:08 Amit Gupta
2002-01-15 15:02 ` 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
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=B51F07F0080AD511AC4A0002A52CAB445B2AA0@ottonexc1.ottawa.loran.com \
--to=dana.lacoste@peregrine.com \
--cc=amit.gupta@amd.com \
--cc=kernel@Expansa.sns.it \
--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
all inboxes | Powered by JetHome®