From: Ard van Breemen <ard@kwaak.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip routing problems in 2.4.20
Date: Tue, 06 May 2003 10:52:35 +0000 [thread overview]
Message-ID: <marc-lartc-105221886504786@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105213310523718@msgid-missing>
On Tue, May 06, 2003 at 12:07:32AM +0300, Julian Anastasov wrote:
> On Mon, 5 May 2003, Ard van Breemen wrote:
>
> > Hi,
> > Has anybody noticed that when:
> > ip addr add 192.168.0.1/32 dev eth0
> > ip route add 192.168.0.2/32 dev eth0
>
> It should respond after "ip route flush cache",
Grrrr, thanks Julian.
> you are missing something, I assume eth0 is not down.
Correct. This was just the educational example...
Pfff, I thought I was going insane.... I had a 2.4.18 kernel
talking to a 2.4.20 kernel, except that the 2.4.20 kernel did not
reply on the arps... Now to find something soft to bounce my head
against (I already have the headache, so I don't want it to hurt
extra...).
Eh, just curious in how arp depends on routing... I've already
seen how neigh/gc_thresh[123] can influence the reachability of a
host, and that the routing cache can lock entries in the neigh
table while they are being flushed, filling up the neigh table
etc...
--
mail up 171+00:12, 7 users, load 0.08, 0.20, 0.16
mistar1 up 29+18:16, 17 users, load 0.02, 0.04, 0.00
Let your government know you value your freedom: sign the petition:
http://petition.eurolinux.org
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-06 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 11:09 [LARTC] ip routing problems in 2.4.20 Ard van Breemen
2003-05-05 11:21 ` ulrich schwarz
2003-05-05 12:28 ` Ard van Breemen
2003-05-05 21:07 ` Julian Anastasov
2003-05-06 10:52 ` Ard van Breemen [this message]
2003-05-06 11:42 ` Julian Anastasov
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=marc-lartc-105221886504786@msgid-missing \
--to=ard@kwaak.net \
--cc=lartc@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