This is a summary of information regarding objects below the ucdIpFwAccMIB MIB object, which is defined within the UCD-IPFWACC-MIB MIB document as .1.3.6.1.4.1.2021.13.1.
Name | Type | Access | OID | Description |
---|
Name | Type | Access | Description |
---|---|---|---|
1
ipFwAccIndex |
INTEGER32
Legal values: 0 .. 2147483647 | ReadOnly |
Reference index for each firewall rule. |
Name | Type | Access | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2
ipFwAccSrcAddr | IPADDR | ReadOnly |
The source address in the firewall rule. |
||||||||||||
3
ipFwAccSrcNetMask | IPADDR | ReadOnly |
The netmask of the source address in the firewall rule. |
||||||||||||
4
ipFwAccDstAddr | IPADDR | ReadOnly |
The destination address in the firewall rule. |
||||||||||||
5
ipFwAccDstNetMask | IPADDR | ReadOnly |
The netmask of the destination address in the firewall rule. |
||||||||||||
6
ipFwAccViaName |
OCTETSTR
Legal Lengths: 1 .. 64 DisplayString | ReadOnly |
Note: this object is based on the DisplayString TEXTUAL-CONVENTION. The name of the interface to which the rule applies. If no interface is associated with the present rule, this should contain a dash (-). |
||||||||||||
7
ipFwAccViaAddr | IPADDR | ReadOnly |
The address of the interface to which the rule applies. Using this parameter makes sense when multiple addresses are associated to the same physical interface. If not defined for the current rule this should be set to 0. |
||||||||||||
8
ipFwAccProto |
INTEGER
| ReadOnly |
The protocol(s) to which the rule applies. |
||||||||||||
9
ipFwAccBidir |
INTEGER
| ReadOnly |
Whether the rule works in both directions (i.e. with the source and destination parts swapped) or not. |
||||||||||||
10
ipFwAccDir |
INTEGER
| ReadOnly |
Whether the rule applies to packets entering or exiting the kernel. |
||||||||||||
11
ipFwAccBytes | COUNTER | ReadOnly |
The number of bytes that matched this rule since the last reset of the counters. |
||||||||||||
12
ipFwAccPackets | COUNTER | ReadOnly |
The number of packets that matched this rule since the last reset of the counters. |
||||||||||||
13
ipFwAccNrSrcPorts | INTEGER32 | ReadOnly |
The number of ports that refer to the source address. |
||||||||||||
14
ipFwAccNrDstPorts | INTEGER32 | ReadOnly |
The number of ports that refer to the destination address. |
||||||||||||
15
ipFwAccSrcIsRange |
INTEGER
| ReadOnly |
Interpret the first two ports of the source part as the upper and lower limit of an interval or not. |
||||||||||||
16
ipFwAccDstIsRange |
INTEGER
| ReadOnly |
Interpret the first two ports of the destination part as the upper and lower limit of an interval or not. |
||||||||||||
17
ipFwAccPort1 | INTEGER32 | ReadOnly |
Port number 1. |
||||||||||||
18
ipFwAccPort2 | INTEGER32 | ReadOnly |
Port number 2. |
||||||||||||
19
ipFwAccPort3 | INTEGER32 | ReadOnly |
Port number 3. |
||||||||||||
20
ipFwAccPort4 | INTEGER32 | ReadOnly |
Port number 4. |
||||||||||||
21
ipFwAccPort5 | INTEGER32 | ReadOnly |
Port number 5. |
||||||||||||
22
ipFwAccPort6 | INTEGER32 | ReadOnly |
Port number 6. |
||||||||||||
23
ipFwAccPort7 | INTEGER32 | ReadOnly |
Port number 7. |
||||||||||||
24
ipFwAccPort8 | INTEGER32 | ReadOnly |
Port number 8. |
||||||||||||
25
ipFwAccPort9 | INTEGER32 | ReadOnly |
Port number 9. |
||||||||||||
26
ipFwAccPort10 | INTEGER32 | ReadOnly |
Port number 10. |
SCALAR OBJECTS
TABLE OBJECTS |
These TEXTUAL-CONVENTIONS are used in other parts of the document above. They are SNMP's way of defining a datatype that is used repeatedly by other MIB objects. Any implementation implementing objects that use one of these definitions must follow its DESCRIPTION clause as well as the DESCRIPTION clause of the object itself.
Name | Type | Description |
---|---|---|
DisplayString | OCTETSTR | Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. |
Tree view generated by running: snmptranslate -Tp UCD-IPFWACC-MIB::ucdIpFwAccMIB
+--ucdIpFwAccMIB(1) | +--ipFwAccTable(1) | +--ipFwAccEntry(1) | Index: ipFwAccIndex | +-- -R-- Integer32 ipFwAccIndex(1) | Range: 0..2147483647 +-- -R-- IpAddr ipFwAccSrcAddr(2) +-- -R-- IpAddr ipFwAccSrcNetMask(3) +-- -R-- IpAddr ipFwAccDstAddr(4) +-- -R-- IpAddr ipFwAccDstNetMask(5) +-- -R-- String ipFwAccViaName(6) | Textual Convention: DisplayString | Size: 1..64 +-- -R-- IpAddr ipFwAccViaAddr(7) +-- -R-- EnumVal ipFwAccProto(8) | Values: other(1), all(2), tcp(3), udp(4), icmp(5) +-- -R-- EnumVal ipFwAccBidir(9) | Values: unidirectional(1), bidirectional(2) +-- -R-- EnumVal ipFwAccDir(10) | Values: both(1), in(2), out(3) +-- -R-- Counter ipFwAccBytes(11) +-- -R-- Counter ipFwAccPackets(12) +-- -R-- Integer32 ipFwAccNrSrcPorts(13) +-- -R-- Integer32 ipFwAccNrDstPorts(14) +-- -R-- EnumVal ipFwAccSrcIsRange(15) | Values: srchasrange(1), srchasnorange(2) +-- -R-- EnumVal ipFwAccDstIsRange(16) | Values: dsthasrange(1), dsthasnorange(2) +-- -R-- Integer32 ipFwAccPort1(17) +-- -R-- Integer32 ipFwAccPort2(18) +-- -R-- Integer32 ipFwAccPort3(19) +-- -R-- Integer32 ipFwAccPort4(20) +-- -R-- Integer32 ipFwAccPort5(21) +-- -R-- Integer32 ipFwAccPort6(22) +-- -R-- Integer32 ipFwAccPort7(23) +-- -R-- Integer32 ipFwAccPort8(24) +-- -R-- Integer32 ipFwAccPort9(25) +-- -R-- Integer32 ipFwAccPort10(26)
Last modified: Wednesday, 01-Aug-2018 04:41:28 UTC
For questions regarding web content and site functionality, please write to the net-snmp-users mail list.