netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thhoep" <thhoep@gmx.de>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Fri, 9 Jan 2004 23:02:08 +0100	[thread overview]
Message-ID: <001501c3d6fc$3a889c80$1684188d@Kiste> (raw)
In-Reply-To: 006501c3d6f7$d96ecf90$1684188d@Kiste



> i just tried over an hour to bring a tunnel up on one of my other servers,
> so i can simulate routing behaviour with it, but just wasted my time with
> trying to fix a broken ppp installation on it. dont have the patience and
> gotten way too tired to do that right now. so i give you the configuration
> of my testing setup and if you would like to reproduce it i would
appreciate
> it.
>
> iptables -t mangle -A PREROUTING -i eth4 -s 192.168.0.22 -j
MARK --set-mark 1
>

damn, forgot the masquerading rule here:
iptables -t nat -A POSTROUTING -o ppp4 -j MASQUERADE


> ip route add 192.168.0.0/24 dev eth4 table test
>
> ip rule add fwmark 1 table test
> OR
> ip rule add from 192.168.0.22 table test
>
> (these ones done in the ppp ip-up script)
>
> ip route add <remote ip> dev <ppp iface> src <local ip>
> ip route add default via <remote ip> dev <ppp iface>
>
> (dont use a default route in the main table to the same ppp iface, so you
> feel a difference when the routing rules apply or not)
>
>
> thats all i think.
>
>



  reply	other threads:[~2004-01-09 22:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 23:05 Iproute2 and fwmark usage Thhoep
2004-01-09 16:47 ` Ramin Dousti
2004-01-09 16:17   ` Thhoep
2004-01-09 17:35     ` Ramin Dousti
2004-01-09 16:50       ` Thhoep
2004-01-09 19:42         ` Ramin Dousti
2004-01-09 19:06           ` Thhoep
2004-01-09 20:47             ` Ramin Dousti
2004-01-09 20:09               ` Thhoep
2004-01-09 21:22                 ` Ramin Dousti
2004-01-09 21:30                   ` Thhoep
2004-01-09 22:02                     ` Thhoep [this message]
2004-01-11 20:57                       ` Thhoep
2004-01-11 21:07                         ` Antony Stone
2004-01-11 21:50                           ` Thhoep
2004-01-11 23:12                             ` Thhoep
2004-01-11 23:22                               ` Antony Stone
2004-01-13 23:46                               ` Thhoep
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:20 Filter out broadcast messages Gabby James
2004-01-08 14:31 ` iproute2 and fwmark usage Thhoep

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='001501c3d6fc$3a889c80$1684188d@Kiste' \
    --to=thhoep@gmx.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=ramin@cannon.eng.us.uu.net \
    /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;
as well as URLs for NNTP newsgroup(s).