No subsequent term will be considered if a packet matches a term condition. Thats the problem here.
Combining both may not work here I would think. ________________________________ From: Alexander Arseniev <[email protected]> Sent: Thursday, April 23, 2015 9:56 AM To: Vijesh Chandran; [email protected] Subject: Re: [j-nsp] solution to a firewall question Hello, "next term" does not work across member filters in a filter list last time I checked. So You have to combine/move these 2 functionalities into a single filter, which could be a member of filter-list. Thanks Alex On 23/04/2015 16:18, Vijesh Chandran wrote: Hi all, I am wondering if we have a solution to this issue. I need two firewall attached to an interface as input-list. e.g.: f1 and f2. Input-list [f1 f2] f1 to match a condition (all tcp port 80) and accept and count that packet. f2 to classify those packets based on code points and push to a forwarding class. Is this possible? -Thanks, Vijesh _______________________________________________ juniper-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
