| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
ioctl SIOCGIFCONG question in libport 1.0
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 ioctl SIOCGIFCONG question in libport 1.0 - Jun. 14, '06, 5:56:50 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Hi-
I'm relatively new to SFU and to these forums.. so please redirect me if I'm in the wrong place with this.
I'm porting over a bunch of code that needs to be aware of the local NICs on the system and their status. After initially determining that the SIOCGIFCONF option for ioctl isn't supported in base SFU 3.5, I found and installed libport 1.0 on these forums.
Using this, my apps now compile and link just fine, but when I try to run:
ioctlReturn = ioctl(sd, SIOCGIFCONF, &nicInterfaceList);
I'm getting a return of -1, with errno 22 (invalid argument).
I've tried a few different things, but suspect that I'm not linking in the correct ioctl (ie not the one from libport). Here are the relevant portions of my build and compile lines. Can you tell me what I'm doing wrong?
Compiling foo.cxx ...
/opt/gcc.3.3/bin/gcc -B/opt/gcc.3.3// -D_ALL_SOURCE -D_USE_LIBPORT -D_REENTRANT -I/usr/include/port -I/usr/include -I/usr/local/include -c foo.cxx -o objs/i86Win32SFU3.5gcc3.3/foo.o
Linking ../../bin/i86Win32SFU3.5gcc3.3/bar ...
/opt/gcc.3.3/bin/g++ -B/opt/gcc.3.3// -o blah.o blahblah.a
-static-libgcc -ldl -lm -lpthread -lsocket -lport -lbind
Thanks!
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 14, '06, 9:46:58 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
The compile line looks a bit odd. The "-I/usr/include" isn't needed and may mess things up.
At least I've experienced this happening. It's also important to have /usr/local/include
header files picked up before /usr/include. You have /usr/include/port in the right sopt.
You don't need the "-B". Gcc was built to this location already, but that should be neither
here nor there.
Check the file that's calling ioctl() that it actually does "#include <sys/ioctl.h>".
If this isn't there then the compile-time magic won't happen.
Verify with the object after by doing "nm foo.o | grep port_ioctl".
< Message edited by Rodney -- Jun. 15, '06, 1:54:48 PM >
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 15, '06, 1:22:46 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Thanks for the quick reply, Rodney.
I found the problem here. The issue was the size of the buffer allocated to the ifconf call. Looking through the headers I saw that you set the buffer size in an ifreq to 512.. much larger than on other OSes. When I increased the buffer size I provided from 1024 bytes to 4096 the call no longer errors.
I also pulled the extra include, just in case it tried to cause me problems down the line.
Thanks again! Hopefully this will be my last hurdle here (knock on wood).
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 15, '06, 4:04:22 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
A follow-up here..
So the call doesn't fail, but the data that comes back from
ioctlReturn = ioctl(sd, SIOCGIFCONF, &nicInterfaceList);
doesn't seem right.
I get the following output.. lo0 looks like it gets loopback, but the other nics return 255.255.255.255
for their IP address.
I am configuring my NICs with DHCP (though I don't see why that would cause a problem).
There also seems to be a 2-byte alignment issue somewhere in my code when reading this
(though this could be my problem).
Seen this before?
-Bob
NDDS: Got 3168/4096 bytes of interface data:
NDDS: 0> 6c 6f 30 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: l o 0 .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 10> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 20> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 30> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 40> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 50> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 60> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 70> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 80> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 90> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 100> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 110> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 120> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 130> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 140> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 150> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 160> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 170> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 180> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 190> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 1f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 200> 02 00 7f 00 00 01 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 210> 6e 69 63 31 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: n i c 1 .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 220> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 230> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 240> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 250> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 260> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 270> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 280> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 290> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 2f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 300> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 310> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 320> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 330> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 340> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 350> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 360> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 370> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 380> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 390> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 3f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 400> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 410> 02 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 420> 6e 69 63 32 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: n i c 2 .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 430> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 440> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 450> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 460> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 470> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 480> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 490> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 4f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 500> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 510> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 520> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 530> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 540> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 550> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 560> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 570> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 580> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 590> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 5f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 600> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 610> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 620> 02 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 630> 6e 69 63 33 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: n i c 3 .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 640> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 650> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 660> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 670> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 680> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 690> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 6f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 700> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 710> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 720> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 730> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 740> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 750> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 760> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 770> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 780> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 790> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7a0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7b0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7c0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7d0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7e0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 7f0> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 800> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 810> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 820> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NDDS: 830> 02 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00
NDDS: .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 12:05:11 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> I get the following output.. lo0 looks like it gets loopback, but the other nics return 255.255.255.255
> for their IP address.
Yes, lo0 is the loopback. It's not actually in the registry where the other information comes from.
But all of the actual NIC information is in the registry. It gets gathered from various locations.
The information gathered is how things are right at the time it's gathered. If you are using DHCP
this might reflect that state at that exact time. Was the machine connected to the network?
What you're seeing is likely the 255.255.255.255 as INADDR_NONE. That is what's filled in
when the registry doesn't make sense and can't get translated.
It may also be you have the lucky machine that's done things slightly different.
I put this heuristic ioctl() call together based on what machines I have access to plus
feedback from other Forum members passed along from their registries.
So if there's some adjustments to make it can be done.
The 0x02 is AF_INET the family BTW.
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 10:04:18 AM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
The machine was definitely on the network at the time.. all the code I build is NFS mounted from my solaris server.
Where is it looking in the registry for information? I just searched my registry for "nic2" and didn't get
any matches. ("nic1" partial matches some device drivers). If I need to add/modify an entry somewhere, I'm happy to
do so.. at this point I'll take a configuration hack in order to get this working.
Is libport source somewhere I can get at it? I wouldn't mind taking a look at what it is doing.
For what it's worth, my machine is WinXP Pro, Version 2002, SP 2 and has 2 active networks (both DHCP).
Thanks for any help you can give me.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 12:51:13 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Sorry, the names are in "debug" mode right now. The long strings are awful
to read. Look in HKLM/System/CUrrentControlSet/Services/Tcpip/Parameters/Interfaces
in the registry for the NIC's. Note that these are not all necessarily active.
The wonderful names start with "{" followed by hex. In each you'll see about
10 to 20 values, depending. Your looking to see what keys have IP addresses in them.
Usually it's "IPAddress", but it may be something else.
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 1:32:37 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Thanks.. I think the DHCP usage might be the problem. In the registry it doesn't fill in IP Address, it only fills DhcpIPaddress.
Any chance you can make it look at the DhcpIPAddress field if the IPAddress field is empty? I'm not sure I can force the customer not to use DHCP.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 4:14:55 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Also... how does it decide how many interfaces to return? My registry contains 8 interfaces
but I'm only getting back 3 + loopback (and none of those appear to be the one that I statically
configured with an IP address). I love windows networking.. I have 2 active NICs and 8 entries in the registry.
While you're looking into that I'll try to figure out why the address is 2 bytes off of where
my code thinks it should be.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 6:39:38 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Hi Rodney-
One last additional issue here.. then hopefully I'll get out of your hair ;)
I'm pretty sure that the reason we are two bytes off in our calculations is that the interface buffer
returned from:
ioctlReturn = ioctl(sd, SIOCGIFCONF, &nicInterfaceList);
is missing the port information.
In particular if you look at the last line of the dump from above (for lo0) you see:
NDDS: 200> 02 00 7f 00 00 01 00 00 00 00 00 00 00 00 00 00
This is the memory in the union portion of:
struct ifreq {
char ifr_name[IFNAMSIZ]; /* e.g. "fxp0" */
union {
struct sockaddr ifru_addr;
struct sockaddr ifru_dstaddr;
struct sockaddr ifru_broadaddr;
short ifru_flags;
int ifru_metric;
caddr_t ifru_data;
} ifr_ifru;
Typically when we want to use this we cast the "generic" sockaddr to a sockaddr_in type
for decoding as an IPv4 socket address, as per Steven's networking book.
This type looks like (comments added for clarity):
struct sockaddr_in {
sa_family_t sin_family; /* this is really an unsigned short */
in_port_t sin_port; /* this is really an unsigned short */
struct in_addr sin_addr;
char sin_zero[8];
};
Clearly the sin_port member isn't being included in the byte dump above, leading to the 2byte
offsite I referred to in a previous post.
I'm not sure that this is necessarily a bug and I can likely work around it easily enough,
but it is a variance from how this works on Solaris, Linux, IRIX and VxWorks (the other OSes
we support that have ioctl) so I thought you'd like to know.
Thanks again!
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 16, '06, 11:37:37 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> Any chance you can make it look at the DhcpIPAddress field if the IPAddress field is empty?
Yes, I can do that. Odd that I hadn't before because the other ioctl()'s I did do
look for DHCP alternatives. Is the "EnableDhcp" entry there and set to 0x1 too?
> Also... how does it decide how many interfaces to return? My registry contains 8 interfaces
Yeah, that's what I was alluding to earlier - that you'll see more.
There's another registry entry that has active lists that are consulted.
...Tcpip/Linkage/Bind
For some reason I implemented it as an in_addr... can't remember why now.
Ah, because the 'struct sockaddr' is sa_family and then sa_data.
I can switch that for portability.
Your comment is good feedback -- thanks.
|
|
|
|
|
RE: ioctl SIOCGIFCONF question in libport 1.0 - Jun. 17, '06, 7:18:08 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
I've put in the beta directory version 1.1.1 which have these changes. Or at least
the first kick at them (hence, beta). The other i/f's are unchanged. The extensions
for libport working with c89 (aka MSVC) are part of this.
If this seems to go for you then I'll do a cleanup and a general release.
If you do (since it's beta) "pkg_add ftp://ftp.interopsystems.com/pkgs/beta/libport-1.1.1-bin.tgz"
it'll update what you have to this beta.
< Message edited by Rodney -- Jun. 23, '06, 3:36:35 AM >
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 19, '06, 11:24:25 AM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Thanks, Rodney! Your response time is fantastic.
I'll grab the download tonight and see how it works tomorrow.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 22, '06, 6:38:03 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Hi Rodney-
The change to allow use of the sockaddr_in cast works great, but I'm still having problems
detecting all the NICs. I am getting loopback and 5 invalid networks back from the ioctl call.
It looks like it is now properly including NICS that have the EnableDHCP key set to 0x1, however it isn't
properly getting the IP address of that NIC. It is still returning 255.255.255.255. My suspicion is that
this is because the IPAdddress key is set to 0.0.0.0 for this interface. However the DhcpIpAddress key *is*
properly set and should be the value returned here.
Here is the registry output for the NIC that is up.
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{81D18F17-9542-4022-B4DE-B94EC0AA500B}
Class Name: <NO CLASS>
Last Write Time: 6/22/2006 - 3:03 PM
Value 0
Name: UseZeroBroadcast
Type: REG_DWORD
Data: 0x0
Value 1
Name: EnableDeadGWDetect
Type: REG_DWORD
Data: 0x1
Value 2
Name: EnableDHCP
Type: REG_DWORD
Data: 0x1
Value 3
Name: IPAddress
Type: REG_MULTI_SZ
Data: 0.0.0.0
Value 4
Name: SubnetMask
Type: REG_MULTI_SZ
Data: 0.0.0.0
Value 5
Name: DefaultGateway
Type: REG_MULTI_SZ
Data:
Value 6
Name: DefaultGatewayMetric
Type: REG_MULTI_SZ
Data:
Value 7
Name: NameServer
Type: REG_SZ
Data:
Value 8
Name: Domain
Type: REG_SZ
Data:
Value 9
Name: RegistrationEnabled
Type: REG_DWORD
Data: 0x1
Value 10
Name: RegisterAdapterName
Type: REG_DWORD
Data: 0x0
Value 11
Name: TCPAllowedPorts
Type: REG_MULTI_SZ
Data: 0
Value 12
Name: UDPAllowedPorts
Type: REG_MULTI_SZ
Data: 0
Value 13
Name: RawIPAllowedProtocols
Type: REG_MULTI_SZ
Data: 0
Value 14
Name: NTEContextList
Type: REG_MULTI_SZ
Data: 0x00000002
Value 15
Name: DhcpClassIdBin
Type: REG_BINARY
Data:
Value 16
Name: DhcpServer
Type: REG_SZ
Data: 192.168.1.1
Value 17
Name: Lease
Type: REG_DWORD
Data: 0x1517d
Value 18
Name: LeaseObtainedTime
Type: REG_DWORD
Data: 0x449b0c40
Value 19
Name: T1
Type: REG_DWORD
Data: 0x449bb4fe
Value 20
Name: T2
Type: REG_DWORD
Data: 0x449c2b1d
Value 21
Name: LeaseTerminatesTime
Type: REG_DWORD
Data: 0x449c5dbd
Value 22
Name: IPAutoconfigurationAddress
Type: REG_SZ
Data: 0.0.0.0
Value 23
Name: IPAutoconfigurationMask
Type: REG_SZ
Data: 255.255.0.0
Value 24
Name: IPAutoconfigurationSeed
Type: REG_DWORD
Data: 0x925393e8
Value 25
Name: AddressType
Type: REG_DWORD
Data: 0x0
Value 26
Name: DhcpIPAddress
Type: REG_SZ
Data: 192.168.1.56
Value 27
Name: DhcpSubnetMask
Type: REG_SZ
Data: 255.255.255.0
Value 28
Name: DhcpRetryTime
Type: REG_DWORD
Data: 0xa8be
Value 29
Name: DhcpRetryStatus
Type: REG_DWORD
Data: 0x0
Value 30
Name: DhcpNameServer
Type: REG_SZ
Data: 192.168.1.1
Value 31
Name: DhcpDefaultGateway
Type: REG_MULTI_SZ
Data: 192.168.1.1
Value 32
Name: DhcpSubnetMaskOpt
Type: REG_MULTI_SZ
Data: 255.255.255.0
Thanks for any help you can give here.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 22, '06, 7:17:03 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Hi Rodney-
Actually, I had another request. Can you modify the ioctl call so that it only returns NICs that aren't INADDR_NONE?
I don't know for sure that this is standard practice, but we don't check for this return on any architectures currently.
I'm open to the possibility that this is a bug in our code, but on windows it appears it is return lots of pseudo devices
that aren't true interfaces.
-Bob
|
|
|
|
|
RE: ioctl SIOCGIFCONG question in libport 1.0 - Jun. 23, '06, 3:43:10 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Thanks for the registry info. I'll check why it's not happening right yet.
I'll filter that non-active devices don't get returned. Windows OS does seem
to have a lot of "extra entries" not see on other systems. I know that some
of these can be older NIC cards that have been removed.
|
|
|
|
|
RE: ioctl SIOCGIFCONF question in libport 1.0 - Jun. 23, '06, 4:09:46 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> Thanks for the registry info. I'll check why it's not happening right yet.
It was simple enough to fix (so many macros & I typed the wrong one).
Let me know if the filtering seems okay for you.
Do similar to before: pkg_add ftp://ftp.interopsystems.com/pkgs/beta/libport-1.1.2-bin.tgz
(from 1.1.1 to 1.1.2)
|
|
|
|
|
RE: ioctl SIOCGIFCONF question in libport 1.0 - Jun. 28, '06, 6:34:02 PM
|
|
|
kindel
Posts: 22
Joined: Jun. 6, '06,
Status: offline
|
Hi Rodney-
Thanks for the new version.. unfortunately it doesn't fix the problem (may make it worse, actually :( )
Right now all I get out is the loopback device. The device listed above doesn't show up and the other guy working with this (who uses static IP) doesn't see either of his network devices either.
For completeness, here are his registry entries. I don't know if his machine worked with the 1.1beta patch, he only tried with the 1.2.
Thanks again for all your help with this. Without you, we would likely have given up.
-Bob
NIC 1
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{B83E2DD0-8E30-4371-A113-F71FA8E89F9F}ഀ
Class Name: <NO CLASS>ഀ
Last Write Time: 6/21/2006 - 1:55 PMഀ
Value 0ഀ
Name: UseZeroBroadcastഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 1ഀ
Name: EnableDeadGWDetectഀ
Type: REG_DWORDഀ
Data: 0x1ഀ
ഀ
Value 2ഀ
Name: EnableDHCPഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 3ഀ
Name: IPAddressഀ
Type: REG_MULTI_SZഀ
Data: 172.16.0.1ഀ
ഀ
Value 4ഀ
Name: SubnetMaskഀ
Type: REG_MULTI_SZഀ
Data: 255.255.255.0ഀ
ഀ
Value 5ഀ
Name: DefaultGatewayഀ
Type: REG_MULTI_SZഀ
Data: ഀ
ഀ
Value 6ഀ
Name: DefaultGatewayMetricഀ
Type: REG_MULTI_SZഀ
Data: ഀ
ഀ
Value 7ഀ
Name: NameServerഀ
Type: REG_SZഀ
Data: ഀ
ഀ
Value 8ഀ
Name: Domainഀ
Type: REG_SZഀ
Data: ഀ
ഀ
Value 9ഀ
Name: RegistrationEnabledഀ
Type: REG_DWORDഀ
Data: 0x1ഀ
ഀ
Value 10ഀ
Name: RegisterAdapterNameഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 11ഀ
Name: TCPAllowedPortsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 12ഀ
Name: UDPAllowedPortsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 13ഀ
Name: RawIPAllowedProtocolsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 14ഀ
Name: NTEContextListഀ
Type: REG_MULTI_SZഀ
Data: 0x00000002ഀ
ഀ
ഀ
NIC 2:
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2ED8D3A2-6D75-4AA9-937A-2DCAA7955935}ഀ
Class Name: <NO CLASS>ഀ
Last Write Time: 6/21/2006 - 2:40 PMഀ
Value 0ഀ
Name: UseZeroBroadcastഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 1ഀ
Name: EnableDeadGWDetectഀ
Type: REG_DWORDഀ
Data: 0x1ഀ
ഀ
Value 2ഀ
Name: EnableDHCPഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 3ഀ
Name: IPAddressഀ
Type: REG_MULTI_SZഀ
Data: 10.190.213.108ഀ
ഀ
Value 4ഀ
Name: SubnetMaskഀ
Type: REG_MULTI_SZഀ
Data: 255.255.255.0ഀ
ഀ
Value 5ഀ
Name: DefaultGatewayഀ
Type: REG_MULTI_SZഀ
Data: 10.190.213.193ഀ
ഀ
Value 6ഀ
Name: DefaultGatewayMetricഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 7ഀ
Name: NameServerഀ
Type: REG_SZഀ
Data: 10.190.213.196,4.22.69.5ഀ
ഀ
Value 8ഀ
Name: Domainഀ
Type: REG_SZഀ
Data: ഀ
ഀ
Value 9ഀ
Name: RegistrationEnabledഀ
Type: REG_DWORDഀ
Data: 0x1ഀ
ഀ
Value 10ഀ
Name: RegisterAdapterNameഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 11ഀ
Name: TCPAllowedPortsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 12ഀ
Name: UDPAllowedPortsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 13ഀ
Name: RawIPAllowedProtocolsഀ
Type: REG_MULTI_SZഀ
Data: 0ഀ
ഀ
Value 14ഀ
Name: NTEContextListഀ
Type: REG_MULTI_SZഀ
Data: 0x00000003ഀ
ഀ
Value 15ഀ
Name: DhcpClassIdBinഀ
Type: REG_BINARYഀ
Data: ഀ
ഀ
Value 16ഀ
Name: DhcpServerഀ
Type: REG_SZഀ
Data: 255.255.255.255ഀ
ഀ
Value 17ഀ
Name: Leaseഀ
Type: REG_DWORDഀ
Data: 0xe10ഀ
ഀ
Value 18ഀ
Name: LeaseObtainedTimeഀ
Type: REG_DWORDഀ
Data: 0x4499a42cഀ
ഀ
Value 19ഀ
Name: T1ഀ
Type: REG_DWORDഀ
Data: 0x4499ab34ഀ
ഀ
Value 20ഀ
Name: T2ഀ
Type: REG_DWORDഀ
Data: 0x4499b07aഀ
ഀ
Value 21ഀ
Name: LeaseTerminatesTimeഀ
Type: REG_DWORDഀ
Data: 0x4499b23cഀ
ഀ
Value 22ഀ
Name: IPAutoconfigurationAddressഀ
Type: REG_SZഀ
Data: 0.0.0.0ഀ
ഀ
Value 23ഀ
Name: IPAutoconfigurationMaskഀ
Type: REG_SZഀ
Data: 255.255.0.0ഀ
ഀ
Value 24ഀ
Name: IPAutoconfigurationSeedഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
Value 25ഀ
Name: AddressTypeഀ
Type: REG_DWORDഀ
Data: 0x0ഀ
ഀ
|
|
|
|
|
RE: ioctl SIOCGIFCONF question in libport 1.0 - Jun. 29, '06, 4:12:01 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
I'll look to see what I did.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
