[OpenAFS-devel] Automated loopback adapter adding (on Windows)

[Dobes Vandermeer]

Another thing worth mentioning, is that if you port it to Visual Basic,
you might not need the header files or libs -- I think VB automatically
detects the available methods etc. on the objects, and reads functions
straight out of DLLs or something.  The code is all COM and would
probably actually be easier to implement in VB now that you can see
which functions to call.  I didn't think of this before, and I'm not a
VB programmer anyhow, but using my source as a reference you could
probably get some useful VB code to do what devcon does now, without the
need for the DDK.

Ben Creech wrote:
> 
> Thanks, I think I'll modify it to make it accept other IP addresses.  I had
> originally decided it wouldn't be worth the time (for my site) to redo
> devcon.exe.  However, since you've already done the work...
> 
> --On Thursday, July 17, 2003 2:42 PM -0700 Dobes Vandermeer
> <dobes@dobesland.com> wrote:
> 
> >
> > I've got a C++ version of this we've used for our project, it doesn't
> > use devcon; devcon isn't legally redistributable :( but it calls the
> > same function(s) devcon would so it *is* redistributable.
> >
> > It needs some headers from the DDK and links with setupapi.lib,
> > wbemuuid.lib and the basic windows libs.  Those headers cannot be
> > redistributed either, so you'll have to get a DDK to compile this.
> > Luckily you can redistribute the resulting binary.
> >
> > It configures the loopback adapter with 192.168.254.254/255.255.255.0.
> > This is hardcoded right now, as I haven't really bumped into any
> > conflicts and our installer doesn't ask the user about it.  If the user
> > wishes, he can modify the IP by changing the properties on the adapter
> > using the windows UI, after all.  If you are doing an automated install,
> > you can either recompile it with a new IP or a command-line parser.
> >
> > I've been waiting until I "spruced it up" before submitting it, and of
> > course never did.  So here's the source; if you want a binary (its 70k
> > zipped if I include the binary, and I didn't want to spam the list) I
> > can send that to whoever requests it.
> >
> > If you do make use of it, please submit bugs back to me...
> >
> > Ben Creech wrote:
> >>
> >> As previously mentioned on these lists, putting the Windows OpenAFS
> >> Client on the Microsoft Loopback adapter may make it less error-prone.
> >> Thanks to Scott Williams' patch in 1.2.8+, the client will automatically
> >> bind to it if it's installed.
> >>
> >> However, installing the loopback adapter is somewhat troublesome to
> >> automate.  I figured I'd make public the thing I just made for an AD
> >> domain here:
> >> <http://www4.ncsu.edu/~bpcreech/loopback/>
> >>
> >> This isn't exactly tested in a production environment yet, so ymmv, etc.
> >> It has worked so far on all the Win2k and XP boxes I've tested it on.
> >> Don't know (or care) if it runs on anything less.
> >>
> >> For more info, look here:
> >> <http://grand.central.org/twiki/bin/view/AFSLore/WindowsLoopBackAdapter>
> >>
> >> _______________________________________________
> >> OpenAFS-devel mailing list
> >> OpenAFS-devel@openafs.org
> >> https://lists.openafs.org/mailman/listinfo/openafs-devel
> 
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel