Thomas,
Create a rule for each possible source address, i.e.:
for i in 127.0.0.1 192.168.1.1 192.168.1.2 192.168.1.3; do
ipchains -A input -s $i
done
That will set up counters for traffic coming from 127.0.0.1, 192.168.1.1,
192.168.1.2, and 192.168.1.3, all with their own counters.
Thanks, Leen, Alexander and Tim for your answers.
I found the solution. I produced the traffic myself.
I did ipchains -v -L every second in a script to see what happens
on my network. I am interested in amount of traffic, at the moment.
But ipchains itselfs displays ip-adresses with names, not
Thomas,
Create a rule for each possible source address, i.e.:
for i in 127.0.0.1 192.168.1.1 192.168.1.2 192.168.1.3; do
ipchains -A input -s $i
done
That will set up counters for traffic coming from 127.0.0.1, 192.168.1.1,
192.168.1.2, and 192.168.1.3, all with their own counters.
I just made my first ipchains to see what kind
of traffic there is.
on accounting rule is:
ipchains -A output -d 193.101.57.0/24 -p udp -j ACCEPT
ipchains -L -v tells me that there is a lot of traffic.
(15M/day!)
But netstat -u tells me that there is no connection
Any help welcome.
--
On Thu, 13 Jul 2000, Thomas Guettler wrote:
I just made my first ipchains to see what kind
of traffic there is.
on accounting rule is:
ipchains -A output -d 193.101.57.0/24 -p udp -j ACCEPT
ipchains -L -v tells me that there is a lot of traffic.
(15M/day!)
But netstat -u tells me
On Thu, Jul 13, 2000 at 05:49:43PM +0200, L. Besselink wrote:
on accounting rule is:
ipchains -A output -d 193.101.57.0/24 -p udp -j ACCEPT
ipchains -L -v tells me that there is a lot of traffic.
(15M/day!)
That's not wholly surprising. It's not an accounting rule, though - how do you
Thomas,
Shave off the `-j ACCEPT' from the end of that ipchains rule! Read the man
page for more.
Regards,
Alex.
---
PGP/GPG Fingerprint:
EFD1 AC6C 7ED5 E453 C367 AC7A B474 16E0 758D 7ED9
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS/CMCC/IT d- s:+ a16 C++()$ UL$ P---() L
7 matches
Mail list logo
