Solved

Making PIX boot server on fedora8.....??

Posted on 2008-10-07
12
661 Views
Last Modified: 2013-12-15
hi,
  I want to make my fedora8 machine as a PIX boot server for network installation.To install both linux and windows also.
  I tried it with some documentations but nt able to figure it out so Step by step guide from scratch will be appreciated.

Thanks in advance,
OrLin
0
Comment
Question by:linuxgroups
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 5
12 Comments
 
LVL 4

Accepted Solution

by:
urgoll earned 500 total points
ID: 22665451
Hello,
I'm assuming you meant PXE-boot server. I have no Windows experience, but can give you the Linux recipe.

Step1:
Basic setup. Have a look at this howto:
http://www.howtoforge.com/unattended-fedora-installations-with-kickstart-and-nfs
Follow this give until section 5, but do not do section 5. This howto boots using a CD, which is not what you want, but cover the rest of Fedora's network install process called kickstart.
During the procedure, you create a kickstart configuration file. Save it as /nfs_share/f8/yourkickstartfile.cfg, it will be used later.

Step2:
PXE setup. For this, you need a TFTP server. TFTP means Trivial FTP, and is a protocol to share files over the network is a very simple way, usable by boot loaders. Fedora doesn't come with a TFTP server, but you can get one there:
ftp://ftp.silfreed.net/repo/fedora/8/i386/silfreednet/RPMS/atftp-0.7-5.fc8.i386.rpm

- Create a directory called /tftpboot and make it owned by root, with everyone allowed to read. This is where you will but the PXE boot and config files.
- Start the atftpd daemon using the provided startup script.
- If your server uses the embedded firewall, you need to open the TFTP port which is UDP/69
- Install the syslinux package from the Fedora distribution; this provides the basic PXE boot loader
- copy /usr/lib/syslinux/pxelinux.0 to /tftpboot/pxelinux.0
- copy /nfs_share/f8/images/pxeboot/initrd.img to /tftpboot/initrd.img
- copy /nfs_share/f8/images/pxeboot/vmlinuz to /tftpboot/vmlinuz
- mkdir /tftpboot/pxelinux.cfg
- create a file called /tftpboot/pxelinux.cfg/default with the content from the snippet
- Configure your DHCP server to provide the following information to booting servers:
                next-server <TFTP server IP address>;
                filename "t/pxelinux.0";

That should be it! All you need now is to turn on your target computer and tell the BIOS to boot using PXE. Then the following happens:
- the computer will use DHCP to get an IP address. It will get the next-server and filename parameters as well.
- the computer will use TFTP to retrieve the pxelinux.0 file from the 'next-server' and execute it.
- The pxelinux executable will use TFTP to retrieve its configuration file using a variety of filenames based on its MAC and IP address, and reverting to the filename default (the one we created).
- Based on that file, it will retrieve the linux kernel and initrd files, and execute the kernel.
- The kernel will initialize, use initrd to load its drivers and install software, which will retrieve the kickstart config file at the location given on the append line in the pxe config file, then use that to configure you new system.

You may also refer to Red Hat Enterprise Linux documents related to kickstarting, as it is very closwe to Fedora Core's process:
https://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-kickstart2.html
https://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html


Hope this helps.

Regards,
Christophe
DEFAULT install
# Boot automatically after 30 seconds in tenths of a second
timeout 300
label install
      kernel vmlinuz
      append initrd=initrd.img ks=nfs://yourservername/nfs_share/f8/yourkickstartfile.cfg

Open in new window

0
 

Author Comment

by:linuxgroups
ID: 22666581
thanks for reply
 the link u've given ftp://ftp.silfreed.net/repo/fedora/8/i386/silfreednet/RPMS/atftp-0.7-5.fc8.i386.rpm is not working.
0
 
LVL 4

Expert Comment

by:urgoll
ID: 22670924
Could it be that you are being a firewall that doesn't allow outgoing FTP connections ? The download link works for me.

Alternatively, you can try the following command:
# yum install tftp-server

A coworker of mine mentioned that recent Fedora included a tftp server package - unfortunately, I don't have a fedora server around to confirm.

Regards,
Christophe
0
Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

 

Author Comment

by:linuxgroups
ID: 22693032
In the firewall step after adding other ports when i apply changes i am getting this error:


/usr/sbin/lokkit --quiet -f --enabled --port=22:tcp --port=21:tcp --addmodule=nf_conntrack_ftp --port=2049:tcp --port=2049:udp --removemodule=nf_conntrack_netbios_ns --port=111:tcp --port=111:udp
 
Traceback (most recent call last):
  File "/usr/sbin/lokkit", line 128, in <module>
    ip4tables_conf.write()
  File "/usr/share/system-config-firewall/fw_iptables.py", line 87, in write
    (temp_file, temp) = tempfile.mkstemp("iptables-config")
  File "/usr/lib/python2.5/tempfile.py", line 295, in mkstemp
    dir = gettempdir()
  File "/usr/lib/python2.5/tempfile.py", line 262, in gettempdir
    tempdir = _get_default_tempdir()
  File "/usr/lib/python2.5/tempfile.py", line 209, in _get_default_tempdir
    ("No usable temporary directory found in %s" % dirlist))
IOError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/root']

Open in new window

0
 
LVL 4

Expert Comment

by:urgoll
ID: 22693631
Hmm, that seems to be an error with lokkit, the error is:

No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/root']

Can you check if your /tmp is full ?
0
 

Author Comment

by:linuxgroups
ID: 22704655
Thanks urgoll for ur reply

my firewall probem is solved automatically after reboot,i dont know how.

now i need ur little help about DHCP configuration with step by step

thanks in advance
0
 

Author Comment

by:linuxgroups
ID: 22720447
hi again,

I did all things you specified above.
i want you to have a llok at my /etc/dhcpd.conf file

info about my network:
my network range is 192.168.1.0/24 my server ip is 192.168.1.2(i.e.will be a PIX server)

clients are taking IP from this DHCP server but not working when i try to boot with LAN option

Urgoll i really appriciate you reply thanks buddy




ddns-update-style interim;
ignore client-updates;
 
#original line subnet 192.168.0.0 netmask 255.255.255.0 {
subnet 192.168.1.0 netmask 255.255.255.0 {
 
# --- default gateway
        option routers                  192.168.1.1;
        option subnet-mask              255.255.255.0;
 
        option nis-domain               "domain.org";
        option domain-name              "domain.org";
        option domain-name-servers      192.168.1.1;
 
        option time-offset              -18000; # Eastern Standard Time
#       option ntp-servers              192.168.1.1;
#       option netbios-name-servers     192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
#       option netbios-node-type 2;
 
        range dynamic-bootp 192.168.1.128 192.168.1.254;
        default-lease-time 21600;
        max-lease-time 43200;
#followin 2 lines r added by me okey??
        next-server 192.168.1.2;
        filename "t/pxelinux.0";
        # we want the nameserver to appear at a fixed address
        host ns {
                next-server marvin.redhat.com;
                hardware ethernet 12:34:56:78:AB:CD;
                fixed-address 207.175.42.254;
        }
}

Open in new window

0
 
LVL 4

Expert Comment

by:urgoll
ID: 22730418
Hello,
sorry for the lag, I was away for a few days on business.

From your dhcp.conf, one question (unrelated): what's the purpose of this block:
        host ns {
                next-server marvin.redhat.com;
                hardware ethernet 12:34:56:78:AB:CD;
                fixed-address 207.175.42.254;
        }

the fixed-address isn't part of the subnet it is nested in. Do you have any errors or warning in the server log when starting your DHCP server ?

Related to this question, are you sure about this line:
          filename "t/pxelinux.0";

The 't' preceding the pxelinux.0 filename looks like an error to me. Assuming you have this file as /tftpboot/pxelinux.0 on your server, then that may be the reason it's not working - it can't find the file as provided.

After making this change, if it still doesn't work please let me know what you see on the server monitor when doing the PXE boot.

Regards,
Christophe
0
 

Author Comment

by:linuxgroups
ID: 22732416
i have attached my new dhcpd.conf
ddns-update-style interim;
ignore client-updates;
 
allow booting;
allow bootp;
 
subnet 192.168.0.0 netmask 255.255.255.0 {
 
# --- default gateway
        option routers                  192.168.0.1;
        option subnet-mask              255.255.255.0;
 
        option nis-domain               "domain.org";
        option domain-name              "domain.org";
        option domain-name-servers      192.168.1.1;
 
        option time-offset              -18000; # Eastern Standard Time
#       option ntp-servers              192.168.1.1;
#       option netbios-name-servers     192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
#       option netbios-node-type 2;
 
 
        range dynamic-bootp 192.168.0.128 192.168.0.254;
        default-lease-time 21600;
        max-lease-time 43200;
 
#class "pxeclients"{ match if substring(options vendor-class-identifier, 0, 9)= "PXEClient";
group {
next-server 192.168.0.1;
filename "linux-install/pxelinux.0";}
 
        # we want the nameserver to appear at a fixed address
        host ns {
                next-server 192.168.0.1;
                hardware ethernet 12:34:56:78:AB:CD;
                fixed-address 207.175.42.254;
        }
}
~                                                                                                                                                            
~                                                                                                                                                            
~                                                                                                                                                            
~                                                                                                                                                            
~                                         

Open in new window

0
 
LVL 4

Expert Comment

by:urgoll
ID: 22777799
Is it working for you  ? What is the path to the file 'pxelinux.0' on your server ?

Regards,
Christophe
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The purpose of this article is to show how we can create Linux Mint virtual machine using Oracle Virtual Box. To install Linux Mint we have to download the ISO file from its website i.e. http://www.linuxmint.com. Once you open the link you will see …
The purpose of this article is to demonstrate how we can upgrade Python from version 2.7.6 to Python 2.7.10 on the Linux Mint operating system. I am using an Oracle Virtual Box where I have installed Linux Mint operating system version 17.2. Once yo…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question