From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] difference between ip(a part of iproute2) and route?
Date: Tue, 12 Jun 2001 02:50:43 +0000 [thread overview]
Message-ID: <marc-lartc-99231433809551@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99231164604968@msgid-missing>
On Tue, Jun 12, 2001 at 10:08:55AM +0800, Chuanbo Xu wrote:
>
> ip can do what route do. However, what difference between ip and route is there?
ip can do what route does and much much more. Have you taken a look at the
documentations? Have you noticed that ip gives you muliple routing tables
and the ability to define rules for routing purposes?
http://ds9a.nl/2.4Routing/HOWTO//cvs/2.4routing/output/2.4routing.html
Ramin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-06-12 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 2:08 [LARTC] difference between ip(a part of iproute2) and route? Chuanbo Xu
2001-06-12 2:50 ` Ramin Alidousti [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=marc-lartc-99231433809551@msgid-missing \
--to=ramin@uu.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