RE: Mapping between long and ASN_IPADDRESS

2004-06-03 Thread Mukherjee, Arijit (Arijit)
ne 02, 2004 3:14 PM To: Mukherjee, Arijit (Arijit) Cc: [EMAIL PROTECTED] Subject: Re: Mapping between long and ASN_IPADDRESS > However, when queried from manager, the agent returns the . separated > IPAddress. No - the agent returns a four-octet binary string (ratehr than an unsigned long)

RE: Mapping between long and ASN_IPADDRESS

2004-06-02 Thread Mukherjee, Arijit (Arijit)
3:14 PM To: Mukherjee, Arijit (Arijit) Cc: [EMAIL PROTECTED] Subject: Re: Mapping between long and ASN_IPADDRESS > However, when queried from manager, the agent returns the . separated > IPAddress. No - the agent returns a four-octet binary string (ratehr than an unsigned long). It

Re: Mapping between long and ASN_IPADDRESS

2004-06-02 Thread Dave Shield
> However, when queried from manager, the agent returns the . separated > IPAddress. No - the agent returns a four-octet binary string (ratehr than an unsigned long). It's the client that *displays* this as a dotted-quad. Given the varbind ('vb') that's returned, the code is basically: prin

Mapping between long and ASN_IPADDRESS

2004-06-02 Thread Mukherjee, Arijit (Arijit)
All, I have a very basic doubt - and do not know where to look for. In the mibmodule, for IpAddress type, the datatype generated by mib2c is "unsigned long". However, when queried from manager, the agent returns the . separated IPAddress. Could someone explain the basic logic of how the unsig