From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] route with different metric
Date: Wed, 26 Sep 2001 21:16:32 +0000 [thread overview]
Message-ID: <marc-lartc-100153899313282@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100150978014261@msgid-missing>
On Wed, Sep 26, 2001 at 10:53:35PM +0200, bert hubert wrote:
> That sometimes happens - policy routing can help with that problem:
>
> $ ip rule ls
> 0: from all lookup local
> 32765: from 213.156.3.162 lookup pine
> 32766: from all lookup main
> 32767: from all lookup default
>
> $ ip route ls
> 195.190.241.81 dev ppp0 proto kernel scope link src 194.109.252.152
> 213.156.3.160/28 dev eth1 proto kernel scope link src 213.156.3.162
> 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.150
> 192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.1
> default via 195.190.241.81 dev ppp0
>
> $ ip route ls table pine
> default via 213.156.3.161 dev eth1
>
> This forces packets to go the right way.
Ah! I knew there must have been a way... Thanks!
--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.enfusion-group.com] 5:12pm up 55 days, 8:22, 4 users
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-09-26 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 13:10 [LARTC] route with different metric Christian Lox
2001-09-26 13:13 ` bert hubert
2001-09-26 13:39 ` Christoph Simon
2001-09-26 13:45 ` Juri Haberland
2001-09-26 13:53 ` Juri Haberland
2001-09-26 14:10 ` bert hubert
2001-09-26 14:37 ` Juri Haberland
2001-09-26 18:05 ` Adrian Chung
2001-09-26 20:53 ` bert hubert
2001-09-26 21:16 ` Adrian Chung [this message]
2001-09-27 7:44 ` Juri Haberland
2001-09-27 22:40 ` Adrian Chung
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-100153899313282@msgid-missing \
--to=adrian@enfusion-group.com \
--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.