Re: [SLE] is a dhcpserver related to 1 network card?
From: Doug B (suse_at_hatterhill.com)
Date: 01/15/05
- Previous message: C Hamel: "Re: [SLE] Kernel Woes: Comments, Please!"
- In reply to: Jon Clausen: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Next in thread: Richard Bos: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Reply: Richard Bos: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Sat, 15 Jan 2005 12:27:23 -0600
On Saturday 15 January 2005 11:42 am, Jon Clausen wrote:
> AFAICT your options are basically:
>
> a) physically separate the existing network from the thin client
> network, and run separate dhcp-servers on each.
>
>
> > 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...
I think option a) is indeed the fact. IIRC the 'new' dhcp server had
two nics. One to the 'reg' network and one to the 'thin' network. If
the thin clients are on their own switch along with the 'thin' nic on
the 'new' dhcp server then I think it should work with little or no
chance of one dhcp server interfering with the other. By deleteing the
subnet section of the 'new' dhcp server you eliminate (I think) the
possibility of interfering with the 'reg' network dhcp server even
should you accidently configure it to respond on both nics.
I can see a scenerio where that would be needed. I have the pull to try
some things at work, as long as I don't bother the IT folks for help.
There is resistance to anything linux. I could get permission to do a
thin net but I wouldn't be able to change/or have changed anything on
the company dhcp server. I would have to set it up as described. The
dhcp server for the thin clients would also be the boot server and
server that hosts the thin clients. Since that server is actually
running the programs being used, it would need to be tied to the
company network in order for the thin clients to be able to do anything
useful at work. Thus, a dhcp server on a machine that is on a lan
servered by another dhcp server. Sometimes we don't get to play in a
world where we can do things as they *should* be done.
Doug
-- 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
- Previous message: C Hamel: "Re: [SLE] Kernel Woes: Comments, Please!"
- In reply to: Jon Clausen: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Next in thread: Richard Bos: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Reply: Richard Bos: "Re: [SLE] is a dhcpserver related to 1 network card?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|