Thanks Andrew, yes that was a typo. It's monitor session 1 destination interface f1/0/2 encapsulation ingress dot1q vlan 23
With regards Kings On Mon, Apr 18, 2011 at 10:30 PM, Andrew Wurster <[email protected] > wrote: > kings - > > regarding point #2 - not sure if it's a typo but your monitor session is > configured for ingress from vlan 123, where the IPS is tagging with vlan 23. > > andrew > > On Mon, Apr 18, 2011 at 8:43 AM, Kingsley Charles < > [email protected]> wrote: > >> Hi all >> >> I tried tcp reset with following two cases which is failing: >> >> 1) An alternate interface is configured for tcp reset. The switch port >> connected to the alternate interface was put in the same vlan in which the >> attacker and victim is present. But the tcp reset never reached them. >> >> 2) The promiscuous interface is being configured for vlan groups and I >> have configured ingress option as following to tag with vlan 23 to carry the >> tcp reset. The attacker and victim is in vlan 23. But the tcp reset never >> reached them. >> >> monitor session 1 destination interface f1/0/2 encapsulation ingress dot1q >> vlan 123 >> >> >> Any idea why both are not working? >> >> With regards >> Kings >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> Are you a CCNP or CCIE and Looking for a Job – check out >> www.PlatinumPlacement.co >> > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and Looking for a Job check out www.PlatinumPlacement.co
