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: [LARTC] Activate ingress policies on suse ent	erpr ise serv	er 9
Date: Tue, 26 Apr 2005 22:30:13 +0000	[thread overview]
Message-ID: <426EC0F5.3040604@dsl.pipex.com> (raw)
In-Reply-To: <E650DED25A93D71184B80002B3CC411D84F54A@vies1a1a.sie.siemens.at>

Grames Gernot wrote:
>  
> Hi,
> 
> The problem is this is my goal to use the policier and not the iptables.
> Because with the policier i think you can give more rules and restrictions
> to the incoming tcpip traffic.

You can limit with iptables aswell as drop.

> 
> So I would prefer to use the policier and not the iptables.

I just looked and AFAICT you will need a newer kernel than the 2.6.5 
that your suse is using maybe suse do a more recent one - I don't know 
about doing kernels on suse - you'll have to see suse docs or ask on a 
suse group about doing kernels as you haven't done it before.

The option that you need selected after doing a make menuconfig is 
packet actions in Qos and/or fair queuing under networking options under 
networking support under Device drivers.

When you select that you can then select policing actions and it will be 
the new policer.

I don't know where your current config is - but try and find it and use 
it as a base when doing a new kernel - you can load it from the make 
menuconfig menus.

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

  parent reply	other threads:[~2005-04-26 22:30 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
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 [this message]
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=426EC0F5.3040604@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.