On Mon, Feb 16, 2009 at 12:57 PM, Marlon Duksa wrote:
> The packet length is variable in my case, I have IMIX traffic coming in.
> Dealing with packet length filters is not practical when you need to
> include _all_ packet lengths...
If you omit the packet-length match condition, you will automa
The packet length is variable in my case, I have IMIX traffic coming in.
Dealing with packet length filters is not practical when you need to
include _all_ packet lengths...Thanks,
Marlon
On Fri, Feb 13, 2009 at 8:36 PM, Stefan Fouant wrote:
> On Fri, Feb 13, 2009 at 11:08 PM, Marlon Duksa wro
On Fri, Feb 13, 2009 at 11:08 PM, Marlon Duksa wrote:
> Thanks Stefan. But maybe there is a statement that says how many bytes to
> prepend to each packet when policing.
Why not just subtract the L2 overhead and set your firewall-filter to
match on packets of a particular IP packet length using t
Thanks Stefan. But maybe there is a statement that says how many bytes to
prepend to each packet when policing.Something like that exists for ingress
shaping already:
pop-10# set chassis fpc 10 pic 3 traffic-manager ?
Possible completions:
+ apply-groups Groups from which to inherit confi
On Fri, Feb 13, 2009 at 9:39 PM, Marlon Duksa wrote:
> Hi - anyone know if there is a way to set policing rates based on L2 packet
> length, as opposed L3 as it is default on Junos?Thanks,
I could be wrong but my assumption would be that this is not possible.
When a packet enters the router on a
Hi - anyone know if there is a way to set policing rates based on L2 packet
length, as opposed L3 as it is default on Junos?Thanks,
Marlon
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
6 matches
Mail list logo
