You could also use a firewall filter to syslog traffic and accept everything. Apply this to the interface you want to watch and you'll catch source/dest and tcp port crossing the int.
On 9/5/07, Gunjan GANDHI (BR/EPA) <[EMAIL PROTECTED]> wrote: > > Simple answer, you cannot, unless you sniff on a device connected to the > router (like a switch) > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of M.Mihailidis > Sent: Wednesday, 5 September 2007 8:26 PM > To: Rafal Szarecki > Cc: [email protected] > Subject: Re: [j-nsp] monitor > > and how can i see traffic transit the router??? > ----- Original Message ----- > From: Rafał Szarecki > To: M.Mihailidis > Cc: [email protected] > Sent: Wednesday, September 05, 2007 1:22 PM > Subject: Re: [j-nsp] monitor > > > This command monitor only traffic originated or terminated on local > routing engine. You do not see packet which transit through the router > (received on one interface and send via other) > > > 2007/9/5, M.Mihailidis <[EMAIL PROTECTED]>: > hello guys i want to monitor a interface to see what source address it > is using when i try to ping a certain address > i used "monitor traffic interface ge-0/0/1 extensive" > and all i got was the rip routing updates as output. > any suggestions? > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > -- > Rafał Szarecki JNCIE-M/T, JNCIP-E > +48602418971 > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
