[K12OSN] Searching for server (DHCP)
Sudev Barar
sudev at mantraonline.com
Sat Aug 28 02:36:37 UTC 2004
On Sat, 2004-08-28 at 06:53, Debbie Schiel wrote:
> lan card address (client)
> 00:C0:4F:7A:19:71
>
> Client Ethernet card
> 3Com Fast EtherLink XL 10/100Mb TX Ethernet NIC (3C905-TX)
For this card you do not have to use option 128 & 129. These were only for use with the older ISA bus cards. Your card should be PCI bus, so no need for these lines.
[SNIP]
> shared-network WORKSTATIONS {
> # YEAR456
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range dynamic-bootp 192.168.0.100 192.168.0.253;
> use-host-decl-names on;
> option log-servers 192.168.0.254;
> # trick from Peter Rundle <peter.rundle at au.interpath.net>
> if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
> filename "/lts/pxe/pxelinux.0";
> }
Make sure that this file is there in the path, although why would you
need PXE boot? Try going with floppy boot to dhcpd straight.
> else {
> filename "/lts/vmlinuz.ltsp";
Same comment as above. This file is normally a link file to the actual
boot file.
[SNIP]
> host ws001 {
> hardware ethernet 00:0E:A6:65:E2:29;
> fixed-address 192.168.0.1;
> filename "/tftpboot/lts/vmlinuz.ltsp";
you should be giving file name as "/lts/vmlinuz.ltsp" if this exists in
/tftpboot/lts
> option option-128 e4:45:74:68:00:00;
> option option-129 "NIC=3c509";
As explained above these two lines are not needed.
[SNIP]
> # DSCHIEL addition...
> host ws004 {
> hardware ethernet 00:C0:4F:7A:19:71;
> fixed-address 192.168.0.4;
> filename "/tftpboot/lts/boot/pxe/pxelinux.0";
Here first do a "ls -l" for your /tftpboot/lts" directory. Note down the
full name of the vmlinuz?????.ltsp file. Now substitute the string above
"/tftpboot/lts/boot/pxe/pxelinux.0" with
"/lts/vmlinuz???.ltsp" file name.
> option option-128 e4:45:74:68:00:00;
> option option-129 "NIC=3com";
Remove the above two lines.
[SNIP]
> --
> And the eth1 card
> Intel Corp e100 82801BA/BAM/CA/CAM Ethernet Controller
My recommendation first deal with one card and one client. Then add the
second card and switch to the first card.
[SNIP]
Go to www.rom-o-matic.org and download image for this card and as root
make boot floppy by command from the directory where you keep the floppy
image:
$ cat eb-5.2.5-3c90x.zdsk > /dev/fd0
I did just that and have attached the file for your card.
[SNIP]
> host ws001 {
> hardware ethernet 00:0E:A6:65:E2:29;
>
You have to also change the /path/name of boot file here.
Secondly when you are running tftp there is no need to give /tftpboot in
the path as the files are searched up this tree. In fact if you are
giving path as /tftpboot/lts/abc it will actually look for these files
in /tftpboot/tftpboot/lts/abc....which do not exist!!
Sorry for the messed up reply but hope this helps. Also below is my
listing of the /tftpboot/lts directory and you will notice that
vmlinuz.ltsp is actually a link to vmlinuz-2.4.21-ltsp-1 in the same
directory!!
--
Sudev Barar
Learning Linux
LISTING
[sudev at server sudev]$ ls -l /tftpboot/lts/
total 5040
drwxr-xr-x 3 root root 4096 Apr 2 19:54 boot
drwxr-xr-x 3 root root 4096 Apr 2 20:03 pxe
lrwxrwxrwx 1 root root 12 Apr 2 20:03
vmlinuz-2.4.18-ltsp -> vmlinuz.ltsp
lrwxrwxrwx 1 root root 12 Apr 2 20:03
vmlinuz-2.4.18-ltsp-1 -> vmlinuz.ltsp
lrwxrwxrwx 1 root root 12 Apr 2 20:03
vmlinuz-2.4.18-ltsp-lpp -> vmlinuz.ltsp
lrwxrwxrwx 1 root root 12 Apr 2 20:03
vmlinuz-2.4.18-ltsp-lpp-1 -> vmlinuz.ltsp
-rw-r--r-- 1 root root 1617920 Jul 1 2003
vmlinuz-2.4.21-ltsp-1
-rw-r--r-- 1 root root 1656832 Jul 5 2003
vmlinuz-2.4.21-ltsp-lpp-1
-rw-r--r-- 1 root root 1863168 Jan 21 2002
vmlinuz-2.4.9-1-kitchen-sink.img
lrwxrwxrwx 1 root root 21 Apr 2 20:03 vmlinuz.ltsp ->
vmlinuz-2.4.21-ltsp-1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eb-5.2.5-3c90x.zdsk
Type: application/octet-stream
Size: 16931 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/k12osn/attachments/20040828/89d0642a/attachment.obj>
More information about the K12OSN
mailing list