OID repository
OID Repository
https://oid-base.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemprivate(4) Action itementerprise(1) Action item11 Action itemnm(2) Action itemicf(14) Action itemicfBridge(3) Action itemwildcardTable(5)   Navigating the OID tree
wildcardUserOffset(5)
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

wildcardUserOffset OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS obsolete
DESCRIPTION
"This value is a byte offset from the beginning
of the packet. If this offset is such that any
portion of the filter extends past the end of the
packet (for wildcard filtering purposes, the FCS
is part of the packet), then the filter is
considered not to match, and the packet is not
filtered.
For a particular filter, the wildcardUserOffset
must be greater than or equal to the
wildcardOffset.
wildcardUserOffset must be between 0 and 1514,
inclusive.
The wildcardUserOffset, wildcardOffset pair must
conform to one of the following four relationships
and also be subject to the range restrictions
listed above. For n = 0,..,378
Offset 4n 4n 4n 4n+2
UserOffset 4n 4n+1 4n+2 4n+3
As an example, consider four examples in the
following table for locating the filter at or near
the beginning of a packet:
- 6 filter/mask bytes - - desired -
0 1 2 3 4 5 6 - position -
A|f/m0 f/m1 f/m2 f/m3 00 00 00 |0,4,8,12,...
B| 00 f/m0 f/m1 f/m2 f/m3 00 00 |1,5,9,13,...
C| 00 00 f/m0 f/m1 f/m2 f/m3 00 |2,6,10,14,...
D| 00 00 00 f/m0 f/m1 f/m2 f/m3|3,7,11,15,...
Example A corresponds to a UserOffset/Offset pair
such as 0/0 (4n/4n). Example B represents a pair
such as 0/1 (4n/4n+1). Example C is 0/2
(4n/4n+2). Finally, example D is 2/3 (4n+2/4n+3).
If any of the above constraints is not honored,
the SET Response will indicate genErr."


 
Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024
Parent OID: wildcardTable(5) First sibling OID: wildcardIndex(1) Previous sibling OID: wildcardOffset(4) Next sibling OID: wildcardArm(6) Last sibling OID: wildcardArm(6)
Separation line
OID helper Webmaster Bullet 18 Dec 2017 Bullet Page top