On Saturday 31 May 2008 03:05:56 [EMAIL PROTECTED]
wrote:
> 2008/5/30 jam <[EMAIL PROTECTED]>:
> > On Friday 30 May 2008 03:04:51 [EMAIL PROTECTED]
> > wrote:
> > [snip]
> >
> >> Sean Carte wrote:
> >> > I want to deploy LTSP in a situation where there is a pre-existing
> >> > DHCP server. From what I've read, the way to make this work involves
> >> > running a DHCP server on a different port and compiling a custom
> >> > kernel for LTSP with the DHCP client set to retrieve its data on that
> >> > port.
> >> >
> >> > I've found some documentation, including this:
> >> > http://ltsp.sourceforge.net/contrib/parallel_dhcp.txt, which mentions
> >> > ltsp_initrd_kit. But this appears to be available for LTSP 4 only.
> >> >
> >> > Is it possible to compile a custom kernel for LTSP 5? Are there
> >> > idiot-proof instructions anywhere? Or is there an easier way to
> >> > accomplish what I need?
> >> >
> >> > I'm running LTSP 5.0.40 on Ubuntu 8.04.
> >
> > There ARE cases where you can't use an existing DHCP server but they are
> > much rarer than first glance suggests.
> >
> > So ... why not use the existing server ...?
> >
> > An easy way is you run two servers in parallel. Your server responds ONLY
> > to MAC qualified queries. TCs boot correctly (in my experience) 50% of
> > the time, and try again for 50%
> >
> > Another way (assuming 24/7 or as appropriate) your DHCP server handles
> > everybody. I do that, took over from a Dlink-604. I even serve the
> > Dlink's wireless queries.
> >
> > James
>
> Thanks for the advice James.
>
> I have looked at using the existing DHCP server, but unfortunately it
> is a Netware server and the administrator says there's no way of
> rejecting specific MAC addresses.
Your DHCP server runs MACs only, don't touch theirs.
> He has offered to look at attempting to get it to hand out the tftp
> server info, but that seems unlikely to be doable if it's as limited
> as he suggests.
>
> That leaves us with creating a separate VLAN, or me putting the LTSP
> DHCP server on a different port.
See Jim's comment about PXE. Take other peoples advice about 'this is a bad
idea'
> So I'll have a go at following Steve's notes.
Me no nuffin (ok sorry for the play with language: I know nothing) about
netware DHCP server but
a) it does everything (and you need very little)
host ws123 {
next-server 192.168.5.120;
hardware ethernet 00:40:63:da:67:8d;
fixed-address ws123;
filename "/ltsp/i386/pxelinux.0";
}
b) you host ALL dhcp queries
c) You take the inconvenience and run two DHCP servers and YOURS does only
MACs./ See the wiki. (often 2 tries before TCs boot)
d) Seperate networks. I've run 2 networks on the same cat5 and switches.
Totally independantly. DHCP broadcast ... hmmmm ... It worked when I did try.
James
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
