All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamen TOMOV <kamen@evrocom.net>
To: lartc@vger.kernel.org
Subject: [LARTC] help on routing
Date: Fri, 02 Mar 2007 08:41:38 +0000	[thread overview]
Message-ID: <uhct4rq9p.fsf@cybuild.com> (raw)

We have a router with two external and one internal interfaces and it
doesn't work as we'd like to. We need it to route all the trafic
through one of the external interfaces and to access a few networks
through the other.

Currently it seems that all the packets with source address from the
inernal network are routed correctly. The problem is with the packets
that originate from the router. For some reason they are routed
through the default interface. Does anybody know why does that happen?

# ip rule ls
0:      from all lookup local
200:    from 192.168.1.0/24 to a.b.c.0/24 lookup 202
201:    from e.f.g.0/24 lookup 201
201:    from 192.168.1.0/24 to 62.44.96.0/19 lookup 201
201:    from 127.0.0.0/8 to 62.44.96.0 lookup 201
202:    from a.b.c.0/24 lookup 202
32766:  from all lookup main
32767:  from all lookup default

# ip route ls
e.f.g.0/24 dev eth3  scope link  metric 1
a.b.c.0/24 dev eth2  scope link
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.1
127.0.0.0/8 dev lo  scope link
default via a.b.c.1 dev eth2

ip route ls table 201
default via e.f.g.1 dev eth3  proto static  src e.f.g.52 realm 201
prohibit default  proto static  metric 1

ip route ls table 202
default via a.b.c.1 dev eth2  proto static  src a.b.c.4 realm 202
prohibit default  proto static  metric 1

Your help is appreciated.

-- 
Камен
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-03-02  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  8:41 Kamen TOMOV [this message]
2007-03-04 11:37 ` [LARTC] help on routing Ivan Vladimirov
2007-03-04 12:12 ` Ivan Vladimirov

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=uhct4rq9p.fsf@cybuild.com \
    --to=kamen@evrocom.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 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.