From: Jeremy (jeremy19@xxxxxxxx)
Date: Sat Sep 15 2001 - 14:52:54 GMT-3
Don't forget that if you use log on your ACL's, you may only get source and
destination IP, so specify range 1-65535 on source and destination ports in
order to log the source and destination ports as well. Hope this helps.
-Jeremy
----- Original Message -----
From: "Ron Royston" <ccie6824@hotmail.com>
To: <tim_wu@gz.ctil.com>; <ccielab@groupstudy.com>
Cc: <Justin.Menga@compaq.com>
Sent: Monday, September 10, 2001 9:21 PM
Subject: Re: about traceroute packets of cisco router
> Cisco divices use more than that for trace. There's been a few threads on
> this one before. You can use the log keyword on an access list and
perhaps
> a syslog server on your laptop, or telnet/term mon to see what going on.
>
>
> >From: tim wu <tim_wu@gz.ctil.com>
> >Reply-To: tim wu <tim_wu@gz.ctil.com>
> >To: ccielab <ccielab@groupstudy.com>
> >CC: "Justin.Menga@compaq.com" <Justin.Menga@compaq.com>
> >Subject: about traceroute packets of cisco router
> >Date: Tue, 11 Sep 2001 11:34:14 +0800
> >
> >Hi,Members
> >
> > I found cisco use tcp 33434 to trace a route,I want to know its
> >mechanism.Could you show me? thanks.
> >
> > I think the following tools can tell me the trueness,but I haven't.
> >
> >
> > BJ---------------------SJ-------------------NY
> > e0 | | e0 loop0
> > | |
> > | |
> > sniffer capture _______|
> >
> >
> >BJ trace a route of NY loop0,decode the packets.
> >**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:18 GMT-3