Hello, once again! One more simple question for any gurus willing to
help. Just looking for a bit of direction. Are there any tools besides
iptables for direct bandwidth monitoring? For instance, ssh'ing to my
machine, running a command, and getting something similar to htop which
will give me a view of what port or service or protocol is sending or
receiving? I'm comfortable with learning anything, though I was looking
for something a bit straightforward. Any suggestions (including one to
write a script or something) is welcome!

Thanks for your time either way.

[ Post a follow-up to this message ]

* Signals wrote in alt.os.linux.debian:
> Hello, once again! One more simple question for any gurus willing to
> help. Just looking for a bit of direction. Are there any tools besides
> iptables for direct bandwidth monitoring? For instance, ssh'ing to my
> machine, running a command, and getting something similar to htop which
> will give me a view of what port or service or protocol is sending or
> receiving? I'm comfortable with learning anything, though I was looking
> for something a bit straightforward. Any suggestions (including one to
> write a script or something) is welcome!

> Thanks for your time either way.

Something like:

$ sudo netstat -n -tcp | grep ".ESTABLISHED."

--
David
For the next hour, WE will control all that you see and hear.

[ Post a follow-up to this message ]

SINNER wrote:
> * Signals wrote in alt.os.linux.debian: 
> 
>
> Something like:
>
> $ sudo netstat -n -tcp | grep ".ESTABLISHED."
>
Thanks! This seems to be a good realtime monitoring tool. I should then
be able to filter out stuff manually with iptables, perhaps?

I feel kinda dumb for missing out on this command..

[ Post a follow-up to this message ]

* Signals wrote in alt.os.linux.debian:
> SINNER wrote: 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen]
> Thanks! This seems to be a good realtime monitoring tool. I should then
> be able to filter out stuff manually with iptables, perhaps?

> I feel kinda dumb for missing out on this command..

Why? I just learned it the other day from someone else that was using it
for something similar.

You just happen to ask while it was in short term memory 

--
David
Lost: gray and white female cat.  Answers to electric can opener.

[ Post a follow-up to this message ]

SINNER wrote:
> * Signals wrote in alt.os.linux.debian: 
> 
> 
> 
> 
> 
>
> Why? I just learned it the other day from someone else that was using it
> for something similar.
>
> You just happen to ask while it was in short term memory 
>
Well then thanks even more for coincidentally remembering  I'll be
sure to pass it on to anyone else who needs it too.

[ Post a follow-up to this message ]

Signals wisely stated:

> Hello, once again! One more simple question for any gurus willing to
> help. Just looking for a bit of direction. Are there any tools besides
> iptables for direct bandwidth monitoring? For instance, ssh'ing to my
> machine, running a command, and getting something similar to htop which
> will give me a view of what port or service or protocol is sending or
> receiving? I'm comfortable with learning anything, though I was looking
> for something a bit straightforward. Any suggestions (including one to
> write a script or something) is welcome!
>
> Thanks for your time either way.

Hi, there are several very useful tools to choose from. Some are comersial,
some of them expensive (Cisco?).
An alternative could be Argus. It will give you what you are loking for,
even in graphs.
http://www.qosient.com/argus/
There is a very good article on setting up and using Argus in Linux Magazine
(february 2007 /issue 75) (www.linux-magazine.com)

Hans Poppe
Oslo, Norway
--
"As we enjoy great advantages from the inventions of others, we should be
glad of an opportunity to serve others with any invention of ours, and this
we should do freely and generously."
-- Benjamin Franklin

[ Post a follow-up to this message ]