All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandro Dentella <sandro@e-den.it>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tables and default
Date: Mon, 02 Aug 2004 11:06:27 +0000	[thread overview]
Message-ID: <20040802110627.GA2441@bluff> (raw)
In-Reply-To: <20040801155104.GA27013@bluff>

> First thing--I don't know why you are seeing this error from 'ip
> route get'.  This should return the real route chosen.  You could
> always try the ping and then check the route cache.  This should
> help you identify the actual route chosen.
> 
> Here's what's happening.
> 
>   - kernel gets packet and needs to select a route
>   - according to rule 0, we look up in table local
>   - perform route lookup in table local--no match!
>   - according to rule 50, we look up in table bluff
>   - perform route lookup in table local--no match!
>   - according to rule 32767, we look up in table main
>   - perform route lookup in table main-- MATCH!
>   - route packet out default gateway
> 
> If you add a route to table bluff as follows, you should effectively
> prevent 192.168.5.0/24 from reaching any network other than
> 192.168.5.0/24.
> 
>   ip route add blackhole default table bluff

thanks a lot for the explanation. This definitely solved my doubts. The only
remainig problem is the 'ip route get' error. I'm sure that in some moments
yesterday I culd get an answer, now it always give errors, independent from
the rule set...

sandro
*:-)


-- 
Sandro Dentella  *:-)
e-mail: sandro@e-den.it 
http://www.tksql.org                    TkSQL Home page - My GPL work
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-08-02 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 15:51 [LARTC] tables and default Sandro Dentella
2004-08-02  2:21 ` Martin A. Brown
2004-08-02 11:06 ` Sandro Dentella [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=20040802110627.GA2441@bluff \
    --to=sandro@e-den.it \
    --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.