CTCI-W32 Loopback Adapter fix (was: having trouble when use the new CTCI package)

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

shanyuliang wrote:

(reformatted)

> Dear all,
> I always use MS loopback adapter before, it works fine. But
> today I replace the CTCI with the new CTCI package, I got error,
> the message is:
> 
>   HHCTU002E Error opening TUN/TAP device: 02-00-4C-4F-4F-50:
>             No such file or directory.
> 
> I did not change any other configrations, just replace the old
> CTCI with the new one. I try the TT32Test program, I found that
> it does not find my Loopback Adapter. Is it the problem?

Yes -- *obviously*.

> By the way, I can find the loopback Adapter by the "ipconfig -all"
> command. 

Dear shanyuliang (and everyone too):

Please try the new 3.1.1b version just uploaded today to my web site:

  http://www.softdevlabs.com/Hercules/CTCI-W32_3.1.1b_bin.zip


It contains a workaround for the bug[1] in [apparently all versions
of] Microsoft's supplied "Loopback Adapter" device (as well as some
additional checks for some common user errors, such as not having
WinPCap installed (or improperly installed) and not having any
[usable] [WinPCap] network adapters defined).

I've tested it as best as I could from within my WinXP virtual
machine (which I apologize for not having done before) and it appears
to work just fine.

Please let me know (BY POSTING YOUR REPORT TO **>> THE LIST! <<** and
NOT to me!) if you have any trouble with it. If I don't receive any
negative responses regarding it within, say, a week or three, I'll go
ahead and release it as the official 3.1.1 fix release.

Thanks.

- -- 
"Fish" (David B. Trout) - fish(at)infidels.org
Fight Spam! Join CAUCE! <http://www.cauce.org/>
(Any HTML email received will be deleted unread)
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89  FE26 48F5 D7F4 C4EE 3E2A
RSA:    6B37 7110 7201 9917 9B0D  99E3 55DB 5D58 FADE 4A52

[1] According to MS's own documentation[2], support for querying the
'OID_GEN_MEDIA_CONNECT_STATUS' general NDIS object id is *MANDATORY*.
Yet, their own damn Loopback device drivers don't support it!
<grrrr!>  >:(

That's why the new version of CTCI-W32 wasn't allowing Loopback
Adapters to be used: because from ITS point-of-view they weren't
"usable" since FishPack's attempt to 'Open' the adapter failed
because one of its QueryOID calls (the one for
OID_GEN_MEDIA_CONNECT_STATUS) failed.[3]

The workaround was of course to simply treat this particular
Object-ID as being optional and simply setting the "connected" flag
to 'FALSE' if querying it fails.
<grumbledamnmicrosoftdoasisaybutnotasidopracticegrumble>

[2]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/NetXP
_r/hh/NetXP_r/22genoid_42acc619-4be7-4579-9beb-57c966b50c7d.xml.asp
(or: http://tinyurl.com/rc8ro)

[3] FishPack is very picky (perhaps too picky?) about which adapters
it says are available for use, and won't report a given adapter as
being available unless it makes it completely through its entire open
process within *any* errors whatsoever.

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBREc+Wkj11/TE7j4qEQLScgCdFEcnclGh+TNDUrW5fQeqmY1nAxcAn2s+
gokBGbIJWBcseWCdjurcCrsV
=GmqI
-----END PGP SIGNATURE-----




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/H390-VM/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/