Hi! akeilo cm schrieb: > Hi again Tobias, > > I guess i need a clarification on your reply; > >> But, if you remove the DHCP Proxy service, you will lose automatic > inclusion of the PXE clients and have to add each client manually. > Plus, when removing the TFTP service you have to do the pxelinux > setup manually. > > Can you please clarify this in details? When i check the otc...\root\tftp > folder while the thinclient booting i dont see any pxelinux.cfg file/folder > created or the configuration file for the macid of the thinclient.... > What sort of mechanism is in place with the OTC TFTP pxelinux configuration > generation and handling here?
Well, this is handled dynamically. If the TFTP server receives a TFTP query for the file named 01-aa-bb-cc-dd-ee-ff, it searches the OTC list of configured thin clients whether there is one with the MAC address aa:bb:cc:dd:ee:ff and if it finds it, generates a suitable config file on-the-fly and hands it to the client. > you mentioned i need to do tftp config manually, which i assumed create a > folder pxelinux.cfg and the filename that match the macid and fill in the > details of the file that matches the constants' values as per > template.txt.... No, as said before, this is done internally. Ok, just for clarification: - you power up a thin client / PXE device that was previously not configured in OTC. - the PXE times out. Why? Because the OTC server does not yet serve it because it is not a configured thin client. Now you do: - expand the "PXE clients" branch of the tree view in the manager. - look up that device in the "PXE clients" list of OTC. - right click on the device in the tree view - edit the client (sorry, here at home, I don't have an english OTC at hand... :-))) - now, the client shows up in the "Thin Clients" branch of the list view. - Restart the thin client. - Now, the server will send an extra DHCP offer telling the thin client where to boot from. > would really appreciate if you can breakdown the internal processes going on > under the tftp folder... Does the above help you? > i have removed the DHCP proxy and the DHCP server is running on Linksys DWRT Why did you remove the DHCP proxy? What is the reason? If you really want to do it without DHCP proxy, you only have to do this: - create a new thin client with the correct MAC address Then it will be served by the DHCP server. But, you will have to add the boot server and boot file "/pxelinux.0" to your DHCP server, too. > WRT54GL (linux) dnsmasq service with "dhcp-boot=pxelinux.0,,192.168.1.63" > option added to dnsmasq - where the 192.168.1.63 is the external NFS server > with two NFS shares defined (/mnt/HD_a2/root and /mnt/HD_a2/home with > contents inline with the OTC server file/folder structure. > If i use the TFTP server from OTC and use the external NFS by changing the > values from manager accordingly, i can boot the thinclients on the NFS > server and their home folder etc. works. Ouch! You are doing everything manually. Possible, but surely the toughest way to get it all to work. >From my point of view, you should have started with a separate OTC server first to watch how everything works and fits into place... :-) Ok, the TFTP server should give out the config files if the thin clients are configured. So, if you have a TC with MAC aa:bb:cc:dd:ee:ff, then try to get the file 01-aa-bb-cc-dd-ee-ff via TFTP. This should work. > The problem arise when i try to move the TFTP server, i.e. copy all the > files under ....\root\tftp folder from OTC and put on the external TFTP > server. Since there is no pxelinux.cfg file or folder, i attempted to create > these folder and file (with macid name) along with the contents that match > the template.txt. Ah, ok, that should work, too. > thinclient boots, gets the dhcp boot server, connects the externa TFTP, > retrieves pxeinux.0 and looks for pxelinux.cfg/MAC_ID_ofThinClient. Even > though i have the file in that folder, it simply doesnt read and attempts to > read alternate configuration files under pxelinux.cfg folder numerous times. The file name consists of a leading "01-" (01 stands for ethernet) and the MAC address is to be written in all lower case characters. > what sort of magic is going on under tftp folder when a new thinclient boots > up? I think you almost got it right, but just not quite, probably some kind of spelling error in the file name or the like. Just try to get the file via TFTP manually using a TFTP client. > how is the templates.txt gets involved in generating the pxeconfig? > is the pxelinux.0 compiled specifically for OTC that reads the template.txt > and parses it against OTC's ldap and create a pxeconfig file for the macid > on the fly?? I have monitored the root\tftp folder with FILEMON tool and i > didnt see a single pxeconfig file/folder being created when a thinclient > boots throught the OTC.... No, all the magic is within the TFTP server, the pxelinux.0 is pretty standard. > definitely needs some clarification here... > > looking forward to hear from you. "Hello!" :-) -- Bye, Tobias Abt levigo systems gmbh ----------- ein unternehmen der levigo gruppe Max-Eyth-Strasse 30 Telefon: 07031 / 4161-10 D-71088 Holzgerlingen Telefax: 07031 / 4161-11 Geschäftsführer: Oliver Bausch http://systems.levigo.de/ Registergericht: Stuttgart HRB 245 180 USt-ID: DE813226078 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
