⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1158.txt

📁 <VC++网络游戏建摸与实现>源代码
💻 TXT
📖 第 1 页 / 共 5 页
字号:
          Definition:               The number of outbound packets which were chosen to be               discarded even though no errors had been detected to               prevent their being transmitted.  One possible reason for               discarding such a packet could be to free up buffer               space.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ifOutErrors { ifEntry 20 }          Syntax:               CounterIETF SNMP Working Group                                        [Page 25]RFC 1158                         MIB II                         May 1990          Definition:               The number of outbound packets that could not be               transmitted because of errors.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ifOutQLen { ifEntry 21 }          Syntax:               Gauge          Definition:               The length of the output packet queue (in packets).          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ifSpecific { ifEntry 22 }          Syntax:               OBJECT IDENTIFIER          Definition:               A reference to MIB definitions specific to the particular               media being used to realize the interface.  For example,               if the interface is realized by an ethernet, then the               value of this object refers to a document defining               objects specific to ethernet.  If an agent is not               configured to have a value for any of these variables,               the object identifier                    nullSpecific OBJECT IDENTIFIER ::= { 0 0 }               is returned.  Note that "nullSpecific" is a syntatically               valid object identifier, and any conformantIETF SNMP Working Group                                        [Page 26]RFC 1158                         MIB II                         May 1990               implementation of ASN.1 and BER must be able to generate               and recognize this value.          Access:               read-only.          Status:               mandatory.5.3.  The Address Translation Group   Implementation of the Address Translation group is mandatory for all   systems.  Note however that this group is deprecated by MIB-II.  That   is, it is being included solely for compatibility with MIB-I nodes,   and will most likely be excluded from MIB-III nodes.  From MIB-II and   onwards, each network protocol group contains its own address   translation tables.   The Address Translation group contains one table which is the union   across all interfaces of the translation tables for converting a   NetworkAddress (e.g., an IP address) into a subnetwork-specific   address.  For lack of a better term, this document refers to such a   subnetwork-specific address as a "physical" address.   Examples of such translation tables are: for broadcast media where   ARP is in use, the translation table is equivalent to the ARP cache;   or, on an X.25 network where non-algorithmic translation to X.121   addresses is required, the translation table contains the   NetworkAddress to X.121 address equivalences.          OBJECT:          -------               atTable { at 1 }          Syntax:               SEQUENCE OF AtEntry          Definition:               The Address Translation tables contain the NetworkAddress               to "physical" address equivalences.  Some interfaces do               not use translation tables for determining address               equivalences (e.g., DDN-X.25 has an algorithmic method);               if all interfaces are of this type, then the Address               Translation table is empty, i.e., has zero entries.          Access:               read-write.IETF SNMP Working Group                                        [Page 27]RFC 1158                         MIB II                         May 1990          Status:               deprecated.          OBJECT:          -------               atEntry { atTable 1 }          Syntax:               AtEntry ::= SEQUENCE {                    atIfIndex                        INTEGER,                    atPhysAddress                        OCTET STRING,                    atNetAddress                        NetworkAddress               }          Definition:               Each entry contains one NetworkAddress to "physical"               address equivalence.          Access:               read-write.          Status:               deprecated.          We now consider the individual components of each Address          Translation table entry:          OBJECT:          -------               atIfIndex { atEntry 1 }          Syntax:               INTEGER          Definition:               The interface on which this entry's equivalence is               effective.  The interface identified by a particular               value of this index is the same interface as identified               by the same value of ifIndex.          Access:               read-write.IETF SNMP Working Group                                        [Page 28]RFC 1158                         MIB II                         May 1990          Status:               deprecated.          OBJECT:          -------               atPhysAddress { atEntry 2 }          Syntax:               OCTET STRING          Definition:               The media-dependent "physical" address.          Setting this object to a null string (one of zero length) has          the effect of invaliding the corresponding entry in the          atTable object.  That is, it effectively disassociates the          interface identified with said entry from the mapping          identified with said entry.  It is an implementation-specific          matter as to whether the agent removes an invalidated entry          from the table.  Accordingly, management stations must be          prepared to receive tabular information from agents that          corresponds to entries not currently in use.  Proper          interpretation of such entries requires examination of the          relevant atPhysAddress object.          Access:               read-write.          Status:               deprecated.          OBJECT:          -------               atNetAddress { atEntry 3 }          Syntax:               NetworkAddress          Definition:               The NetworkAddress (e.g., the IP address) corresponding               to the media-dependent "physical" address.          Access:               read-write.IETF SNMP Working Group                                        [Page 29]RFC 1158                         MIB II                         May 1990          Status:               deprecated.5.4.  The IP Group   Implementation of the IP group is mandatory for all systems.          OBJECT:          -------               ipForwarding { ip 1 }          Syntax:               INTEGER {                    forwarding(1),    -- i.e., acting as a gateway                    not-forwarding(2) -- i.e., NOT acting as a gateway               }          Definition:               The indication of whether this entity is acting as an IP               gateway in respect to the forwarding of datagrams               received by, but not addressed to, this entity.  IP               gateways forward datagrams.  IP hosts do not (except               those source-routed via the host).          Access:               read-write.          Status:               mandatory.          OBJECT:          -------               ipDefaultTTL { ip 2 }          Syntax:               INTEGER          Definition:               The default value inserted into the Time-To-Live field of               the IP header of datagrams originated at this entity,               whenever a TTL value is not supplied by the transport               layer protocol.          Access:               read-write.IETF SNMP Working Group                                        [Page 30]RFC 1158                         MIB II                         May 1990          Status:               mandatory.          OBJECT:          -------               ipInReceives { ip 3 }          Syntax:               Counter          Definition:               The total number of input datagrams received from               interfaces, including those received in error.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipInHdrErrors { ip 4 }          Syntax:               Counter          Definition:               The number of input datagrams discarded due to errors in               their IP headers, including bad checksums, version number               mismatch, other format errors, time-to-live exceeded,               errors discovered in processing their IP options, etc.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipInAddrErrors { ip 5 }          Syntax:               CounterIETF SNMP Working Group                                        [Page 31]RFC 1158                         MIB II                         May 1990          Definition:               The number of input datagrams discarded because the IP               address in their IP header's destination field was not a               valid address to be received at this entity.  This count               includes invalid addresses (e.g., 0.0.0.0) and addresses               of unsupported Classes (e.g., Class E).  For entities               which are not IP Gateways and therefore do not forward               datagrams, this counter includes datagrams discarded               because the destination address was not a local address.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipForwDatagrams { ip 6 }          Syntax:               Counter          Definition:               The number of input datagrams for which this entity was               not their final IP destination, as a result of which an               attempt was made to find a route to forward them to that               final destination.  In entities which do not act as IP               Gateways, this counter will include only those packets               which were Source-Routed via this entity, and the               Source-Route option processing was successful.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipInUnknownProtos { ip 7 }          Syntax:               CounterIETF SNMP Working Group                                        [Page 32]RFC 1158                         MIB II                         May 1990          Definition:               The number of locally-addressed datagrams received               successfully but discarded because of an unknown or               unsupported protocol.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipInDiscards { ip 8 }          Syntax:               Counter          Definition:               The number of input IP datagrams for which no problems               were encountered to prevent their continued processing,               but which were discarded (e.g., for lack of buffer               space).  Note that this counter does not include any               datagrams discarded while awaiting re-assembly.          Access:               read-only.          Status:               mandatory.          OBJECT:          -------               ipInDelivers { ip 9 }          Syntax:

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -