Topic: DHCP - add custom entry

[bloodshoteye]

Hi all
We have an existing SME 7.3 sever providing dhcp, which we don't want to mess with.
We are setting up a FOG imaging server on the same LAN.
The FOG install has this option (bolding is mine):

[...]
Would you like to use the FOG server for dhcp service? [Y/n]
DHCP will not be setup but you must setup your
current DHCP server to use FOG for pxe services.

On a Linux DHCP server you must set:
next-server
[...]

I had a look at /etc/e-smith/templates/etc/dhcpd.conf  - all the files in there are code, not settings, thus I'm unsure as to how to make the above entry in templates/custom.
Could someone prompt me on how to do that (exactly, please)?

[cactus]

Hi all
We have an existing SME 7.3 sever providing dhcp, which we don't want to mess with.
We are setting up a FOG imaging server on the same LAN.
The FOG install has this option (bolding is mine):
I had a look at /etc/e-smith/templates/etc/dhcpd.conf  - all the files in there are code, not settings, thus I'm unsure as to how to make the above entry in templates/custom.
Could someone prompt me on how to do that (exactly, please)?

I don't know what your exact question is but my guess is you need a hostname to resolve to the IP of your FOG server. If so you can do that by reserving a IP number using the MAC address in the server-manager under the Hostnames and addresses panel.

You do not necessarily need FOG as you can also serve images from your SME Server using this contrib: http://wiki.contribs.org/Tftp_server

[bloodshoteye]

cactus

I don't know what your exact question is but my guess is you need a hostname to resolve to the IP of your FOG server. If so you can do that by reserving a IP number using the MAC address in the server-manager under the Hostnames and addresses panel.

Of course, why didn't I think of that.

Thanks for this pointer

You do not necessarily need FOG as you can also serve images from your SME Server using this contrive: http://wiki.contribs.org/Tftp_server

I'm looking through the threads on this - very interesting. This contrib promotes a one stop shop, which can be ideal.
I've not yet read how to provide a xp image to a pxe client, though. I assume this is feasible?

[cactus]

cactusOf course, why didn't I think of that.

Thanks for this pointerI'm looking through the threads on this - very interesting. This contrib promotes a one stop shop, which can be ideal.
I've not yet read how to provide a xp image to a pxe client, though. I assume this is feasible?

I guess so there is a thinclient contrib to go with it.

[bloodshoteye]

I guess so there is a thinclient contrib to go with it.

It seems these contribs are for booting thin clients.

FOG will download an image to a pxe client, making it a free opensource Ghost replacement:
http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Background_on_FOG
I'm not punting FOG here, just looking for a bit of help in sorting out our DHCP environment.

We wish to keep the DHCP service as currently supplied by our SME server, so have disabled DHCP on the FOG server.
All I'm asking, please, is where (in templates-custom) a more experienced SME admin would place the following DHCP statement:

Code: [Select]

if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
   next-server x.x.x.x;
   filename "pxelinux.0";
 };


Simply adding a host entry to SME's host panel is insufficient, I believe, although I've done that.
The FOG wiki indicates the above addition, but they aren't aware of SME's custom templating, so cannot assist me any further.

[cactus]

The FOG wiki indicates the above addition, but they aren't aware of SME's custom templating, so cannot assist me any further.

Does the FOG wiki give you any pointers as to which configuration file to edit? Those templates together build the normal configuration files...

[bloodshoteye]

cactus, thanks for responding.

Does the FOG wiki give you any pointers as to which configuration file to edit?

All they say is the following:

Existing DHCP server
You must add the following lines to your existing DHCP server

I've hunted through the forum - there is no specific mention, but I would think they refer to the dhcpd.conf file? Of course all threads relate to "standard" Linux.

[Confucius]

From what I can make of the story is that the choice NO has the effect that FOG suggests it's running on a seperate server and therefore needs the line "next-server".
Any PXE request will be re-routed to the IP-address used with "next-server".
When you install FOG on the same server where you have the DHCP-service running you don't need to use "next-server".
The TFTP contrib is very suitable when you use FOG on the same server.

I hope this helps a little

Harro

[CharlieBrady]

The FOG wiki indicates the above addition, but they aren't aware of SME's custom templating, so cannot assist me any further.

SME's templating is just an automated text editor. If you understand what you want to change in the output (the dhcpd.conf file) then working out what to replace or add to the templates shouldn't be hard.

[electroman00]

Code: [Select]

if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
   next-server x.x.x.x;
   filename "pxelinux.0";
 };

Paste that to /etc/dhcpd.conf at the end of the file.

Restart the dhcp service

service dhcpd restart

If all is working cut it out and create a template file

pxeclient

 in

/etc/e-smith/templates-custom/etc/dhcpd.conf

dhcpd.conf is a folder in /etc/e-smith/templates-custom/etc/

create the folder & create the template file pxeclient in that folder.

restart the dhcp service.

service dhcpd restart

HTH

[electroman00]

.

[electroman00]

FOG interesting

[electroman00]

.

[CharlieBrady]

.« Last Edit: Today at 03:12:34 PM by electroman00 »

electroman, please do not try to alter history by removing what you have written in the past.

[electroman00]

electroman, please do not try to alter history by removing what you have written in the past.

10-4