Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Sandro Dentella <sandro@e-den.it>
To: lartc@vger.kernel.org
Subject: [LARTC] tables and default
Date: Sun, 01 Aug 2004 15:51:04 +0000	[thread overview]
Message-ID: <20040801155104.GA27013@bluff> (raw)

I already setup several 2 gateways boxes, with rules too decide which lan
should use which gateway.

Now I'm stuck with a simpler problem. At home I was just making some
experimental setup:

  *  1 adsl (ppp0)
  *  1 more tables in rt_tables (200 ping) called "bluff"
  *  table 'bluff *has not* a default route

       root@fw-eden root # ip ro li table bluff
       192.168.5.0/24 dev eth1  scope link 

  *  ip rule add from 192.168.5.2 table bluff prio 50

       root@fw-eden root # ip ru li
       0:      from all lookup local 
       50:     from 192.168.5.0/24 lookup bluff 
       32766:  from all lookup main 
       32767:  from all lookup default 


Now I would think that pinging from  192.168.5.2 outside the LAN should not
work and in fact:

    root@fw-eden root # ip ro get 62.207.143.51 from 192.168.5.2
    RTNETLINK answers: Invalid argument

but if I try I can flawlessly get out. Is this related to SNAT? In my opinion
that should come afterwords since SNAT in in the POSTrouting chain.

Any hints?  TYA
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/

             reply	other threads:[~2004-08-01 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 15:51 Sandro Dentella [this message]
2004-08-02  2:21 ` [LARTC] tables and default Martin A. Brown
2004-08-02 11:06 ` Sandro Dentella

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=20040801155104.GA27013@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox