From: Andrew Lunn <andrew@lunn.ch>
To: Tad <ecos_removethispart@ds3switch.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Is arpresolve() good to get ARP started on an IP address?
Date: Thu, 21 Jun 2007 15:07:00 -0000 [thread overview]
Message-ID: <20070620214559.GB8424@lunn.ch> (raw)
In-Reply-To: <4678630E.3050406@ds3switch.com>
On Tue, Jun 19, 2007 at 03:13:18PM -0800, Tad wrote:
> Andrew Lunn wrote:
> >On Tue, Jun 19, 2007 at 12:19:50PM -0800, Tad wrote:
> >
> >>SNMP agent is dropping coldstart and LinkUp traps since ARP table comes
> >>up without entries
> >>
> >
> >Maybe i don't understand what you are saying, but if there is no ARP
> >entry, the IP packet which needs to be sent is normally queued and an
> >ARP request is sent out. Once an ARP reply is received the queues
> >packet is then sent. Is this not happening?
> ARP will only que one mbuf, then drops it if more come in If a
> coldstart and 2 link-up traps occur at powerup, and if we have 2
> trapsinks, for example, that's 6 msgs of which 4-5 are dropped. I need
> to update the ipdropped snmp stats counter too, cause it took awhile to
> figure out where the missing packets were going. Looked tricky to use
> arpresolve? without dropping any mbuf queued there also.
Ah, O.K. Well, two comments:
SNMP is designed to be unreliable. It uses UDP. So this is acceptable
behaviour.
You could change the single mbuf into a queue. All the macros to do
this exist, so i doubt it would be too big a job.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-06-20 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 19:59 Tad
2007-06-19 22:39 ` Andrew Lunn
2007-06-20 13:12 ` Tad
[not found] ` <4678630E.3050406@ds3switch.com>
2007-06-21 15:07 ` Andrew Lunn [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=20070620214559.GB8424@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ecos_removethispart@ds3switch.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).