Re: [j-nsp] How many bits/bytes of a packet can be matched in a firewall rule on Juniper MX-series?

On Fri, 9 Jul 2021 at 13:24, embolist wrote: > So, I can match a bit pattern within the first 256 bytes from the start of > the IP header, is that correct? > How many bits can I match within that first 256 bytes? You can set the match-start from L3, L4 or payload and take 256 bytes offset

Re: [j-nsp] How many bits/bytes of a packet can be matched in a firewall rule on Juniper MX-series?

--- Begin Message --- Sent from ProtonMail for iOS On Fri, Jul 9, 2021 at 12:30, Saku Ytti wrote: > But seeing you included a question about filter chaining, I'm not sure > I understood your question right. I'm the one who's not understanding right, haha! So, I can match a bit pattern within

Re: [j-nsp] How many bits/bytes of a packet can be matched in a firewall rule on Juniper MX-series?

Hey, I'm not sure I can parse what you are asking. I thought you're asking how far in the packet you can match with flexible-match-mask, which I can commit up-to 255 byte offset, but didn't test. I know the original Trio gets about 320B of the packet in the LU, but newer Trio's get a little bit

[j-nsp] How many bits/bytes of a packet can be matched in a firewall rule on Juniper MX-series?

--- Begin Message --- I'm trying to figure out how many bits/bytes of a packet I can match on in a firewall rule for a Juniper MX router. A lot of the documentation talks about a 128-bit match criteria, but then I see some examples which seem to imply that I can do multi-term matching, chaining