>> ip hst 192.168.11.4 or ip hst 192.168.11.5 or ip hst 192.168.11.1
"hst" should be "host"
I cann't swear there are no more problems, I avoid capture filters, but try
that until someone else gets back to you.
--
Richard Urwin, Software Design Engineer
Schenck Test Automation
Braemar Court, 1311b Melton Road, Syston, UK.
rurwin@xxxxxxxxxxxxx
-----Original Message-----
From: Hector Villafuerte [mailto:hec.villafuerte@xxxxxxxxxxxxx]
Sent: Monday, June 03, 2002 5:47 AM
To: ethereal-users@xxxxxxxxxxxx
Subject: [Ethereal-users] Re: VoIP Sniffing
Hi!
Since I like to do my homework (sort of research),
I looked at the tcpdump man page in order to figure
out how to filter what Andreas said:
> Filter out all traffic NOT going to/from the endpoints (and servers like
> gatekeepers) using a capture filter.
> ip hst 192.168.11.4 or ip hst 192.168.11.5 or ip hst 192.168.11.1
> Or something like that, creating capture filters is not my hobby ;-)
> A couple of more suggestions:
> - Filter out all non tcp or udp traffic
> - filter out all non ethernet traffic
But I couldn't get it right... would you be so kind to enlighten me?
As always, thanks in advance,
Hector
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
_____________________________________________________________________
This message has been checked for all known viruses by UUNET delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.uk.uu.net/products/security/virus/
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
