From: "hare ram" <hareram@sol.net.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Performanace fo the Iptables Server
Date: Tue, 02 Sep 2003 10:20:39 +0000 [thread overview]
Message-ID: <marc-lartc-106249738828279@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106196327503921@msgid-missing>
Hi Stef
regarding the same topic
if i use
iptables -A INPUT -s 192.168.2.1
iam able to capture packets going fro 192.168.2.1 to any address
how about any address coming to 192.168.2.1
this will be added in to same rule
or i need to add another Rule
iptables -A INPUT -d 192.168.2.1
hare
----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: "hare ram" <hareram@sol.net.in>; <netfilter@lists.samba.org>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, August 27, 2003 10:47 PM
Subject: Re: [LARTC] Performanace fo the Iptables Server
> On Wednesday 27 August 2003 19:03, hare ram wrote:
> > Hi Stef
> >
> > thanks for the reply
> >
> > yes i would like to do accounting the source IP
> > so i need to log them all the traffic,
> > so i will know each IP how much transfering DATA
> >
> > with my configuration, is there any performance issue
> > i may have more than thousands of passing through this firewall or qos
> > server
> >
> > so my PC will have any performance issue or,
> > this configuration need any modification
> You don't have to log each packet to do accounting. If you create 1
iptables
> rule for each src address, you know how many packets and bytes that that
src
> address transmitted.
>
> iptables -A INPUT -s 192.168.1.0
> iptables -A INPUT -s 192.168.1.1
> iptables -A INPUT -s 192.168.1.2
>
> iptables -L -v -n
> Chain INPUT (policy DROP 47 packets, 5842 bytes)
> pkts bytes target prot opt in out source destination
> 0 0 all -- * * 192.168.1.0
0.0.0.0/0
> 0 0 all -- * * 192.168.1.1
0.0.0.0/0
> 0 0 all -- * * 192.168.1.2
0.0.0.0/0
>
> Stef
>
> --
>
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.oftc.net
>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-09-02 10:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 5:58 [LARTC] Performanace fo the Iptables Server hare ram
2003-08-27 15:30 ` Stef Coene
2003-08-27 17:15 ` hare ram
2003-08-27 17:17 ` Stef Coene
2003-08-27 17:41 ` Stef Coene
2003-08-27 17:43 ` hare ram
2003-08-27 17:51 ` hare ram
2003-08-27 17:57 ` Eric Leblond
2003-08-27 18:09 ` Stef Coene
2003-08-28 3:37 ` Raj Mathur
2003-09-02 10:20 ` hare ram [this message]
[not found] <019f01c36c5e$9f7868e0$c2bf09ca@Housecall>
2003-08-27 15:30 ` Stef Coene
[not found] ` <200308271730.07228.stef.coene@docum.org>
2003-08-27 17:03 ` hare ram
[not found] ` <011601c36cbd$185a5da0$c2bf09ca@Housecall>
2003-08-27 17:17 ` Stef Coene
[not found] ` <200308271917.00121.stef.coene@docum.org>
2003-08-27 17:31 ` hare ram
[not found] ` <015d01c36cc1$11fbabe0$c2bf09ca@Housecall>
2003-08-27 17:41 ` Stef Coene
[not found] ` <200308271941.53445.stef.coene@docum.org>
2003-08-27 17:50 ` hare ram
[not found] ` <026101c36cc3$b6b76280$c2bf09ca@Housecall>
2003-08-27 18:09 ` Stef Coene
2003-08-28 3:25 ` Raj Mathur
2003-09-02 10:08 ` hare ram
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=marc-lartc-106249738828279@msgid-missing \
--to=hareram@sol.net.in \
--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.