From: Bernd Eckenfels <ecki-news2002-01@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: strange kernel message when hacking the NIC driver
Date: Mon, 14 Jan 2002 08:41:00 +0100 [thread overview]
Message-ID: <E16Q1jo-0006Op-00@sites.inka.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201140831240.28735-100000@netfinity.realnet.co.sz>
In article <Pine.LNX.4.33.0201140831240.28735-100000@netfinity.realnet.co.sz> you wrote:
> Using your argument... Everytime my feline decides to chew my ethernet
> cable i lose my network connection, hence i get ICMP HOST UNREACHABLE ergo
> my cat has very much to do with ARP.
> Those are errors just filtering up the layers, same way an app doesn't
> know anything about what device you're writing to, but will complain about
> incomplete data writes if you run out of space.
Well actually, the neighbour alive discovery done by arp influences the
routing cache very much. Therefore recent Linux networking is actually able to
send "Host unreachable" messages based on the fact, that an host is down.
You are right, that it is not closely related, but it is something one should
not forget, since it is a behaviour introduced in 2.2 kernels, I think.
You can check it with "ip neig". Entries which have an unreachable host are
marked with "nud failed".
Greetings
Bernd
next prev parent reply other threads:[~2002-01-14 7:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 6:32 strange kernel message when hacking the NIC driver Zwane Mwaikambo
2002-01-14 7:41 ` Bernd Eckenfels [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 4:19 Pei Zheng
2002-01-11 5:20 ` Timothy Covell
2002-01-11 11:55 ` Timothy Covell
2002-01-11 12:07 ` David S. Miller
2002-01-11 12:20 ` Timothy Covell
2002-01-11 12:28 ` David S. Miller
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:44 ` Timothy Covell
2002-01-11 13:11 ` Alan Cox
2002-01-11 19:02 ` Timothy Covell
2002-01-11 19:24 ` Paul Walmsley
2002-01-11 22:51 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:58 ` Timothy Covell
2002-01-11 19:33 ` Pei Zheng
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=E16Q1jo-0006Op-00@sites.inka.de \
--to=ecki-news2002-01@lina.inka.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.