All of lore.kernel.org
 help / color / mirror / Atom feed
From: bash <0x62ash@gmail.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: help me
Date: Wed, 29 Mar 2006 07:29:33 +0400	[thread overview]
Message-ID: <20060329072933.26ba1e7a.0x62ash@gmail.com> (raw)
In-Reply-To: <1143597051.12219.91.camel@localhost>

On Tue, 28 Mar 2006 20:50:51 -0500
"John A. Sullivan III" <jsullivan@opensourcedevel.com> wrote:

> On Wed, 2006-03-29 at 04:19 +0400, bash wrote:
> >  Hello All,
> > 
> > I wanna dynamically block some ip's that load my router with --state NEW
> > packets (usually it's generated by very aggressive NetLook win
> > program). But there is a problem -m limit will block all my router's
> > user, and I wanna block just one ip :/
> I'm not entirely sure of what you want to do.  Why can you not match
> source? If you want, match the one IP and send all traffic for that IP
> to a user defined chain, e.g., :
> iptables -A FORWARD -s 10.1.1.100 -j SpecialChain
> iptables -A SpecialChain -j DOWHATEVERYOUWANT
> 
> If it is that you want to exempt certain addresses, send all the packets
> to a user defined chain and return the exemptions, e.g., 
> 
> iptables -A FORWARD -j LimitChain
> iptables -A LimitChain -m iprange --src-range 10.1.1.70-10.1.1.223 -j
> RETURN
> iptables -A LimitChain -j LOG, DROP, LIMIT, WHATEVERYOUWANTTODO

The problem is that I don't know IP of this machine.... And anyone in
my net can run NetLook program... So i want that - if some-one in my net
exceed limit then iptables will block this ip dynamically.... 

-- 
Biomechanica Artificial Sabotage Humanoid


  reply	other threads:[~2006-03-29  3:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29  0:19 help me bash
2006-03-29  1:50 ` John A. Sullivan III
2006-03-29  3:29   ` bash [this message]
2006-03-29  4:22     ` help me (nfcan: addressed to exclusive sender for this address) Jim Laurino
2006-03-29 17:54       ` bash
2006-03-29 18:28         ` Rob Sterenborg
2006-03-29 19:14           ` bash
2006-03-30  5:45             ` Rob Sterenborg
2006-03-30 15:58               ` bash
  -- strict thread matches above, loose matches on Subject: below --
2019-04-07 23:46 Help Me Ms. Heba Oudeh
2014-09-10 12:02 Alina Yukov
2010-07-01  5:01 help me oleg ershov
2010-07-01  5:36 ` Mike Frysinger
2007-01-04  6:21 Help me Debasree Mallick
2007-01-04  8:26 ` Matthew Palmer
2007-01-05  7:31   ` Debasree Mallick
2007-01-05  7:31   ` Debasree Mallick
2006-11-26 10:01 help me ahmed nabel
2006-05-09  9:44 abdul hafeez
2005-07-04 10:39 umar draz
2005-07-04 10:47 ` Christoph Georgi
2005-07-04 13:45   ` /dev/rob0
2004-11-29 11:41 Help Me Umar Draz
2004-11-29 12:02 ` DervishD
2004-09-17 13:08 HELP ME Marcel Bogdan
2004-05-23 14:51 [Bluez-users] help me Vitaliy
2004-05-23 15:01 ` Marcel Holtmann
2004-05-23 15:20   ` [Bluez-users] " Vitaliy
2004-05-23 15:30     ` Marcel Holtmann
2004-05-23 15:48       ` Vitaliy Pronkin
2004-05-23 16:04         ` Marcel Holtmann
2004-05-23 16:12           ` Vitaliy Pronkin
2003-06-10 22:20 Help Me George Vieira
2003-06-10  6:31 Pham Dinh Hieu
2003-04-26  4:52 Help me cyberyam
2002-10-31  4:01 help me 곽동원
2001-06-28 21:05 Help me 강신규
2001-06-28 16:43 ` Ralph Metzler
2001-06-29 13:28   ` 강신규
2001-07-02 13:47   ` 강신규

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=20060329072933.26ba1e7a.0x62ash@gmail.com \
    --to=0x62ash@gmail.com \
    --cc=jsullivan@opensourcedevel.com \
    --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.