Re: [j-nsp] SRX Screen not working

Thanks for the info. The attack we recently saw was using IP protocol 3 (GGP) which is not specifically permitted so I'm unsure how it was allowed to create a session in the first place. Does the session limit screening only apply to TCP/UDP? Also what is the definition of an invalidated sessio

Re: [j-nsp] srx cluster - control and data link throuigh cisco nexus switches

Le 30/05/2013 07:28, Andrew Jones a écrit : There is a hidden command you can use which is "show chassis cluster information detail" which will give you a lot more information about how the cluster is set up on each node and if there are any errors in regards to the control link and fabric link.

Re: [j-nsp] srx cluster - control and data link throuigh cisco

Le 30/05/2013 07:25, Farrukh Haroon a écrit : Also if the link is passing through high-end Cisco switches you might have to disable IP header checks, as mentioned in this KB article: http://kb.juniper.net/InfoCenter/index?page=content&id=KB15141 I couldn't find anything related to ip header che

Re: [j-nsp] [OT] unit-level vs interface-level description

Jared Mauch writes: >This will break many systems that I know of. Please don't do this :-) Cool. Consider it not done. Thanks, Phil ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] SRX Screen not working

30.05.2013 04:41, Luca Salvatore wrote: > However, we recently had an attack on one of our customers where there was > around 400,000 sessions to a single IP address, as shown: > > show security flow session summary destination-prefix 202.x.x.x > node1: > -