From: Wojtek <voyo@punkt.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to force iproute2 to FORWARD to another interface
Date: Thu, 29 Aug 2002 12:07:08 +0000 [thread overview]
Message-ID: <marc-lartc-103062279528026@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103028115623453@msgid-missing>
Jan Macek wrote:
> I have this situation:
>
> 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).
>
> How to achieve that?
>
you can use set of 'ip rule' and other routing table
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-29 12:07 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 ` Wojtek [this message]
2002-09-02 12:58 ` [LARTC] how to force iproute2 to FORWARD to another interface Miernik
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-103062279528026@msgid-missing \
--to=voyo@punkt.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.