LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 03-24-2006, 02:10 PM   #1
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613

Rep: Reputation: 69
Anyone successfully using diskless PXE?


I know some people are, I've read probably a good 20 or so "How-TO's" on the subject. However, I just can't seem to get it straight.

I think my problem lies in my dhcp.conf file, the PXE message from the client computer (the one trying to boot without a disc) says "No DHCP or proxyDHCP offers were received".

And then kicks me to the next boot device, if any.

I'm using PXELinux from http://syslinux.zytor.com/pxe.php and Gentoo, I have dhcp-3.0.3-r4 and tftp-hpa-0.40-r1. My filesystem structure for the PXE environment looks like this:
Code:
ls
bin   dev  home  mnt  proc        pxelinux.cfg  sbin  tmp  var
boot  etc  lib   opt  pxelinux.0  root          sys   usr
And inside pxelinux.cfg directory:
Code:
00-14-2A-B3-E4-1C  C0A80167  bzImage-2.6.15-gentoo-r7
And the 00-14-2A-B3-E4-1C and C0A80167 is:
Code:
DEFAULT pxelinux.cfg/bzImage-2.6.15-gentoo-r7 ip=dhcp root=/dev/nfs nfsroot=192.
168.1.25:/mnt/hdc/chroot/pxe
My network is a very small, probably very confused network as I'm just hitting on subnets, broadcasts, and things of that nature. I'll include my dhcp.conf and my ifconfig data at the end of this post. Here's my network as is:
Internet in through cable modem, hooked into a Linksys router, IP 192.168.1.1 From there it goes to other switches and computers on the LAN. The DHCP server exists on a server with 2 ethernet's. I've got the second ethernet (eth1) sitting at 192.168.1.25, and it is attached to the PXE machine I'm trying to boot via a switch (I don't have crossover cables otherwise I'd just direct connect them for this part of my process of getting the PXE working). I assume the rest of my network is inconsequential, if I'm wrong, please let me know and I'll describe the rest of it. Ok, so we have the initial router (linksys wrt54g) serving DHCP to the entire network. And now I have the DHCP server (192.168.1.25/eth1) serving DHCP to a single machine (I think, but probably not) in a range above that of the router's available DHCP IP's. The router gets 100-199, the DHCP on the server serves 200-220.

Ok, so now I am sure that you are thoroughly confused, but as promised here's my ifconfig (from the DHCP server) and dhcp.conf:

Code:
eth0      Link encap:Ethernet  HWaddr 00:02:55:B7:A4:3B  
          inet addr:192.168.1.24  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6177559 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21841034 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          Interrupt:22 

eth1      Link encap:Ethernet  HWaddr 00:02:55:B7:A4:3C  
          inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          Interrupt:23 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76532 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76532 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
Code:
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
#option domain-name "example.com";
#option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.200 192.168.1.210;
}
#subnet 192.168.1.24 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}

group {
#PXE-specific configuration directives:
next-server 192.168.1.25;
filename "/mnt/hdc/chroot/pxe/pxelinux.0";

host disklesspxe {
hardware ethernet 00:14:2A:B3:E4:1C;
}
}

ddns-update-style ad-hoc;
Any ideas are welcome, I don't even know where to begin to give you info, so feel free to ask.

Cool
 
Old 03-25-2006, 07:25 PM   #2
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware
Posts: 1,134

Rep: Reputation: 277Reputation: 277Reputation: 277
I'm using thinstation:

thinstation.sf.net

to run a thin client, diskless (well, no hd) workstation.

I originally wanted to boot using pxe, but, even though my client's nic was supposed to support pxe, I could never figure it out.

So, I boot from floppy.

I managed to setup my thinclient using a combination of the docs for LTSP (linux terminal services project), and thinstation.

I've been successful running a thinclient using both Linux and, briefly, Windows Server 2003. The setup involves configuring both dhcp and tftp.

At the risk of going on forever telling you what you may already know/have tried, or, if I'm off on a tangent, I'll end now, and if you need more assistance along these lines, let me know, and I'll continue.

Essentially, whether booting via pxe or floppy shouldn't matter, but I need you to confirm that we're on the same page.


cheers,
 
Old 03-30-2006, 04:02 AM   #3
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613

Original Poster
Rep: Reputation: 69
Thanks for the response!

I finally was able to get PXE working. My problem seemed to lie in the DHCP conf file, and I tried about a million variations from various places around the web, and finally came upon one that looked really simple, so I copied it nearly word for word (changing internal IP for my network) and it finally worked. The big change came when I stopped trying to use 1 specific bootloader (the PXELinux bootloader) and found others to try. Came across the pxegrub PXE How-To on the Gentoo-wiki.com pages, and that's when it all kind of fell in place.

Thanks again for the follow up, it's nice to know other people are doing the same thing out there

Cool
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
pxe boot "PXE-T01 file not found" ssharma_02 Linux - Networking 16 05-18-2011 04:21 PM
install SUSE on a diskless laptop through PXE ssalman SUSE / openSUSE 3 02-06-2006 09:28 AM
Diskless kermitthefrog91 Linux - Distributions 5 04-29-2005 08:50 AM
help me do pxe... Xswitch Linux - Networking 8 03-18-2005 09:48 AM
diskless ziox General 1 03-12-2005 03:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 01:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration