o BŠ]o_ã@sÚddlmZmZddlmZddlmZddlZejZe edƒr,e edƒr,ej Z ej Z n*ddl Z e j dkrHddlmZmZd d „Z d d „Z d ZnerVddlZd d„Z dd„Z e dddd¡\ZZZe dd¡\Ze dddddd¡\ZZZZZe ddd¡\ZZe ddd d!d"d#d$d%d&d'd(d)d*d+d,d-d.d/d0¡\ZZZ Z!Z"Z#Z$Z%Z&Z'Z(Z)Z*Z+Z,Z-Z.Z/e d1d2d3¡\Z0Z1e"d4ƒZ2ej3r¾e2 4d5¡ej3rÆe2 5d6¡ej3rÎe2 6d7¡ej3rÖe2 7d8¡ej3rÞe2 8d9¡e d:ƒZ9e*d;ƒZ:ej3rîe: ;d<¡ej3röe: 8d=¡e*d>ƒZej3r/e> ;d<¡ej3r8e> 8dC¡e*dDƒZ?ej3rEe? ;d<¡ej3rNe? 8dE¡e*dFƒZ@ej3r[e@ ;d<¡ej3rde@ 8dG¡e*dHƒZAej3rqeA ;d<¡ej3rzeA 8dI¡e*dJƒZBej3r‡eB ;d<¡ej3reB 8dK¡e*dLƒZCej3reC ;d<¡ej3r¦eC 8dM¡e*dNƒZDej3r³eD ;d<¡ej3r¼eD 8dO¡e*dPƒZEej3rÉeE ;d<¡ej3rÒeE 8dQ¡e*dRƒZFej3rßeF ;d<¡ej3rèeF 8dS¡e*dTƒZGej3rõeG ;d<¡ej3rþeG 8dU¡e*dVƒZHej3r eH ;d<¡ej3reH 8dW¡e*dXƒZIej3r!eI ;d<¡ej3r*eI 8dY¡e*dZƒZJej3r7eJ ;d<¡ej3r@eJ 8d[¡Gd\d]„d]e1eƒZKGd^d_„d_e1eƒZLGd`da„dae1eƒZMGdbdc„dce1eƒZNGddde„dee1eƒZOGdfdg„dge1eƒZPGdhdi„die1eƒZQGdjdk„dke1eƒZRGdldm„dme1eƒZSejTd‚idoe<“d]eK“dpeJ“dqe2“d_eL“dre?“dieQ“dseG“dkeR“dte:“due=“dve9“dweC“deeO“dmeS“dxeF“dye2“dzeB“d{eD“d|eH“d}e@“d~e>“dceN“deE“d€eA“daeM“deI“dgeP“ŽdS)ƒé)Úint2octÚoct2int)Úerror)ÚsockfixNÚ inet_ntopÚ inet_ptonÚwin32)Ú inet_ntoaÚ inet_atoncCót|ƒS©N)r ©ÚxÚy©rúG/usr/lib/python3/dist-packages/pysnmp/smi/mibs/TRANSPORT-ADDRESS-MIB.pyÚórcCr r )r r rrrrrFcCsŒ|tjkr t |¡S|tjkrt d|f¡‚| d¡}| d¡}d|dvr;dd„t dt |d¡¡Dƒ|dd…<|d krV|  d¡}d gd t |ƒd |||d …<nM|d kr…d gd t |ƒd }|  d ¡rq||dd …<n2|  d ¡r}||dd…<n&t d|f¡‚|dkr—|d kr•t d|f¡‚dS|dkr£t d|f¡‚dd„dd„|DƒDƒ}t |ƒd kr½t d|f¡‚tj dg|¢RŽS)NúUnknown address family %sú:ÚÚ.éÿÿÿÿcSsg|]}d|‘qS)ú%xr©Ú.0rrrrÚ 1ózinet_pton..z!HHéÚ0ééz::éþÿÿÿzInvalid IPv6 address: "%s"ézcSsg|] }|d@|kr|‘qS)iÿÿr©rÚtrrrrKscSsg|]}t|dƒ‘qS)é)Úintr$rrrrKsú!8H)ÚsocketÚAF_INETr ÚAF_INET6rÚsplitÚcountÚstructÚunpackÚindexÚlenÚ startswithÚendswithZpack)Úaddress_familyZ ip_stringÚgroupsÚspacesÚidxZzerosrrrr%sL   ÿ   ( $  ÿÿÿ ÿcsX|tjkr t |¡S|tjkrt d|f¡‚t|ƒdkr&t dt|ƒ¡‚tt d|¡ƒ}d}}}}t dƒD](}||rT|dkrS|dksL||krQ||}}d}q:|dkr^|d}}q:|d7}q:|dkrt|dkso||krt||}}|dkr…|dkr…dg||||…<|d dkr‘|  d d¡|ddkrœ|  d¡d d „‰d  ‡fd d „|Dƒ¡S)Nrr&zincorrect address length: %sr(rr rrrcSs|dkrd|p dS)Nrrrr)rrrrr~rzinet_ntop..csg|]}ˆ|ƒ‘qSrrr©Úfrrr€rzinet_ntop..) r)r*rr+rr1Úlistr.r/ÚrangeÚinsertÚappendÚjoin)r4Z packed_ipr5Zcur_baseZ best_baseZcur_lenZbest_lenr7rr8rrUsB   ÿ  ÿ  €       ZASN1ÚIntegerÚ OctetStringÚObjectIdentifierzASN1-ENUMERATIONÚ NamedValueszASN1-REFINEMENTÚConstraintsIntersectionÚConstraintsUnionÚValueRangeConstraintÚValueSizeConstraintÚSingleValueConstraintz SNMPv2-CONFÚNotificationGroupÚModuleCompliancez SNMPv2-SMIÚ Integer32Ú Unsigned32Ú MibIdentifierÚ Counter32ÚModuleIdentityÚ MibScalarÚMibTableÚ MibTableRowÚMibTableColumnÚNotificationTypeÚBitsÚ TimeTicksÚObjectIdentityÚ Counter64ÚGauge32Ú IpAddressÚisozmib-2z SNMPv2-TCÚ DisplayStringÚTextualConvention)rr#érr!réd)z2002-11-01 00:00Z 200211010000Zz#IETF Operations and Management Areaz¸Juergen Schoenwaelder (Editor) TU Braunschweig Bueltenweg 74/75 38106 Braunschweig, Germany Phone: +49 531 391-3289 EMail: schoenw@ibr.cs.tu-bs.de Send comments to .zÐThis MIB module provides commonly used transport address definitions. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3419; see the RFC itself for full legal notices.)rr#r]rr!rr^r) rr#r]rr!rr^rrÚcurrentz‚The UDP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses.) rr#r]rr!rr^rr!z‚The UDP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses.) rr#r]rr!rr^rr#z•The UDP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index.) rr#r]rr!rr^réz•The UDP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index.) rr#r]rr!rr^réz‚The TCP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses.) rr#r]rr!rr^rr]z‚The TCP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses.) rr#r]rr!rr^réz•The TCP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index.) rr#r]rr!rr^rr z•The TCP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index.) rr#r]rr!rr^ré zÞThe SCTP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses. This transport domain usually represents the primary address on multihomed SCTP endpoints.) rr#r]rr!rr^ré zÞThe SCTP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses. This transport domain usually represents the primary address on multihomed SCTP endpoints.) rr#r]rr!rr^ré zñThe SCTP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index. This transport domain usually represents the primary address on multihomed SCTP endpoints.) rr#r]rr!rr^ré zñThe SCTP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index. This transport domain usually represents the primary address on multihomed SCTP endpoints.) rr#r]rr!rr^ré zÁThe Posix Local IPC transport domain. The corresponding transport address is of type TransportAddressLocal. The Posix Local IPC transport domain incorporates the well-known UNIX domain sockets.) rr#r]rr!rr^réz€The UDP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.) rr#r]rr!rr^réz€The TCP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.) rr#r]rr!rr^rr&zThe SCTP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.c@seZdZdZdZdS)ÚTransportDomainz¸A value that represents a transport domain. Some possible values, such as transportDomainUdpIpv4, are defined in this module. Other possible values can be defined in other MIB modules.r_N)Ú__name__Ú __module__Ú __qualname__Ú descriptionÚstatusrrrrrjÀsrjc@sneZdZdZdZejeeddddddd d d d d ddddddƒƒZe ddddddddddddd d!d"d#d$ƒZ d%S)&ÚTransportAddressTypea÷A value that represents a transport domain. This is the enumerated version of the transport domain registrations in this MIB module. The enumerated values have the following meaning: unknown(0) unknown transport address type udpIpv4(1) transportDomainUdpIpv4 udpIpv6(2) transportDomainUdpIpv6 udpIpv4z(3) transportDomainUdpIpv4z udpIpv6z(4) transportDomainUdpIpv6z tcpIpv4(5) transportDomainTcpIpv4 tcpIpv6(6) transportDomainTcpIpv6 tcpIpv4z(7) transportDomainTcpIpv4z tcpIpv6z(8) transportDomainTcpIpv6z sctpIpv4(9) transportDomainSctpIpv4 sctpIpv6(10) transportDomainSctpIpv6 sctpIpv4z(11) transportDomainSctpIpv4z sctpIpv6z(12) transportDomainSctpIpv6z local(13) transportDomainLocal udpDns(14) transportDomainUdpDns tcpDns(15) transportDomainTcpDns sctpDns(16) transportDomainSctpDns This textual convention can be used to represent transport domains in situations where a syntax of TransportDomain is unwieldy (for example, when used as an index). The usage of this textual convention implies that additional transport domains can only be supported by updating this MIB module. This extensibility restriction does not apply for the TransportDomain textual convention which allows MIB authors to define additional transport domains independently in other MIB modules.r_rrr!r#r`rar]rbr rcrdrerfrgrhrir&)Úunknownr)ZudpIpv4r)ZudpIpv6r!)ZudpIpv4zr#)ZudpIpv6zr`)ZtcpIpv4ra)ZtcpIpv6r])ZtcpIpv4zrb)ZtcpIpv6zr )ZsctpIpv4rc)ZsctpIpv6rd)Z sctpIpv4zre)Z sctpIpv6zrf)Zlocalrg)ZudpDnsrh)ZtcpDnsri)ZsctpDnsr&N) rkrlrmrnrorJÚ subtypeSpecrDrGrBZ namedValuesrrrrrpÄs 2,rpc@s$eZdZdZdZejeddƒZdS)ÚTransportAddressaÙDenotes a generic transport address. A TransportAddress value is always interpreted within the context of a TransportAddressType or TransportDomain value. Every usage of the TransportAddress textual convention MUST specify the TransportAddressType or TransportDomain object which provides the context. Furthermore, MIB authors SHOULD define a separate TransportAddressType or TransportDomain object for each TransportAddress object. It is suggested that the TransportAddressType or TransportDomain is logically registered before the object(s) which use the TransportAddress textual convention if they appear in the same logical row. The value of a TransportAddress object must always be consistent with the value of the associated TransportAddressType or TransportDomain object. Attempts to set a TransportAddress object to a value which is inconsistent with the associated TransportAddressType or TransportDomain must fail with an inconsistentValue error. When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers.r_réÿN)rkrlrmrnror@rrrFrrrrrsÊsrsc@óLeZdZdZdZdZejeddƒZdZ dd„Z dd„Z d d „Z d d „Z d S)ÚTransportAddressIPv4aÚRepresents a transport address consisting of an IPv4 address and a port number (as used for example by UDP, TCP and SCTP): octets contents encoding 1-4 IPv4 address network-byte order 5-6 port number network-byte order This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.r_z1d.1d.1d.1d:2dr]cCsJt|tƒrttj|dƒt|dd?d@ƒt|dd@ƒ}t ||¡S)Nrrr rt)Ú isinstanceÚtuplerr)r*rr@ÚprettyIn©ÚselfÚvaluerrrryÖs 4 zTransportAddressIPv4.prettyIncCsJt|dƒs"| ¡}ttj|dd…ƒt|dƒd>t|dƒBf|_|jS)NÚ __tuple_valuer`r ra)ÚhasattrÚasOctetsrr)r*rZ"_TransportAddressIPv4__tuple_value©r{ÚvrrrÚ__asSocketAddressÝs þz&TransportAddressIPv4.__asSocketAddresscCó t| ¡ƒSr )ÚiterÚ&_TransportAddressIPv4__asSocketAddress©r{rrrÚ__iter__æó zTransportAddressIPv4.__iter__cCó | ¡|Sr )r…©r{ÚitemrrrÚ __getitem__érˆz TransportAddressIPv4.__getitem__N)rkrlrmrnroÚ displayHintr@rrrFÚ fixedLengthryr…r‡rŒrrrrrvÏs rvc@ru)ÚTransportAddressIPv6aÝRepresents a transport address consisting of an IPv6 address and a port number (as used for example by UDP, TCP and SCTP): octets contents encoding 1-16 IPv6 address network-byte order 17-18 port number network-byte order This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.r_z 0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2décCsXtst d¡‚t|tƒr&ttj|dƒt|dd?d@ƒt|dd@ƒ}t   ||¡S)NúIPv6 not supported by platformrrr rt) Úhas_ipv6rÚ PySnmpErrorrwrxrr)r+rr@ryrzrrrryôs   4 zTransportAddressIPv6.prettyIncCs\t|dƒs+ts t d¡‚| ¡}ttj|dd…ƒt|dƒd>t|dƒBddf|_ |j S)Nr}r‘r&r ér) r~r’rr“rrr)r+rZ"_TransportAddressIPv6__tuple_valuer€rrrr‚üs  üz&TransportAddressIPv6.__asSocketAddresscCrƒr )r„Ú&_TransportAddressIPv6__asSocketAddressr†rrrr‡rˆzTransportAddressIPv6.__iter__cCr‰r )r•rŠrrrrŒ rˆz TransportAddressIPv6.__getitem__N)rkrlrmrnrorr@rrrFrŽryr•r‡rŒrrrrrís rc@ó,eZdZdZdZdZejeddƒZdZ dS)ÚTransportAddressIPv4za Represents a transport address consisting of an IPv4 address, a zone index and a port number (as used for example by UDP, TCP and SCTP): octets contents encoding 1-4 IPv4 address network-byte order 5-8 zone index network-byte order 9-10 port number network-byte order This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.r_z1d.1d.1d.1d%4d:2drdN© rkrlrmrnrorr@rrrFrŽrrrrr—ó r—c@r–)ÚTransportAddressIPv6zaRepresents a transport address consisting of an IPv6 address, a zone index and a port number (as used for example by UDP, TCP and SCTP): octets contents encoding 1-16 IPv6 address network-byte order 17-20 zone index network-byte order 21-22 port number network-byte order This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair.r_z#0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2déNr˜rrrrršr™ršc@s,eZdZdZdZdZdZeje ddƒZdS)ÚTransportAddressLocalz4Protocol Independent Interfaces (IEEE POSIX 1003.1g)aËRepresents a POSIX Local IPC transport address: octets contents encoding all POSIX Local IPC address string The Posix Local IPC transport domain subsumes UNIX domain sockets. This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair. When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers.r_Ú1arrtN) rkrlrmZ referencernrorr@rrrFrrrrrœs rœc@s(eZdZdZdZdZejeddƒZdS)ÚTransportAddressDnsaÀRepresents a DNS domain name followed by a colon ':' (ASCII character 0x3A) and a port number in ASCII. The name SHOULD be fully qualified whenever possible. Values of this textual convention are not directly useable as transport-layer addressing information, and require runtime resolution. As such, applications that write them must be prepared for handling errors if such values are not supported, or cannot be resolved (if resolution occurs at the time of the management operation). The DESCRIPTION clause of TransportAddress objects that may have TransportAddressDns values must fully describe how (and when) such names are to be resolved to IP addresses and vice versa. This textual convention SHOULD NOT be used directly in object definitions since it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with TransportAddressType or TransportDomain as a pair. When this textual convention is used as a syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the OBJECT-TYPE declaration MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers.r_rrrtN) rkrlrmrnrorr@rrrFrrrrrž#s ržúTRANSPORT-ADDRESS-MIBÚtransportDomainUdpIpv6ÚtransportDomainSctpDnsZPYSNMP_MODULE_IDÚtransportDomainTcpIpv4ÚtransportDomainLocalÚtransportDomainUdpIpv4ÚtransportDomainUdpIpv4zÚtransportDomainsÚtransportDomainSctpIpv4ÚtransportDomainSctpIpv6zÚtransportAddressMIBÚtransportDomainTcpIpv6zÚtransportDomainSctpIpv6ÚtransportDomainUdpDnsÚtransportDomainTcpIpv6ÚtransportDomainUdpIpv6zÚtransportDomainSctpIpv4zÚtransportDomainTcpIpv4zÚtransportDomainTcpDns)rŸ)UZpyasn1.compat.octetsrrZpysnmprZpysnmp.carrierrr)r’r~rrÚsysÚplatformr r r.Z mibBuilderZ importSymbolsr?r@rArBrCrDrErFrGrHrIrJrKrLrMrNrOrPrQrRrSrTrUrVrWrXrYrZZmib_2r[r\r©Z loadTextsZ setRevisionsZsetLastUpdatedZsetOrganizationZsetContactInfoZsetDescriptionr¦r¤Z setStatusr r¥r®r¢r­r°rªr§r«r¯r¨r£r¬r±r¡rjrprsrvrr—ršrœržZ exportSymbolsrrrrÚs²   0-R!¸