Ethereal-users: RE: [Ethereal-users] Filters
Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.
From: "Visser, Martin (SNO)" <Martin.Visser@xxxxxxxxxx>
Date: Fri, 22 Jun 2001 14:17:25 +0800
1.
Firstly I would probably make use of the ip accounting in the Cisco. You need to
config on the serial interface and add " ip accounting output-packets
". After a minute then do "show ip accounting". You'll get something like :-
Source
Destination
Packets
Bytes
10.138.2.2 10.128.9.2 865846 76277502 10.138.2.2 10.136.5.2 907612 78689819 10.138.2.2 10.128.9.4 1904894 126219478 10.138.2.2 10.132.2.2 439578 38682864 10.138.2.2 10.176.71.3 10629 694619 10.138.2.2 10.176.71.2 859281 75611829 10.138.2.2 10.128.2.150 691 120774 10.138.3.2 10.128.2.150 3423 206338 10.138.2.2 127.0.0.1 906 26274 Accounting data age is 3d03h
2. If
you are on the ethernet going into the router you can't actually know if traffic
is going to the Internet. However you can certainly make a good
guess.
As a
capture filter you can use the MAC address of the router e.g. "ether dst
01:02:34:56:78:90". This will only capture traffic to the router. If the router
also does local routing you may also need to added display filtering to remove
local destination addresses. Once you have isolated the traffic type though you
can probably just analyse a small sample of data to determine the
culprits
Martin Visser
Network Consultant - Compaq Global Services Compaq Computer Australia Phone: +61-2-9022-5630
|
- Follow-Ups:
- Re: [Ethereal-users] Filters
- From: Serge Dergham
- Re: [Ethereal-users] Filters
- Prev by Date: Re: [Ethereal-users] Bug in 802.11 dissector
- Next by Date: [Ethereal-users] (no subject)
- Previous by thread: [Ethereal-users] Filters
- Next by thread: Re: [Ethereal-users] Filters
- Index(es):