All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Sun, 11 Jan 2004 21:07:09 +0000	[thread overview]
Message-ID: <200401112107.09764.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <000d01c3d885$8181e710$1684188d@Kiste>

On Sunday 11 January 2004 8:57 pm, Thhoep wrote:

> in my opinion something is completely wrong with my 2.4.23 kernel. i just
> used another server of mine to reproduce the same situation. for this
> purpose i compiled a completely new 2.4.23 kernel with advanced routing and
> netfilter and whatever support and installed fresh versions of the iptables
> and iproute2 package with the debian system (using 'stable').

What version of iptables is that?   Is it as up to date as the netfilter 
version you've got in your shiny new kernel?

> because the host only has 1 ethernet interface i used a ppp-over-ssh tunnel
> to simulate routing behaviour.

This sounds a little bit dodgy to me....

> then i added a firewall rule
> "iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE"
>
> is anything wrong with it??

No, looks perfectly reasonable to me.

> well do make it short: it changed nothing. packets still get un-masqueraded
> out of ppp0 with local lan ips.

Any chance you can put in another ethernet card and try a simpler routing 
setup?

Antony.

-- 
You can spend the whole of your life trying to be popular,
but at the end of the day the size of the crowd at your funeral
will be largely dictated by the weather.

 - Frank Skinner

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-01-11 21:07 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
2004-01-11 20:57                       ` Thhoep
2004-01-11 21:07                         ` Antony Stone [this message]
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=200401112107.09764.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.netfilter.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.