From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] A complicated routing scenario (for me at least)
Date: Fri, 17 Nov 2000 13:00:05 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216946@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216914@msgid-missing>
<PRE>On Thu, 16 Nov 2000, Andrew wrote:
><i> Hey, I'm working on the rules and routes to implement what I've been talking
</I>><i> about, and I've got a small question about the ip rule add.
</I>
><i> I'm trying to add a blackhole route, and ip rule add seems to insist that I
</I>><i> provide a lookup table with the route.
</I>><i>
</I>><i> For instance If I execute the command:
</I>><i>
</I>><i> "ip rule add from 0.0.0.0/0 type blackhole."
</I>><i>
</I>><i> when I look at what it did with "ip rule ls" I see
</I>><i>
</I>><i> "from all lookup main blackhole"
</I>
Try using ip rule add priority 256 from 0.0.0.0/0 type blackhole
Doei, Arthur. (There's some hints as to the priority being required in the
IP command reference)
--
/\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
</PRE>
next prev parent reply other threads:[~2000-11-17 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:58 [LARTC] A complicated routing scenario (for me at least) Andrew
2000-11-14 14:34 ` Arthur
2000-11-14 14:44 ` Wingtung.Leung
2000-11-14 20:15 ` Andrew
2000-11-14 21:47 ` Whit
2000-11-14 23:10 ` Wingtung.Leung
2000-11-15 10:49 ` Arthur
2000-11-15 11:27 ` Arthur
2000-11-15 14:57 ` Warren
2000-11-15 19:20 ` Andrew
2000-11-15 19:30 ` Arthur
2000-11-15 20:11 ` Andrew
2000-11-17 1:07 ` Andrew
2000-11-17 12:11 ` Mike
2000-11-17 12:24 ` Mike
2000-11-17 13:00 ` Arthur [this message]
2000-11-17 21:25 ` Mike
2000-11-18 16:28 ` Warren
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-98373938216946@msgid-missing \
--to=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 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.