pxeboot not working

sathiya_rag · 12-17-2009, 08:46 AM

Hi,
am trying to install through pxeboot and not able to suceed. I have googled and tried out all possibilities and was not able to get through.

These are the things which i followed,

1. Checked tftp conf file and whether tftp is running

Code:

service tftp
{
        disable = no
        socket_type             = dgram
        protocol                = udp
        wait                    = yes
        user                    = root
        server                  = /usr/sbin/in.tftpd
        server_args             = -s /tftpboot
        per_source              = 11
        cps                     = 100 2
        flags                   = IPv4
}

Tftp running or not

chkconfig --list tftp
tftp on

2. Created a test file in tftpboot folder and in my tftp client did the following
tftp mypxeserver_ip
tftp>get test

test has been successfully downloaded

3. dhcpd conf file

Code:

deny unknown-clients;
ddns-update-style none;
allow bootp;
allow booting;
subnet 192.170.33.0 netmask 255.255.255.0 {
default-lease-time 21600;
max-lease-time 43200;
option routers 192.170.33.1;
group {
host MyClient{
hardware ethernet 00:80:42:1E:B8:AF;
fixed-address 192.170.33.7;
option root-path "/tftpboot";
filename "pxelinux.0";
}
}
}

I also restarted my dhcpd

But my client just gets struck here without booting from my server

Code:

Trying to load: pxelinux.cfg/01-00-80-42-1e-b8-af
Trying to load: pxelinux.cfg/C0AA2107
Trying to load: pxelinux.cfg/C0AA210
Trying to load: pxelinux.cfg/C0AA21
Trying to load: pxelinux.cfg/C0AA2
Trying to load: pxelinux.cfg/C0AA
Trying to load: pxelinux.cfg/C0A
Trying to load: pxelinux.cfg/C0
Trying to load: pxelinux.cfg/C
Trying to load: pxelinux.cfg/default

It takes around 3 mins for each of the above line.. But never took the default file and started installing

My /var/log/messages shows the following

Code:

Dec 17 17:33:26 localhost dhcpd: DHCPDISCOVER from 00:80:42:1e:b8:af via eth1
Dec 17 17:33:26 localhost dhcpd: DHCPOFFER on 192.170.33.7 to 00:80:42:1e:b8:af via eth1
Dec 17 17:33:28 localhost dhcpd: DHCPREQUEST for 192.170.33.7 (192.170.33.3) from 00:80:42:1e:b8:af via eth1
Dec 17 17:33:28 localhost dhcpd: DHCPACK on 192.170.33.7 to 00:80:42:1e:b8:af via eth1
Dec 17 17:33:28 localhost xinetd[2403]: START: tftp pid=22889 from=192.170.33.7
Dec 17 17:33:28 localhost in.tftpd[22890]: RRQ from 192.170.33.7 filename pxelinux.0
Dec 17 17:03:28 localhost in.tftpd[22890]: tftp: client does not accept options
Dec 17 17:33:28 localhost in.tftpd[22891]: RRQ from 192.170.33.7 filename pxelinux.0
lDec 17 17:48:29 localhost xinetd[2403]: EXIT: tftp status=0 pid=22889 duration=901(sec)

What am i missing actually which is stopping my client to boot from my server

Person_1873 · 12-17-2009, 10:40 AM

it looks somewhat to me as though your router may be interfering, when you PXE boot, the only two machines on the network should be the server and the client, it is ok to have other machines just as long as they arent running any kind of server especially not DHCP, you should also probably try removing these two lines from your DHCP config

Code:

option routers 192.170.33.1;
option root-path "/tftpboot";

if you read the error output it says the client cannot accept options

sathiya_rag · 12-18-2009, 12:34 AM

Even after removing those lines its not booting...

I saw somewhere in net BOOTREQUEST/BOOTREPLY after DHCPDISCOVER/OFRER/REQUEST/PACK... Any idea on that.....

log shows
[CODE]
Dec 18 12:24:59 localhost dhcpd: DHCPDISCOVER from 00:80:42:1e:b8:af via eth1 Dec 18 12:24:59 localhost dhcpd: DHCPOFFER on 192.170.33.7 to 00:80:42:1e:b8:af
via eth1 Dec 18 12:25:01 localhost dhcpd: DHCPREQUEST for 192.170.33.7 (192.170.33.3) fro
m 00:80:42:1e:b8:af via eth1 Dec 18 12:25:01 localhost dhcpd: DHCPACK on 192.170.33.7 to 00:80:42:1e:b8:af vi
a eth1 Dec 18 12:25:01 localhost in.tftpd[15785]: RRQ from 192.170.33.7 filename pxelin
ux.0 Dec 18 11:55:01 localhost in.tftpd[15785]: tftp: client does not accept options
Dec 18 12:25:01 localhost in.tftpd[15786]: RRQ from 192.170.33.7 filename pxelinux.0
[\CODE]

tcpdump shows
[CODE]
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
12:18:08.128164 IP 192.170.33.3.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300
12:18:10.160315 IP 192.170.33.3.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300
12:18:10.160994 arp who-has 192.170.33.3 tell 192.170.33.7
12:18:10.161027 arp reply 192.170.33.3 is-at 00:60:67:01:85:30 (oui Unknown)
12:18:10.161138 IP 192.170.33.7.ah-esp-encap > 192.170.33.3.tftp: 27 RRQ "pxelinux.0" octet tsize 0
12:18:10.163593 IP 192.170.33.3.32781 > 192.170.33.7.ah-esp-encap: UDP, length 14
12:18:10.163712 IP 192.170.33.7.ah-esp-encap > 192.170.33.3.32781: UDP, length 17
12:18:10.163905 IP 192.170.33.7.acp-port > 192.170.33.3.tftp: 32 RRQ "pxelinux.0" octet blksize 1456
12:18:10.166014 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 15
12:18:10.166130 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.166494 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.166998 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.167050 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.172759 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.172916 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.178521 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.178684 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.184281 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.184432 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.190045 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.190204 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.195809 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.195961 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.201576 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.201755 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.207337 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.207508 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 1460
12:18:10.213099 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:10.213250 IP 192.170.33.3.32781 > 192.170.33.7.acp-port: UDP, length 48
12:18:10.218851 IP 192.170.33.7.acp-port > 192.170.33.3.32781: UDP, length 4
12:18:15.162476 arp who-has 192.170.33.7 tell 192.170.33.3
12:18:15.162585 arp reply 192.170.33.7 is-at 00:80:42:1e:b8:af (oui Unknown)
[\CODE]

Person_1873 · 12-20-2009, 06:56 AM

just as a curiosity, is this pxe boot server running over wifi? if it is then you may be experiencing packet loss, i really dont know what else it could be, one thing i sorta thought look suspicious was this line

Code:

12:18:10.161138 IP 192.170.33.7.ah-esp-encap > 192.170.33.3.tftp: 27 RRQ "pxelinux.0" octet tsize 0

it tells me that the file pxelinux.0 has no data in it

vishesh · 12-20-2009, 07:52 AM

specify next-server parameter in dhcpd.conf , example

next-server <ip address of boot server>;

Thanks

Person_1873 · 01-08-2010, 10:01 AM

ah... yet another one of the annoying quirks in linux, a variable that isnt automatically set :P