Results 1 to 8 of 8

Thread: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

  1. #1
    Join Date
    Jul 2006
    Beans
    4,842

    Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    I'm curious if anybody can shed some light for me in this department. We're in a large environment with a Windows DHCP Server. We have been tinkering with LTSP on Edubuntu as thin and fat clients. It works great, but right now we just have 1 server handling the lab, which works fine unless we want to expand, which may be very possible.

    These are the instructions I received:

    • Login to your windows server and load the DHCP configuration screen
    • Create a DHCP reservation for the MAC address you obtained
    • Add the configuration options below to enable the machine to boot from the LTSP server
    • 017 Root Path: /opt/ltsp/i386
    • 066 Boot Server Host Name: <ip address>
    • 067 Bootfile Name: ltsp/arch/pxelinux.0 # Specify CPU architecture in place of 'arch', for instance 'i386'


    From: https://help.ubuntu.com/community/Ub...TSPWindowsDHCP

    I'm curious, what if I want to have multiple Ubuntu servers on the network that I want to have bootable? For example, let's say I have 3 labs, and 3 servers. Server A to Lab A, Server B to Lab B, and Server C to Lab C. I want all C's computers to boot to C, and B to B, A to A, etc.

    1 - How would I add multiple entries on the Windows DHCP Server to allow all 3 (A B C) servers to boot?

    2 - How would I be able to isolate the clients so ONLY Lab A clients boot to Server A, etc?

  2. #2
    Join Date
    Jul 2007
    Location
    Atlanta, GA
    Beans
    668
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Without going into the detailed bits...you would use three different subnets for A, B, and C (and therefore three different DHCP Scopes on your Windows server configured respectively). The second half would be to use VLANs to isolate your traffic and configure DHCP helper addresses (also called DHCP proxy) to forward the requests to the Windows DHCP server.

    Cheers!

  3. #3
    Join Date
    Jul 2006
    Beans
    4,842

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Not sure I follow. If we can't do subnetting with our environment already being set up, is a proxy the only alternative? Secondly, how difficult is that to set up?

  4. #4
    Join Date
    Dec 2010
    Beans
    31

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Another simple way, avoiding VLANs etc, might be to ditch DHCP and settle for fixed Ip addresses. Unusual but doable.

  5. #5
    Join Date
    Jul 2006
    Beans
    4,842

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Quote Originally Posted by boldford View Post
    Another simple way, avoiding VLANs etc, might be to ditch DHCP and settle for fixed Ip addresses. Unusual but doable.
    2,000 systems here at work.

    This certainly falls under undoable.

    Any other suggestions to make this work?

  6. #6
    Join Date
    Jul 2007
    Location
    Atlanta, GA
    Beans
    668
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Quote Originally Posted by Roasted View Post
    Not sure I follow. If we can't do subnetting with our environment already being set up, is a proxy the only alternative? Secondly, how difficult is that to set up?
    It was not meant to be two separate approaches but two steps in conjunction to accomplish the network isolation setup.

    The other option is to configure the labs as isolated networks where each lab subnet has its own DHCP server configured.

    If you prefer to keep DHCP on the single server, let me know how your networking is configured and we can workout the config changes needed to implement the vlans and DHCP proxy bits. DHCP proxy is typically configured on the network switch or the subnet default gateway. All it does it receive the DHCP requests from the clients and pass it along to a specified DHCP server on another subnet to assign the address to the client.

    Cheers!

  7. #7
    Join Date
    Nov 2006
    Location
    Belgium
    Beans
    3,025
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    Quote Originally Posted by Fire_Chief View Post
    The other option is to configure the labs as isolated networks where each lab subnet has its own DHCP server configured.
    how about 1 dhcp with multiple NICs, 1 in each subnet ?


    although long term, with 2000 hosts and with future expansion "quite possible", VLANs and a bit of network redesign maybe isn't a bad idea

  8. #8
    Join Date
    Jul 2006
    Beans
    4,842

    Re: Windows DHCP Server - Multiple Linux Boot Servers. Ehh?

    After discussing it more, I think that's what we're doing, is giving each server it's own DHCP service with its own scope, and VLAN'ing it from the rest of the network. I suppose it makes sense, to have 1 VLAN per lab. I hear of some schools doing this anyway. Now that we're doing this it does make more sense. I guess I just need to read up more on VLANing.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •