All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M.F. PSIkappa" <psi@platon.atlantis.sk>
To: lartc@vger.kernel.org
Subject: [LARTC] Differencie between route and route-rule
Date: Wed, 18 Apr 2001 15:58:47 +0000	[thread overview]
Message-ID: <marc-lartc-98760969913615@msgid-missing> (raw)

HI,
could you explain what's difference between this two examples ?

ip addr add 10.10.10.3/24 brd + dev eth0
ip addr add 192.168.1.254/24 brd + dev eth1
ip route add default 10.10.10.1

# first case
ip route add via 10.10.10.5 table 100
ip rule add to 192.168.2.0/24 table 100

# second case
ip route add to 192.168.2.0/24 via 10.10.10.5

In 1st case it make some stange thing. In 2nd case it work fine. I only 
see one difference that in 2nd case is all in table main. 
I would like if somebody explain me what happed in 1st and in 2nd case.

PSIkappa
psi@atlantis.sk

PS: sorry for my english


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

                 reply	other threads:[~2001-04-18 15:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-98760969913615@msgid-missing \
    --to=psi@platon.atlantis.sk \
    --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 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.