From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [ECOS] i82559 and FreeBSD stack
Date: Thu, 27 Feb 2003 13:26:00 -0000 [thread overview]
Message-ID: <20030227132554.GK14616@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <1046351601.31018.10172.camel@hermes.chez-thomas.org>
> It works fine for me (I just tried it here). I also know that
> I did most of the original testing using such interfaces.
>
> What kinds of problems exactly do you have?
I've not debugged it much, so cannot give much detail.
I noticed the problem when testing the SNMP changes for the FreeBSD
patch. Im using an AFE1, thats ascom's hardware which is not in the
anoncvs tree. Im using a HAL from 1.5.2. All works fine for OpenBSD.
but the snmpping test program has problems with FreeBSD. The snmpwalk
works, but its very slow. I used tcpdump which showed it was making
lots of retransmits of requests because the target was not replying.
I then pinged the target from my linux host and got around 25% packet
loss. This does not show what is broken, RX or TX. So lastly i look at
tcpdump while snmpping was pinging my server as returned by DHCP. 1 in
4 ICMP echo requests were not making it to my host. So i think there
is something broken in the transmit path.
Hopefully over the weekend i can spend some more time to try to track
down the problem.
Andrew
prev parent reply other threads:[~2003-02-27 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030225091019.GW11159@biferten.ma.tech.ascom.ch>
2003-02-27 8:38 ` Andrew Lunn
2003-02-27 13:13 ` Gary Thomas
2003-02-27 13:26 ` 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=20030227132554.GK14616@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=gary@mlbassoc.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).