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 configuration data + apply-groups-except Don't inherit configuration data from these groups egress-shaping-overhead Number of CoS shaping overhead bytes in egress (0..255 bytes) ingress-shaping-overhead Number of CoS shaping overhead bytes in ingress (0..255 bytes) mode Configure traffic manager mode On Fri, Feb 13, 2009 at 7:41 PM, Stefan Fouant <[email protected]> wrote: > On Fri, Feb 13, 2009 at 9:39 PM, Marlon Duksa <[email protected]> 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 an incoming PIC the Layer 2 header > information is stripped by the I/O manager prior to creation of the > notification cell which is sent to the IPII Processor. The IPII > Processor handles the forwarding-table lookup, firewalling and > policing features, amongst other things. As the L2 header information > is not present in the notification cell, the IPII processor has no > awareness of the L2 information - therefore policing on things such as > L2 packet length is not possible. > > Somebody may correct me if I am wrong but this is my understanding... > > -- > Stefan Fouant > > Yesterday it worked. > Today it is not working. > Windows is like that. > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
