[K12OSN] is it possible to use Windows DHCP server with LTSP?

[john]

Hi Chuck,

A couple of questions:

1) Do I need option 12, the netvista option, if I am not using netvistas? Is
this a generic netboot parameter?

2) If windows pads the root path with 000 do I need a symlink on my linux
server from a directory called /opt/ltsp/i386000 > /opt/ltsp/i386

3) is the string for option 211 always tftp?

4) I glibly said I had the other boot parameters (ip, subnet mask, gateway)
correctly set, because those parameters are the defaults handed over by the
dhcp server on that scope. As I think about it I think I should be using an
ip, subnet mask, and gateway consistent with that of the ltsp server (which
sits on a different subnet than my test client. So if my LTSP server is
10.114.0.105/16 my clients should be 10.114.0.x/16 and use 10.114.0.105 as
the gateway. Err, but perhaps I am getting myself in a muddle here.

Thanks again.

John


On 10/18/06, cliebow at midmaine.com <cliebow at midmaine.com> wrote:
>
> also remember windows pads the root path with three 000s
>
>
> http://wiki.ltsp.org/twiki/bin/view/Ltsp/DHCP#Adding_options_to_windows_dhcp_t
>
>
>
> In windows dhcp add options 12 17 66 67 and create a new option 211
>
> option 12 netvista1 option 17 10.10.10.254:/opt/ltsp/i386 option 66
> 10.10.10.254 option 67 /opt/ltsp/i386/vmlinux-2.4.19-LTSP-IBMNC option 211
> tftp
>
> Remember that windows pads the root-path with 000 so the path passed to
> the terminal is /opt/ltsp/i386000.
>
> Creating option 211-from command line type netsh..this give a secondary
> command line.tpye dhcp server..gives a tertiary command line..type add
> OptionDef? 211 BootProtocol? STRING.
>
>
>
> > atypo? /tftpboot?
> >
> >
> >> Wow,
> >>
> >> I guess I'll keep reading. It seems pretty cryptic. I assume that If I
> >> managed to get the right DHCP options configured, i'd also need to edit
> >> /etc/hosts, /etc/hosts.allow and /etc/exports. My client picks up the
> IP
> >> I
> >> reserved for it along with correct subnet mask and route but doesn't
> get
> >> handed an image.
> >>
> >> For the record, this is what I have, but it doesn't work, yet:
> >>
> >> 017 Root Path    10.114.0.105:/opt/ltsp-4.2/i386
> >> 060 PXEClient
> >> 066 Boot Server Host Name   10.114.0.105
> >> 067 Bootfile Name /tftboot/lts/2.6.17.8-ltsp-1/pxelinux.0
> >>
> >> I guess I need to do a bit of reading and see if I can suss out what's
> >> needed. If I ever figure it out it would be a great one for the
> >> ltsp.wiki!
> >>
> >> John
> >>
> >> On 10/18/06, cliebow at midmaine.com < cliebow at midmaine.com> wrote:
> >>>
> >>> option 17 10.10.10.254:/opt/ltsp/ppc
> >>> option 43 01 01 02 08 04 00 00 01 82 05 69 6d 61 63 34
> >>> option 60 PXEClient
> >>> option 66 10.10.10.254
> >>> option 67 /yaboot
> >>> option 211 74:66:74:70
> >>>
> >>> add options using netsh for options not normally in dhcp .Get a
> command
> >>> prompt
> >>>
> >>> netsh
> >>> dhcp server
> >>> add optionDef 211 BootProtocol STRING
> >>>
> >>> pretty easy to add options..never tried option 128/9 though..chuck
> >>>
> >>> _______________________________________________
> >>> K12OSN mailing list
> >>> K12OSN at redhat.com
> >>> https://www.redhat.com/mailman/listinfo/k12osn
> >>> For more info see < http://www.k12os.org>
> >>>
> >> _______________________________________________
> >> K12OSN mailing list
> >> K12OSN at redhat.com
> >> https://www.redhat.com/mailman/listinfo/k12osn
> >> For more info see <http://www.k12os.org>
> >
> >
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> >
>
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/k12osn/attachments/20061019/1ed31220/attachment.htm>