From: Jan De Luyck <lkml@kcore.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-net@vger.kernel.org
Subject: Re: ARP routing issue - semi-solved
Date: Mon, 24 Jan 2005 11:40:30 +0100 [thread overview]
Message-ID: <200501241140.31464.lkml@kcore.org> (raw)
In-Reply-To: <1105829477.16028.0.camel@localhost.localdomain>
Hello lists,
Just for the archive records: we solved it this way (with the good help of IBM):
# ip route add 10.0.24.0/24 dev eth1 proto kernel scope link src 10.0.24.xxx table 1
# ip route add default via 10.0.24.1 dev eth1 table 1
# ip rule add from 10.0.24.xxx/32 table 1 priority 500
# ip route flush cache
Which is now run at bootup on the affected servers, giving us the solve we need.
Thanks everyone who replied.
Jan
--
Auribus teneo lupum.
[I hold a wolf by the ears.]
[Boy, it *sounds* good. But what does it *mean*?]
prev parent reply other threads:[~2005-01-24 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 16:06 ARP routing issue Steve Iribarne
2005-01-06 16:11 ` Jan De Luyck
2005-01-06 17:53 ` Paul Rolland
2005-01-06 17:57 ` Jan De Luyck
2005-01-14 22:47 ` James Courtier-Dutton
2005-01-15 12:31 ` Jan De Luyck
2005-01-15 22:51 ` Alan Cox
2005-01-24 10:40 ` Jan De Luyck [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=200501241140.31464.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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