All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miernik <miernik@ctnet.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to force iproute2 to FORWARD to another interface
Date: Mon, 02 Sep 2002 12:58:38 +0000	[thread overview]
Message-ID: <marc-lartc-103097158012904@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103028115623453@msgid-missing>

On Thu, 29 Aug 2002, Wojtek wrote:

> > My machine debina, has three interfaces:
> >
> > eth1   212.126.24.129
> > ppp0   10.2.0.1   (Point-to-Point: 212.31.242.98)
> > nsc5   10.2.0.250   (Point-to-Point: 172.23.140.32)
> >
> > I want packets which come in through the nsc5 interface, to be FORWARDED
> > to the ppp0 interface to 212.31.242.98, even when their destination
> > address is 212.126.24.129 (even so this is the IP of eth1 on this
> > machine).
>
> you can use set of 'ip rule' and other routing table

I tried to, but it is not that simple:

The routing table 'local' is bound to the first rule (rule 0), and I
cannot put any other rule before it.

I cannot delete the rule 0.

I tried deleting rules from from the local table, and putting them into
table local2, and assinging rule 2 to table local2, but it didn't work
too: I lost connectivity to my local host.

-- 
Miernik              _____________________________________
                    /   /
tel.: +48603070983 /   /  mailto:miernik@ctnet.pl
__________________/___/  ICQ UIN: 4004001

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

  parent reply	other threads:[~2002-09-02 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 13:11 [LARTC] how to force iproute2 to FORWARD to another interface packets with Jan Macek
2002-08-29 12:07 ` [LARTC] how to force iproute2 to FORWARD to another interface Wojtek
2002-09-02 12:58 ` Miernik [this message]
2002-09-02 15:17 ` David Lamparter

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-103097158012904@msgid-missing \
    --to=miernik@ctnet.pl \
    --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.