Re: GetIpAddrTable
- From: v-terryf@xxxxxxxxxxxxxxxxxxxx ("TerryFei")
- Date: Mon, 13 Mar 2006 07:48:44 GMT
Hi Norman,
I just wanted to check how things are going and whether community member's
suggestion is useful for you. If there is any question, please feel free to
join the community and we are here to support you at your convenience.
Thanks for your understanding!
Best Regards,
Terry Fei[MSFT]
Microsoft Community Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
From: "Norman Diamond" <ndiamond@xxxxxxxxxxxxxxxx><eDtMT$oQGHA.5092@xxxxxxxxxxxxxxxxxxxx>
References: <OuNuYRnQGHA.5812@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: GetIpAddrTablemicrosoft.public.win32.programmer.networks:29170
Date: Wed, 8 Mar 2006 18:35:53 +0900
Lines: 41
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-2022-jp";
reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Message-ID: <uESh0OpQGHA.2628@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.win32.programmer.networks
NNTP-Posting-Host: p1185-ipad501marunouchi.tokyo.ocn.ne.jp 222.148.32.185
Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
Xref: TK2MSFTNGXA03.phx.gbl
X-Tomcat-NG: microsoft.public.win32.programmer.networksin
I think that the order which you see in memory and the order which I see
memory are the same. I think that order is network order not host order.:
Load the DWORD from memory into a register and you get 0x681010ac. Before
doing any further processing in the host you have to call ntohl.
"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:eDtMT$oQGHA.5092@xxxxxxxxxxxxxxxxxxxxxxx
Hi,Norman!
dwAddr and dwMask sit exactly in host order and not net and here example
104My IP in lan is 172.16.16.104 what I see after return from the function
those are bytes ( in memory ) : ac 10 10 68 hex ( which is 172 16 16
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iphlp/iphlpdecimal) , so ac sit in lowest byte and 68 in highest ( due to Intel's (
host ) byte order ( little endian ) ) of dword and network order demand
172 (ac hex ) to be in highest byte et al accordingly
Arkady
"Norman Diamond" <ndiamond@xxxxxxxxxxxxxxxx> wrote in message
news:OuNuYRnQGHA.5812@xxxxxxxxxxxxxxxxxxxxxxx
/managing_ip_addresses_using_getipaddrtable.asp
valuessays:
Note The DWORD objects dwAddr and dwMask are returned as numerical
values
in host byte order, not network byte order.
As far as I can tell, dwAddr and dwMask are returned as numerical
convertin
network byte order, not host byte order. I have to call ntohl to
them.
The page doesn't say anything about the byte order of dwBCastAddr, but
that
doesn't matter. As far as I can tell, dwBCastAddr isn't a broadcast
address in any byte order or bit order.
Does anyone find more sensible information in these fields?
.
- References:
- GetIpAddrTable
- From: Norman Diamond
- Re: GetIpAddrTable
- From: Arkady Frenkel
- Re: GetIpAddrTable
- From: Norman Diamond
- GetIpAddrTable
- Prev by Date: Re: Howto get workgroup name
- Next by Date: Re: How to connect to a network share as a different user
- Previous by thread: Re: GetIpAddrTable
- Next by thread: Re: storing a zip file on a server
- Index(es):
Relevant Pages
|