Re: [SLE] is a dhcpserver related to 1 network card?

From: Jon Clausen (jon_at_stevnsgade.dk)
Date: 01/15/05

  • Next message: Carlos E. R.: "Re: [SLE] Kernel Woes: Comments, Please!" 
    Date: Sat, 15 Jan 2005 18:42:18 +0100
To: suse-linux-e@suse.com

    On Sat, 15 Jan, 2005 at 08:45:14 -0600, Doug B wrote:
    > On Saturday 15 January 2005 04:50 am, Richard Bos wrote:

    <snip>

    > > I don't know if I can change the config, and actually I don't want to
    > > change it. Anyway it is running that other OS....

    Hmmm... Does anything prevent you from ditching the present dhcp server?

    I think having more than one dhcp-server in a network is asking for trouble.
    And if the one already running doesn't provide you with the options you
    want... well I'd recommend swithing to one that will.

    AFAICT your options are basically:

    a) physically separate the existing network from the thin client network,
       and run separate dhcp-servers on each.

    b) set up *one* dhcp server to serve all clients in both networks via two
       interfaces.

    c) set up one dhcp server to serve all client (thin ones and regular alike)
       in one single network.
     
    For b) and c) you could certainly use the one included in the distro.

    > I *think*, you can do that. I haven't tried it. In my dhcp server, I
    > set each thin client up in a separate host section. I serve my thin
    > clients by mac address and use static ip addresses for them (and
    > sometimes some host specific options). I also serve the 'regular'
    > network clients with this dhcp server in a subnet section. If I pulled
    > that subnet section out, I *think* it would no longer serve the regular
    > network but would serve the individual hosts that were defined. Maybe
    > someone with more dhcp knowledge could answer that for sure.

    But the 'regular' dhcp server would probably still try to serve the thin
    clients...

    CMIIW

    /Jon 

    -- 
YMMV
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Carlos E. R.: "Re: [SLE] Kernel Woes: Comments, Please!"

    Relevant Pages

    • RE: Migrating 2000 workstations to 2003 domain
      ... Your understanding is correct that static IP address and DNS suffix will be ... we don't use static IP address in a network with more ... address after you migrate those 1000 clients from NT to win2k3 domain. ... I suggest you add a DHCP server in the ...
      (microsoft.public.windows.server.migration)
    • Re: 1 Machine, 2 NICs, 2 Instances of ntpd; Possible?
      ... time to clients on network B. ... I was considering running the ntpd instance A with the ... clock, and serve your clients. ...
      (comp.protocols.time.ntp)
    • Re: FC6: kickstart, static ip
      ... I do kickstart installations and try to assign a static ip ... After a successful installation process the clients come up and try to ... reach a dhcp server (see dhcp discovers in a network trace). ...
      (Fedora)
    • Re: DHCP security
      ... Since this network is only growing to include more and more ... configuration on new clients. ... concern is how do you stop a rogue DHCP server from getting on the ... However, a written, approved, and legally binding policy would ...
      (comp.os.linux.networking)
    • Re: D-Link Wireless Router and DHCP Problems
      ... > be a DHCP Server. ... It is able to serve an address to the hard-wired ... > unknown MAC Address. ... > Server got a little screwey with XP Clients on the network, ...
      (microsoft.public.windowsxp.general)