All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: AW: AW: AW: AW: [LARTC] Activate ingress policies on suse enterpr
Date: Fri, 22 Apr 2005 23:34:27 +0000	[thread overview]
Message-ID: <42698A03.4000402@dsl.pipex.com> (raw)
In-Reply-To: <E650DED25A93D71184B80002B3CC411D84F54A@vies1a1a.sie.siemens.at>

Grames Gernot wrote:
> Hi,
> 
> So far, if have understand correctly: I route the incoming tcpip message of
> port 8099 directly to 8080 and then the ingress filter on port 8099 has
> nothing to do!?
> 
> Yes I think on different interface on one machine (different Ports for
> different Request, with different restriction).
> 
> What has exactly to be done to set the policier before Prerouting!
> Which kernel options, or also extra modules!?

On recent kernels if you select packet action in Qos and/or fair queuing 
of config the policer will be before PREROUTING.

> 
> Or how it can be done on iptable level??

You could have your DNAT rule only for packets from the interface you 
want eg .... -i eth1 DNAT ...... would only do packets inbound from eth1.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-04-22 23:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 11:19 [LARTC] Activate ingress policies on suse enterprise server 9 Grames Gernot
2005-04-18 13:01 ` Andy Furniss
2005-04-18 13:13 ` AW: " Grames Gernot
2005-04-18 14:05 ` Andy Furniss
2005-04-19  5:55 ` AW: AW: [LARTC] Activate ingress policies on suse enterprise serv er 9 Grames Gernot
2005-04-19 21:50 ` AW: AW: [LARTC] Activate ingress policies on suse enterprise Andy Furniss
2005-04-20  6:06 ` AW: " Grames Gernot
2005-04-21 20:46 ` Andy Furniss
2005-04-22  6:25 ` AW: AW: AW: AW: [LARTC] Activate ingress policies on suse enterpr Grames Gernot
2005-04-22 23:34 ` Andy Furniss [this message]
2005-04-26  5:58 ` [LARTC] Activate ingress policies on suse ent erpr ise serv er 9 Grames Gernot
2005-04-26 22:30 ` Andy Furniss
2005-04-27  6:03 ` AW: [LARTC] Activate ingress policies on suse ent erpr ise serv e r 9 Grames Gernot
2005-04-27 19:51 ` AW: [LARTC] Activate ingress policies on suse ent erpr ise serv Andy Furniss

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=42698A03.4000402@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.