Mailing List Archive

Hi ALL


Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.


Is there a Protocol communication problem ????????

Are there alternative tftp-severs that work for the RHEL5..

It seems:

the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir

RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm)

But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm)


Client very SLOWLY displays thus:

Trying to load: pxelinux.cfg/AC1000FD
Trying to load: pxelinux.cfg/AC1000F
Trying to load: pxelinux.cfg/AC1000
Trying to load: pxelinux.cfg/AC100
Trying to load: pxelinux.cfg/AC10
Trying to load: pxelinux.cfg/AC1
Trying to load: pxelinux.cfg/AC
Trying to load: pxelinux.cfg/A
Trying to load: pxelinux.cfg/default



Message log :
####################################################################


dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b via eth1
dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1
xinetd[3173]: START: tftp pid=3238 from=172.16.0.253
in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0
in.tftpd[3239]: tftp: client does not accept options
in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0

*** AND STOPS here **

####################################################################

the "tftp: client does not accept options" doesn't seem to be a problem as it is generated on RHEL4 servers & the pxe booting still WORKS.

Enviroment details:

OS: RHEL5
KERNEL: Kernel 2.6.18-8.el5
SERVER: tftp-server-0.42-3.1.i386.rpm
NIC: INTEL 82801BA/CA # server

THanks in advance
Roger

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

RgSalisbury wrote:
>
> the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir
>
> RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm)
>
> But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm)
>

*TO THE SAME CLIENT*????

What you're describing is a common problem, but I have NEVER seen it be
a server problem.

The one thing that might be an issue is if you have a funny firewall
setup on your server.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

sorry --1st message was html

correcting now!


Hi ALL


Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far
as PXE booting is concerned.


Is there a Protocol communication problem ????????

Are there alternative tftp-severs that work for the RHEL5..

It seems:

the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir

RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with
(tftp-server-0.39-1.i386.rpm)

But RHEL5 seems to be broken..... is the TFTP SERVER broken
(tftp-server-0.42-3.1.i386.rpm)


Client very SLOWLY displays thus:

Trying to load: pxelinux.cfg/AC1000FD
Trying to load: pxelinux.cfg/AC1000F
Trying to load: pxelinux.cfg/AC1000
Trying to load: pxelinux.cfg/AC100
Trying to load: pxelinux.cfg/AC10
Trying to load: pxelinux.cfg/AC1
Trying to load: pxelinux.cfg/AC
Trying to load: pxelinux.cfg/A
Trying to load: pxelinux.cfg/default



Message log :
####################################################################


dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b
via eth1
dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1
xinetd[3173]: START: tftp pid=3238 from=172.16.0.253
in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0
in.tftpd[3239]: tftp: client does not accept options
in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0

*** AND STOPS here **

####################################################################

the "tftp: client does not accept options" doesn't seem to be a problem as
it is generated on RHEL4 servers & the pxe booting still WORKS.

Enviroment details:

OS: RHEL5
KERNEL: Kernel 2.6.18-8.el5
SERVER: tftp-server-0.42-3.1.i386.rpm
NIC: INTEL 82801BA/CA # server

THanks in advance
Roger

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

I've done RHEL 5 installs from an FC6 based system (not terribly
different all told) without any issues, so I can at least confirm that
RHEL 5 installs via pxe.

- John 'Warthog9' Hawley

On Sun, 2007-05-27 at 22:38 -0700, H. Peter Anvin wrote:
> RgSalisbury wrote:
> >
> > the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir
> >
> > RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with (tftp-server-0.39-1.i386.rpm)
> >
> > But RHEL5 seems to be broken..... is the TFTP SERVER broken (tftp-server-0.42-3.1.i386.rpm)
> >
>
> *TO THE SAME CLIENT*????
>
> What you're describing is a common problem, but I have NEVER seen it be
> a server problem.
>
> The one thing that might be an issue is if you have a funny firewall
> setup on your server.
>
> -hpa
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

> I've done RHEL 5 installs from an FC6 based system (not terribly
> different all told) without any issues, so I can at least confirm that
> RHEL 5 installs via pxe.
Thx John

from what mirrors i have looked at FC6 uses (tftp-server-0.42-3.1.i386.rpm)
the same RPM.

Could you supply pls the FC6 tftp-server version if possible.

Also I have tried atftp-sever-0.7-5.2.elf.rf.i386.rpm with no
success.....which is the latest version I have found thus far

So ......... still trying !


>
> - John 'Warthog9' Hawley
>
> On Sun, 2007-05-27 at 22:38 -0700, H. Peter Anvin wrote:
>> RgSalisbury wrote:
>> >
>> > the PXE CLIENT when booting cannot access files in the "pxelinux.cfg"
>> > dir
>> >
>> > RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with
>> > (tftp-server-0.39-1.i386.rpm)
>> >
>> > But RHEL5 seems to be broken..... is the TFTP SERVER broken
>> > (tftp-server-0.42-3.1.i386.rpm)
>> >
>>
>> *TO THE SAME CLIENT*????
>>
>> What you're describing is a common problem, but I have NEVER seen it be
>> a server problem.
>>
>> The one thing that might be an issue is if you have a funny firewall
>> setup on your server.
>>
>> -hpa
>>
>> _______________________________________________
>> SYSLINUX mailing list
>> Submissions to SYSLINUX@zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
>> Please do not send private replies to mailing list traffic.
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

RgSalisbury wrote:
>> I've done RHEL 5 installs from an FC6 based system (not terribly
>> different all told) without any issues, so I can at least confirm that
>> RHEL 5 installs via pxe.
> Thx John
>
> from what mirrors i have looked at FC6 uses (tftp-server-0.42-3.1.i386.rpm)
> the same RPM.
>
> Could you supply pls the FC6 tftp-server version if possible.
>
> Also I have tried atftp-sever-0.7-5.2.elf.rf.i386.rpm with no
> success.....which is the latest version I have found thus far
>
> So ......... still trying !
>

Could you produce a wireshark trace of the traffic?

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

> RgSalisbury wrote:
>>> I've done RHEL 5 installs from an FC6 based system (not terribly
>>> different all told) without any issues, so I can at least confirm that
>>> RHEL 5 installs via pxe.
>> Thx John
>>
>> from what mirrors i have looked at FC6 uses
>> (tftp-server-0.42-3.1.i386.rpm)
>> the same RPM.
>>
>> Could you supply pls the FC6 tftp-server version if possible.
>>
>> Also I have tried atftp-sever-0.7-5.2.elf.rf.i386.rpm with no
>> success.....which is the latest version I have found thus far
>> So ......... still trying !
>>
>
> Could you produce a wireshark trace of the traffic?


Raw tcpdump
output__________________________________________________________________________________________________________________

04:01:08.376626 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:01:6c:ca:24:7b (oui Unknown), length: 548
04:01:08.377754 arp who-has 172.16.0.253 tell 172.16.0.254
04:01:08.407747 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:09.000895 IP 172.16.0.254.bootps > 255.255.255.255.bootpc: BOOTP/DHCP,
Reply, length: 300
04:01:09.377529 arp who-has 172.16.0.253 tell 172.16.0.254
04:01:09.407501 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:10.377310 arp who-has 172.16.0.253 tell 172.16.0.254
04:01:10.407288 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:12.440658 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:01:6c:ca:24:7b (oui Unknown), length: 548
04:01:12.478988 IP 172.16.0.254.bootps > 255.255.255.255.bootpc: BOOTP/DHCP,
Reply, length: 300
04:01:12.484124 arp who-has 172.16.0.254 tell 172.16.0.253
04:01:12.484191 arp reply 172.16.0.254 is-at 00:03:47:a4:c4:4c (oui Unknown)
04:01:12.484285 IP 172.16.0.253.ah-esp-encap > 172.16.0.254.tftp: 27 RRQ
"pxelinux.0" octet tsize 0
04:01:12.640501 IP 172.16.0.254.filenet-re > 172.16.0.253.ah-esp-encap: UDP,
length 14
04:01:12.640626 IP 172.16.0.253.ah-esp-encap > 172.16.0.254.filenet-re: UDP,
length 17
04:01:12.642264 IP 172.16.0.253.acp-port > 172.16.0.254.tftp: 32 RRQ
"pxelinux.0" octet blksize 1456
04:01:12.645683 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 15
04:01:12.645834 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.715852 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.716120 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.716184 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.716424 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.716460 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.716692 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.716732 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.716974 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.717011 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.717242 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.717278 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.717510 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.717546 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.717785 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.717821 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.718060 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.718095 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 1460
04:01:12.718328 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.718358 IP 172.16.0.254.filenet-re > 172.16.0.253.acp-port: UDP,
length 48
04:01:12.718458 IP 172.16.0.253.acp-port > 172.16.0.254.filenet-re: UDP,
length 4
04:01:12.794876 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:13.406658 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:13.836594 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:14.406443 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:15.406243 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:15.919841 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:17.638741 arp who-has 172.16.0.253 tell 172.16.0.254
04:01:17.638862 arp reply 172.16.0.253 is-at 00:01:6c:ca:24:7b (oui Unknown)
04:01:18.406582 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:19.406363 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:20.086504 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:20.406152 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:23.405500 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:24.405287 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:25.405070 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:28.322983 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:28.421426 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:29.421205 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:30.420990 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:33.420337 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:34.420127 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:35.419910 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:38.420264 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:39.420048 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:40.419831 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:43.419185 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:44.418968 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:44.780889 IP 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
04:01:45.418754 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:48.419108 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:49.418891 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:50.418676 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:53.418028 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:54.417813 arp who-has 172.16.254.254 tell 172.16.0.254
04:01:55.417595 arp who-has 172.16.254.254 tell 172.16.0.254
04:02:17.697383 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:02:18.725814 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:02:20.782947 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:02:24.897673 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:02:33.126673 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:02:49.583008 IP 172.16.0.253.57090 > 0.0.0.0.tftp: 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440
04:03:22.501692 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:03:23.530232 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:03:25.587533 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:03:29.701840 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:03:37.931182 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:03:54.387581 IP 172.16.0.253.57091 > 0.0.0.0.tftp: 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440
04:04:27.305773 IP 172.16.0.253.57092 > 0.0.0.0.tftp: 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440
04:04:28.334499 IP 172.16.0.253.57092 > 0.0.0.0.tftp: 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440
04:04:30.391490 IP 172.16.0.253.57092 > 0.0.0.0.tftp: 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440
04:04:34.505964 IP 172.16.0.253.57092 > 0.0.0.0.tftp: 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440
04:04:42.734536 IP 172.16.0.253.57092 > 0.0.0.0.tftp: 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440




end of Raw tcpdump output









>
> -hpa
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

>
> Could you produce a wireshark trace of the traffic?
>
A little more with verbosity turned up & no arp messages
#############################################################################

04:20:12.958842 IP (tos 0x0, ttl 20, id 0, offset 0, flags [none], proto:
UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:01:6c:ca:24:7b (oui Unknown), length: 548, xid:0x6dca247b,
secs:4, flags: [Broadcast] (0x8000)

Client Ethernet Address: 00:01:6c:ca:24:7b (oui Unknown) [|bootp]

04:20:13.001140 IP (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto:
UDP (17), length: 328) 172.16.0.254.bootps > 255.255.255.255.bootpc:
BOOTP/DHCP, Reply, length: 300, xid:0x6dca247b, secs:4, flags: [Broadcast]
(0x8000)

Your IP: 172.16.0.253

Client Ethernet Address: 00:01:6c:ca:24:7b (oui Unknown) [|bootp]

04:20:17.022082 IP (tos 0x0, ttl 20, id 1, offset 0, flags [none], proto:
UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:01:6c:ca:24:7b (oui Unknown), length: 548, xid:0x6dca247b,
secs:4, flags: [Broadcast] (0x8000)

Client Ethernet Address: 00:01:6c:ca:24:7b (oui Unknown) [|bootp]

04:20:17.050110 IP (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto:
UDP (17), length: 328) 172.16.0.254.bootps > 255.255.255.255.bootpc:
BOOTP/DHCP, Reply, length: 300, xid:0x6dca247b, secs:4, flags: [Broadcast]
(0x8000)

Your IP: 172.16.0.253

Client Ethernet Address: 00:01:6c:ca:24:7b (oui Unknown) [|bootp]

04:20:17.055295 arp reply 172.16.0.254 is-at 00:03:47:a4:c4:4c (oui Unknown)

04:20:17.055387 IP (tos 0x0, ttl 20, id 2, offset 0, flags [none], proto:
UDP (17), length: 55) 172.16.0.253.ah-esp-encap > 172.16.0.254.tftp: [udp
sum ok] 27 RRQ "pxelinux.0" octet tsize 0

04:20:17.065350 IP (tos 0x0, ttl 64, id 17788, offset 0, flags [none],
proto: UDP (17), length: 42) 172.16.0.254.filenet-pch >
172.16.0.253.ah-esp-encap: [udp sum ok] UDP, length 14

04:20:17.065476 IP (tos 0x0, ttl 20, id 3, offset 0, flags [none], proto:
UDP (17), length: 45) 172.16.0.253.ah-esp-encap > 172.16.0.254.filenet-pch:
[udp sum ok] UDP, length 17

04:20:17.067109 IP (tos 0x0, ttl 20, id 4, offset 0, flags [none], proto:
UDP (17), length: 60) 172.16.0.253.acp-port > 172.16.0.254.tftp: [udp sum
ok] 32 RRQ "pxelinux.0" octet blksize 1456

04:20:17.070228 IP (tos 0x0, ttl 64, id 17789, offset 0, flags [none],
proto: UDP (17), length: 43) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: [udp sum ok] UDP, length 15

04:20:17.070350 IP (tos 0x0, ttl 20, id 5, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.070509 IP (tos 0x0, ttl 64, id 17790, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.070758 IP (tos 0x0, ttl 20, id 6, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.070793 IP (tos 0x0, ttl 64, id 17791, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.071027 IP (tos 0x0, ttl 20, id 7, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.071068 IP (tos 0x0, ttl 64, id 17792, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.071307 IP (tos 0x0, ttl 20, id 8, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.071352 IP (tos 0x0, ttl 64, id 17793, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.071597 IP (tos 0x0, ttl 20, id 9, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.071635 IP (tos 0x0, ttl 64, id 17794, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.071877 IP (tos 0x0, ttl 20, id 10, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.071915 IP (tos 0x0, ttl 64, id 17795, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.072146 IP (tos 0x0, ttl 20, id 11, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.072181 IP (tos 0x0, ttl 64, id 17796, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.072414 IP (tos 0x0, ttl 20, id 12, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.072451 IP (tos 0x0, ttl 64, id 17797, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.072683 IP (tos 0x0, ttl 20, id 13, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.072718 IP (tos 0x0, ttl 64, id 17798, offset 0, flags [none],
proto: UDP (17), length: 1488) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: UDP, length 1460

04:20:17.072951 IP (tos 0x0, ttl 20, id 14, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.072992 IP (tos 0x0, ttl 64, id 17799, offset 0, flags [none],
proto: UDP (17), length: 76) 172.16.0.254.filenet-pch >
172.16.0.253.acp-port: [udp sum ok] UDP, length 48

04:20:17.073087 IP (tos 0x0, ttl 20, id 15, offset 0, flags [none], proto:
UDP (17), length: 32) 172.16.0.253.acp-port > 172.16.0.254.filenet-pch: [udp
sum ok] UDP, length 4

04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:20:18.168595 IP (tos 0x0, ttl 20, id 17, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:20:20.247548 IP (tos 0x0, ttl 20, id 18, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:20:22.064029 arp reply 172.16.0.253 is-at 00:01:6c:ca:24:7b (oui Unknown)

04:20:24.404906 IP (tos 0x0, ttl 20, id 19, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:20:32.720913 IP (tos 0x0, ttl 20, id 20, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:20:49.353204 IP (tos 0x0, ttl 20, id 21, offset 0, flags [none], proto:
UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
"pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks

04:21:22.375841 IP (tos 0x0, ttl 20, id 22, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:21:23.402291 IP (tos 0x0, ttl 20, id 23, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:21:25.455215 IP (tos 0x0, ttl 20, id 24, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:21:29.560819 IP (tos 0x0, ttl 20, id 25, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:21:37.772695 IP (tos 0x0, ttl 20, id 26, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:21:54.196235 IP (tos 0x0, ttl 20, id 27, offset 0, flags [none], proto:
UDP (17), length: 79) 172.16.0.253.57090 > 0.0.0.0.tftp: [udp sum ok] 51 RRQ
"pxelinux.cfg/AC1000FD" octet tsize 0 blksize 1440

04:22:27.047176 IP (tos 0x0, ttl 20, id 28, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:22:28.073693 IP (tos 0x0, ttl 20, id 29, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:22:30.127047 IP (tos 0x0, ttl 20, id 30, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:22:34.233689 IP (tos 0x0, ttl 20, id 31, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:22:42.444399 IP (tos 0x0, ttl 20, id 32, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:22:58.872452 IP (tos 0x0, ttl 20, id 33, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57091 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/AC1000F" octet tsize 0 blksize 1440

04:23:31.721798 IP (tos 0x0, ttl 20, id 34, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:23:32.748680 IP (tos 0x0, ttl 20, id 35, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:23:34.802202 IP (tos 0x0, ttl 20, id 36, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:23:38.909096 IP (tos 0x0, ttl 20, id 37, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:23:47.120448 IP (tos 0x0, ttl 20, id 38, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:24:03.543140 IP (tos 0x0, ttl 20, id 39, offset 0, flags [none], proto:
UDP (17), length: 77) 172.16.0.253.57092 > 0.0.0.0.tftp: [udp sum ok] 49 RRQ
"pxelinux.cfg/AC1000" octet tsize 0 blksize 1440

04:24:36.393579 IP (tos 0x0, ttl 20, id 40, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:24:37.419959 IP (tos 0x0, ttl 20, id 41, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:24:39.472814 IP (tos 0x0, ttl 20, id 42, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:24:43.578596 IP (tos 0x0, ttl 20, id 43, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:24:51.789267 IP (tos 0x0, ttl 20, id 44, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:25:08.211266 IP (tos 0x0, ttl 20, id 45, offset 0, flags [none], proto:
UDP (17), length: 76) 172.16.0.253.57093 > 0.0.0.0.tftp: [udp sum ok] 48 RRQ
"pxelinux.cfg/AC100" octet tsize 0 blksize 1440

04:25:41.059953 IP (tos 0x0, ttl 20, id 46, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:25:42.086521 IP (tos 0x0, ttl 20, id 47, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:25:44.138923 IP (tos 0x0, ttl 20, id 48, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:25:48.244339 IP (tos 0x0, ttl 20, id 49, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:25:56.455838 IP (tos 0x0, ttl 20, id 50, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:26:12.883230 IP (tos 0x0, ttl 20, id 51, offset 0, flags [none], proto:
UDP (17), length: 75) 172.16.0.253.57094 > 0.0.0.0.tftp: [udp sum ok] 47 RRQ
"pxelinux.cfg/AC10" octet tsize 0 blksize 1440

04:26:45.731052 IP (tos 0x0, ttl 20, id 52, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:26:46.757801 IP (tos 0x0, ttl 20, id 53, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:26:48.810818 IP (tos 0x0, ttl 20, id 54, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:26:52.917352 IP (tos 0x0, ttl 20, id 55, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:27:01.127555 IP (tos 0x0, ttl 20, id 56, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:27:17.549875 IP (tos 0x0, ttl 20, id 57, offset 0, flags [none], proto:
UDP (17), length: 74) 172.16.0.253.57095 > 0.0.0.0.tftp: [udp sum ok] 46 RRQ
"pxelinux.cfg/AC1" octet tsize 0 blksize 1440

04:27:50.406124 IP (tos 0x0, ttl 20, id 58, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:27:51.432516 IP (tos 0x0, ttl 20, id 59, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:27:53.485388 IP (tos 0x0, ttl 20, id 60, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:27:57.590810 IP (tos 0x0, ttl 20, id 61, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:28:05.803934 IP (tos 0x0, ttl 20, id 62, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:28:22.231292 IP (tos 0x0, ttl 20, id 63, offset 0, flags [none], proto:
UDP (17), length: 73) 172.16.0.253.57096 > 0.0.0.0.tftp: [udp sum ok] 45 RRQ
"pxelinux.cfg/AC" octet tsize 0 blksize 1440

04:28:55.079564 IP (tos 0x0, ttl 20, id 64, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:28:56.106256 IP (tos 0x0, ttl 20, id 65, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:28:58.159065 IP (tos 0x0, ttl 20, id 66, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:29:02.264321 IP (tos 0x0, ttl 20, id 67, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:29:10.477658 IP (tos 0x0, ttl 20, id 68, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:29:26.900090 IP (tos 0x0, ttl 20, id 69, offset 0, flags [none], proto:
UDP (17), length: 72) 172.16.0.253.57097 > 0.0.0.0.tftp: [udp sum ok] 44 RRQ
"pxelinux.cfg/A" octet tsize 0 blksize 1440

04:29:59.747640 IP (tos 0x0, ttl 20, id 70, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:30:00.774034 IP (tos 0x0, ttl 20, id 71, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:30:02.826430 IP (tos 0x0, ttl 20, id 72, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:30:06.932012 IP (tos 0x0, ttl 20, id 73, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:30:15.143158 IP (tos 0x0, ttl 20, id 74, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:30:31.564885 IP (tos 0x0, ttl 20, id 75, offset 0, flags [none], proto:
UDP (17), length: 78) 172.16.0.253.57098 > 0.0.0.0.tftp: [udp sum ok] 50 RRQ
"pxelinux.cfg/default" octet tsize 0 blksize 1440

04:31:04.417771 IP (tos 0x0, ttl 20, id 76, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:31:05.444207 IP (tos 0x0, ttl 20, id 77, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:31:07.497600 IP (tos 0x0, ttl 20, id 78, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:31:11.603342 IP (tos 0x0, ttl 20, id 79, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:31:19.814311 IP (tos 0x0, ttl 20, id 80, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:31:36.237350 IP (tos 0x0, ttl 20, id 81, offset 0, flags [none], proto:
UDP (17), length: 63) 172.16.0.253.57099 > 0.0.0.0.tftp: [udp sum ok] 35 RRQ
"linux" octet tsize 0 blksize 1440

04:32:09.083301 IP (tos 0x0, ttl 20, id 82, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:32:10.109718 IP (tos 0x0, ttl 20, id 83, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:32:12.162594 IP (tos 0x0, ttl 20, id 84, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:32:16.268226 IP (tos 0x0, ttl 20, id 85, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:32:24.481411 IP (tos 0x0, ttl 20, id 86, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:32:40.903891 IP (tos 0x0, ttl 20, id 87, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57100 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.cbt" octet tsize 0 blksize 1440

04:33:13.750844 IP (tos 0x0, ttl 20, id 88, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:33:14.777531 IP (tos 0x0, ttl 20, id 89, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:33:16.830190 IP (tos 0x0, ttl 20, id 90, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:33:20.935928 IP (tos 0x0, ttl 20, id 91, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:33:29.149470 IP (tos 0x0, ttl 20, id 92, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:33:45.571280 IP (tos 0x0, ttl 20, id 93, offset 0, flags [none], proto:
UDP (17), length: 65) 172.16.0.253.57101 > 0.0.0.0.tftp: [udp sum ok] 37 RRQ
"linux.0" octet tsize 0 blksize 1440

04:34:18.423668 IP (tos 0x0, ttl 20, id 94, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:34:19.450166 IP (tos 0x0, ttl 20, id 95, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:34:21.503513 IP (tos 0x0, ttl 20, id 96, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:34:25.609152 IP (tos 0x0, ttl 20, id 97, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:34:33.819526 IP (tos 0x0, ttl 20, id 98, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:34:50.246136 IP (tos 0x0, ttl 20, id 99, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57102 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.com" octet tsize 0 blksize 1440

04:35:23.091374 IP (tos 0x0, ttl 20, id 100, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:35:24.117664 IP (tos 0x0, ttl 20, id 101, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:35:26.170568 IP (tos 0x0, ttl 20, id 102, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:35:30.276122 IP (tos 0x0, ttl 20, id 103, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:35:38.486455 IP (tos 0x0, ttl 20, id 104, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:35:54.908319 IP (tos 0x0, ttl 20, id 105, offset 0, flags [none], proto:
UDP (17), length: 67) 172.16.0.253.57103 > 0.0.0.0.tftp: [udp sum ok] 39 RRQ
"linux.c32" octet tsize 0 blksize 1440

04:44:59.201222 IP (tos 0x0, ttl 20, id 106, offset 0, flags [none], proto:
UDP (17), length: 59) 172.16.0.253.57104 > 0.0.0.0.tftp: [udp sum ok] 31 RRQ
"1" octet tsize 0 blksize 1440

04:45:00.242580 IP (tos 0x0, ttl 20, id 107, offset 0, flags [none], proto:
UDP (17), length: 59) 172.16.0.253.57104 > 0.0.0.0.tftp: [udp sum ok] 31 RRQ
"1" octet tsize 0 blksize 1440

04:45:02.321290 IP (tos 0x0, ttl 20, id 108, offset 0, flags [none], proto:
UDP (17), length: 59) 172.16.0.253.57104 > 0.0.0.0.tftp: [udp sum ok] 31 RRQ
"1" octet tsize 0 blksize 1440

04:45:06.478398 IP (tos 0x0, ttl 20, id 109, offset 0, flags [none], proto:
UDP (17), length: 59) 172.16.0.253.57104 > 0.0.0.0.tftp: [udp sum ok] 31 RRQ
"1" octet tsize 0 blksize 1440

04:45:14.792684 IP (tos 0x0, ttl 20, id 110, offset 0, flags [none], proto:
UDP (17), length: 59) 172.16.0.253.57104 > 0.0.0.0.tftp: [udp sum ok] 31 RRQ
"1" octet tsize 0 blksize 1440




_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

RgSalisbury wrote:
>> Could you produce a wireshark trace of the traffic?
>>
> A little more with verbosity turned up & no arp messages
> #############################################################################
>
> 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none], proto:
> UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
> "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
>

Did you set "next-server" in "dhcpd.conf"?

Seems to me that the client tries to TFTP from 0.0.0.0, after retrieving "pxelinux.0".

RHEL 5 might have a newer version "dhcpd" which no longer sets "next-server"
to "boot/dhcp server" when missing in "dhcpd.conf".

Axel

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

>
> RgSalisbury wrote:
>>> Could you produce a wireshark trace of the traffic?
>>>
>> A little more with verbosity turned up & no arp messages
>> #############################################################################
>>
>> 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none],
>> proto:
>> UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
>> "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
>>
>
> Did you set "next-server" in "dhcpd.conf"?

No & thanks for the feedback Axel!

It's been my understanding that next-server relates to the server needed
after the dhcpd server. (the tftp server)

As the tftp server is on the same machine as dhcpd (and has been the case
often before) i comment it out.

I will try with it stipulated. ---





> Seems to me that the client tries to TFTP from 0.0.0.0, after retrieving
> "pxelinux.0".
>
> RHEL 5 might have a newer version "dhcpd" which no longer sets
> "next-server"
> to "boot/dhcp server" when missing in "dhcpd.conf".
>
> Axel
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date: 5/24/2007
> 4:01 PM
>
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

RgSalisbury wrote:
>> RgSalisbury wrote:
>>>> Could you produce a wireshark trace of the traffic?
>>>>
>>> A little more with verbosity turned up & no arp messages
>>> #############################################################################
>>>
>>> 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none],
>>> proto:
>>> UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
>>> "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
>>>
>> Did you set "next-server" in "dhcpd.conf"?
>
> No & thanks for the feedback Axel!
>
> It's been my understanding that next-server relates to the server needed
> after the dhcpd server. (the tftp server)
>
> As the tftp server is on the same machine as dhcpd (and has been the case
> often before) i comment it out.

Search for "next-server" on

http://syslinux.zytor.com/archives/

or read the following thread

http://syslinux.zytor.com/archives/2007-May/thread.html#8488

and you'll see that this is a common problem/misunderstanding.

:-) Axel

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

OK

Different symptons
I have now tried on a RHEL different machine with a different nic.(Intel
ethernet pro 100)
But same client & a different client

Client messages are:

##################
PXE-T02 Only absolute filenames allowed
PXE-E3C TFTP ERROR - Access Violation
PXE-M0F: Exiting Broadcom PXE ROM.
##################
##################
PXE-T02 Only absolute filenames allowed
PXE-E3C TFTP ERROR - Access Violation
PXE-M0F: Exiting Intel PXE ROM.
##################
Added
next-server

to My minimal dhcpd.conf & looks thus:
##################
ddns-update-style interim;
ignore client-updates;
subnet 172.16.0.0 netmask 255.255.255.0 {
option routers 172.16.0.254;
option subnet-mask 255.255.255.0;
host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
filename "pxelinux.0";
allow booting;
allow bootp;
range dynamic-bootp 172.16.0.128 172.16.0.254;
default-lease-time 21600;
max-lease-time 43200;
host ns {
next-server 172.16.0.254;
hardware ethernet 00:02:B3:99:05:A0;
# 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
fixed-address 172.16.0.254;
}
}
##################


> RgSalisbury wrote:
>>> Could you produce a wireshark trace of the traffic?
>>>
>> A little more with verbosity turned up & no arp messages
>> #############################################################################
>>
>> 04:20:17.129158 IP (tos 0x0, ttl 20, id 16, offset 0, flags [none],
>> proto:
>> UDP (17), length: 91) 172.16.0.253.57089 > 0.0.0.0.tftp: 63 RRQ
>> "pxelinux.cfg/01-00-01-6c-ca-24-7b" octet tsize 0 blks
>>
>
> Did you set "next-server" in "dhcpd.conf"?
>
> Seems to me that the client tries to TFTP from 0.0.0.0, after retrieving
> "pxelinux.0".
>
> RHEL 5 might have a newer version "dhcpd" which no longer sets
> "next-server"
> to "boot/dhcp server" when missing in "dhcpd.conf".
>
> Axel
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date: 5/24/2007
> 4:01 PM
>
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

RgSalisbury wrote:
> OK
>
> Different symptons
> I have now tried on a RHEL different machine with a different nic.(Intel
> ethernet pro 100)
> But same client & a different client
>
> Client messages are:
>
> ##################
> PXE-T02 Only absolute filenames allowed
> PXE-E3C TFTP ERROR - Access Violation
> PXE-M0F: Exiting Broadcom PXE ROM.
> ##################
> ##################
> PXE-T02 Only absolute filenames allowed
> PXE-E3C TFTP ERROR - Access Violation
> PXE-M0F: Exiting Intel PXE ROM.
> ##################
> Added
> next-server
>
> to My minimal dhcpd.conf & looks thus:
> ##################
> ddns-update-style interim;
> ignore client-updates;
> subnet 172.16.0.0 netmask 255.255.255.0 {
> option routers 172.16.0.254;
> option subnet-mask 255.255.255.0;
> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
> filename "pxelinux.0";
> allow booting;
> allow bootp;
> range dynamic-bootp 172.16.0.128 172.16.0.254;
> default-lease-time 21600;
> max-lease-time 43200;
> host ns {
> next-server 172.16.0.254;
> hardware ethernet 00:02:B3:99:05:A0;
> # 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
> fixed-address 172.16.0.254;
> }
> }

fixed-address 172.16.0.254 ???

Seems that you are trying to assign the dhcp server's ip address
also to the client.

Furthermore "hardware ethernet ..." should list the CLIENT'S
MAC address and not the server's, if you want to assign
a fixed IP address to the client.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

>
>
> RgSalisbury wrote:
>> OK
>>
>> Different symptons
>> I have now tried on a RHEL different machine with a different nic.(Intel
>> ethernet pro 100)
>> But same client & a different client
>>
>> Client messages are:
>>
>> ##################
>> PXE-T02 Only absolute filenames allowed
>> PXE-E3C TFTP ERROR - Access Violation
>> PXE-M0F: Exiting Broadcom PXE ROM.
>> ##################
>> ##################
>> PXE-T02 Only absolute filenames allowed
>> PXE-E3C TFTP ERROR - Access Violation
>> PXE-M0F: Exiting Intel PXE ROM.
>> ##################
>> Added
>> next-server
>>
>> to My minimal dhcpd.conf & looks thus:
>> ##################
>> ddns-update-style interim;
>> ignore client-updates;
>> subnet 172.16.0.0 netmask 255.255.255.0 {
>> option routers 172.16.0.254;
>> option subnet-mask 255.255.255.0;
>> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address
>> 172.16.0.30;}
>> filename "pxelinux.0";
>> allow booting;
>> allow bootp;
>> range dynamic-bootp 172.16.0.128 172.16.0.254;
>> default-lease-time 21600;
>> max-lease-time 43200;
>> host ns {
>> next-server 172.16.0.254;
>> hardware ethernet 00:02:B3:99:05:A0;
>> # 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
>> fixed-address 172.16.0.254;
>> }
>> }
>
> fixed-address 172.16.0.254 ???
>
> Seems that you are trying to assign the dhcp server's ip address
> also to the client.

Client recieves fixed address of 172.16.0.30 bound to mac
"00:01:6c:ca:24:7b "of client
So that works.


> Furthermore "hardware ethernet ..." should list the CLIENT'S
> MAC address and not the server's, if you want to assign
> a fixed IP address to the client.

ditto
Client recieves fixed address of 172.16.0.30 bound to mac
"00:01:6c:ca:24:7b "of client
So that works

The DHCP server is on box with ip of 172.16.0.254 with 00:02:B3:99:05:A0
The TFTP server is on box with ip of 172.16.0.254 with ditto

Yes I tried to find info on next-server but couldn't find a search function
on the list.
So downloded the last 3 months archives uncompressed them & searched for
next-server but haven't yet found much info.
I tried the next-server set as below with the other 2 commented out .. with
no joy. so I tried (didn't make much sense) all 3, also no good.
Obvioulsy I really don't know how to set the 3 below options.
Should I put the tftp server on a different box?
Is the "next-server" simply a DNS server? if so how ........

next-server 172.16.0.254;
# hardware ethernet 00:02:B3:99:05:A0;
# fixed-address 172.16.0.254;

Thanks for your reply XL






_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Quoting RgSalisbury <rgsalisbury@exemail.com.au>:
> > RgSalisbury wrote:
> >> OK
> >>
> >> Different symptons
> >> I have now tried on a RHEL different machine with a different nic.(Intel
> >> ethernet pro 100)
> >> But same client & a different client
> >>
> >> Client messages are:
> >>
> >> ##################
> >> PXE-T02 Only absolute filenames allowed
> >> PXE-E3C TFTP ERROR - Access Violation
> >> PXE-M0F: Exiting Broadcom PXE ROM.
> >> ##################
> >> ##################
> >> PXE-T02 Only absolute filenames allowed
> >> PXE-E3C TFTP ERROR - Access Violation
> >> PXE-M0F: Exiting Intel PXE ROM.
> >> ##################
> >> Added
> >> next-server
> >>
> >> to My minimal dhcpd.conf & looks thus:
> >> ##################
> >> ddns-update-style interim;
> >> ignore client-updates;
> >> subnet 172.16.0.0 netmask 255.255.255.0 {
> >> option routers 172.16.0.254;
> >> option subnet-mask 255.255.255.0;
> >> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address
> >> 172.16.0.30;}
> >> filename "pxelinux.0";
> >> allow booting;
> >> allow bootp;
> >> range dynamic-bootp 172.16.0.128 172.16.0.254;
> >> default-lease-time 21600;
> >> max-lease-time 43200;
> >> host ns {
> >> next-server 172.16.0.254;
> >> hardware ethernet 00:02:B3:99:05:A0;
> >> # 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
> >> fixed-address 172.16.0.254;
> >> }
> >> }
> >
> > fixed-address 172.16.0.254 ???
> >
> > Seems that you are trying to assign the dhcp server's ip address
> > also to the client.
>
> Client recieves fixed address of 172.16.0.30 bound to mac
> "00:01:6c:ca:24:7b "of client
> So that works.
>
>
> > Furthermore "hardware ethernet ..." should list the CLIENT'S
> > MAC address and not the server's, if you want to assign
> > a fixed IP address to the client.
>
> ditto
> Client recieves fixed address of 172.16.0.30 bound to mac
> "00:01:6c:ca:24:7b "of client
> So that works
>
> The DHCP server is on box with ip of 172.16.0.254 with 00:02:B3:99:05:A0
> The TFTP server is on box with ip of 172.16.0.254 with ditto
>
> Yes I tried to find info on next-server but couldn't find a search function
> on the list.
> So downloded the last 3 months archives uncompressed them & searched for
> next-server but haven't yet found much info.
> I tried the next-server set as below with the other 2 commented out .. with
>
> no joy. so I tried (didn't make much sense) all 3, also no good.
> Obvioulsy I really don't know how to set the 3 below options.
> Should I put the tftp server on a different box?
> Is the "next-server" simply a DNS server? if so how ........
>
> next-server 172.16.0.254;
> # hardware ethernet 00:02:B3:99:05:A0;
> # fixed-address 172.16.0.254;
>

"next-server 172.16.0.254;" needs either to be defined for the entire
group/subnet (preferred solution) or within the "host" block of your
client!

See

http://syslinux.zytor.com/pxe.php#dhcp

for an example "dhcpd.conf" that works.

Axel



_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

OK good NEWS

It seems that the dhcpd-3.0.5-5.el5.rpm and dhcpd-3.0.3-5.el5.rpm
versions need a next-server option (even if tftp& dhcp are on the same
box )& ought to be grouped with the client directives.

As below:

This minimal dhcpd.conf file **WORKS**
###########################################
ddns-update-style interim;
ignore client-updates;
subnet 172.16.0.0 netmask 255.255.255.0 {
option routers 172.16.0.254;
option subnet-mask 255.255.255.0;
filename "/tftpboot/pxelinux.0";
allow booting;
allow bootp;
range dynamic-bootp 172.16.0.128 172.16.0.254;
default-lease-time 21600;
max-lease-time 43200;
group {
next-server 172.16.0.254;
host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
}
}
###########################################










Thankyou everone for your HELP


Roger





> Quoting RgSalisbury <rgsalisbury@exemail.com.au>:
>> > RgSalisbury wrote:
>> >> OK
>> >>
>> >> Different symptons
>> >> I have now tried on a RHEL different machine with a different
>> >> nic.(Intel
>> >> ethernet pro 100)
>> >> But same client & a different client
>> >>
>> >> Client messages are:
>> >>
>> >> ##################
>> >> PXE-T02 Only absolute filenames allowed
>> >> PXE-E3C TFTP ERROR - Access Violation
>> >> PXE-M0F: Exiting Broadcom PXE ROM.
>> >> ##################
>> >> ##################
>> >> PXE-T02 Only absolute filenames allowed
>> >> PXE-E3C TFTP ERROR - Access Violation
>> >> PXE-M0F: Exiting Intel PXE ROM.
>> >> ##################
>> >> Added
>> >> next-server
>> >>
>> >> to My minimal dhcpd.conf & looks thus:
>> >> ##################
>> >> ddns-update-style interim;
>> >> ignore client-updates;
>> >> subnet 172.16.0.0 netmask 255.255.255.0 {
>> >> option routers 172.16.0.254;
>> >> option subnet-mask 255.255.255.0;
>> >> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address
>> >> 172.16.0.30;}
>> >> filename "pxelinux.0";
>> >> allow booting;
>> >> allow bootp;
>> >> range dynamic-bootp 172.16.0.128 172.16.0.254;
>> >> default-lease-time 21600;
>> >> max-lease-time 43200;
>> >> host ns {
>> >> next-server 172.16.0.254;
>> >> hardware ethernet 00:02:B3:99:05:A0;
>> >> # 00:02:B3:99:05:A0 is MAC on the dhcpd & tftp server box
>> >> fixed-address 172.16.0.254;
>> >> }
>> >> }
>> >
>> > fixed-address 172.16.0.254 ???
>> >
>> > Seems that you are trying to assign the dhcp server's ip address
>> > also to the client.
>>
>> Client recieves fixed address of 172.16.0.30 bound to mac
>> "00:01:6c:ca:24:7b "of client
>> So that works.
>>
>>
>> > Furthermore "hardware ethernet ..." should list the CLIENT'S
>> > MAC address and not the server's, if you want to assign
>> > a fixed IP address to the client.
>>
>> ditto
>> Client recieves fixed address of 172.16.0.30 bound to mac
>> "00:01:6c:ca:24:7b "of client
>> So that works
>>
>> The DHCP server is on box with ip of 172.16.0.254 with
>> 00:02:B3:99:05:A0
>> The TFTP server is on box with ip of 172.16.0.254 with ditto
>>
>> Yes I tried to find info on next-server but couldn't find a search
>> function
>> on the list.
>> So downloded the last 3 months archives uncompressed them & searched for
>> next-server but haven't yet found much info.
>> I tried the next-server set as below with the other 2 commented out ..
>> with
>>
>> no joy. so I tried (didn't make much sense) all 3, also no good.
>> Obvioulsy I really don't know how to set the 3 below options.
>> Should I put the tftp server on a different box?
>> Is the "next-server" simply a DNS server? if so how ........
>>
>> next-server 172.16.0.254;
>> # hardware ethernet 00:02:B3:99:05:A0;
>> # fixed-address 172.16.0.254;
>>
>
> "next-server 172.16.0.254;" needs either to be defined for the entire
> group/subnet (preferred solution) or within the "host" block of your
> client!
>
> See
>
> http://syslinux.zytor.com/pxe.php#dhcp
>
> for an example "dhcpd.conf" that works.
>
> Axel
>
>
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Quoting RgSalisbury <rgsalisbury@exemail.com.au>:

> OK good NEWS
>
> It seems that the dhcpd-3.0.5-5.el5.rpm and dhcpd-3.0.3-5.el5.rpm
> versions need a next-server option (even if tftp& dhcp are on the same
> box )& ought to be grouped with the client directives.
>
> As below:
>
> This minimal dhcpd.conf file **WORKS**
> ###########################################
> ddns-update-style interim;
> ignore client-updates;
> subnet 172.16.0.0 netmask 255.255.255.0 {
> option routers 172.16.0.254;
> option subnet-mask 255.255.255.0;
> filename "/tftpboot/pxelinux.0";
> allow booting;
> allow bootp;
> range dynamic-bootp 172.16.0.128 172.16.0.254;
> default-lease-time 21600;
> max-lease-time 43200;
> group {
> next-server 172.16.0.254;
> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
> }
> }
> ###########################################

ISC changed dhcpd's default for missing "next-server" statements
from version 3.0.2 to version 3.0.3.

See: http://syslinux.zytor.com/archives/2007-May/008492.html

It's all in the books (mailing loist archives) ...

:-) Axel

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Man O Man
Answered in *SUPERB DETAIL* within the links

Thanks again Axel

cheers
Roger -)


----- Original Message -----
From: "Dyks, Axel (XL)" <xl@xlsigned.net>
To: "For discussion of SYSLINUX and tftp-hpa" <syslinux@zytor.com>
Sent: Wednesday, May 30, 2007 12:42 AM
Subject: Re: [syslinux] Has anyone any insightas towhy RedHatEnterprise
Level 5 is broken as far asPXE bootingis concerned.


> Quoting RgSalisbury <rgsalisbury@exemail.com.au>:
>
>> OK good NEWS
>>
>> It seems that the dhcpd-3.0.5-5.el5.rpm and dhcpd-3.0.3-5.el5.rpm
>> versions need a next-server option (even if tftp& dhcp are on the same
>> box )& ought to be grouped with the client directives.
>>
>> As below:
>>
>> This minimal dhcpd.conf file **WORKS**
>> ###########################################
>> ddns-update-style interim;
>> ignore client-updates;
>> subnet 172.16.0.0 netmask 255.255.255.0 {
>> option routers 172.16.0.254;
>> option subnet-mask 255.255.255.0;
>> filename "/tftpboot/pxelinux.0";
>> allow booting;
>> allow bootp;
>> range dynamic-bootp 172.16.0.128 172.16.0.254;
>> default-lease-time 21600;
>> max-lease-time 43200;
>> group {
>> next-server 172.16.0.254;
>> host abcd {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address
>> 172.16.0.30;}
>> }
>> }
>> ###########################################
>
> ISC changed dhcpd's default for missing "next-server" statements
> from version 3.0.2 to version 3.0.3.
>
> See: http://syslinux.zytor.com/archives/2007-May/008492.html
>
> It's all in the books (mailing loist archives) ...
>
> :-) Axel
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 30-05-2007 om 01:17 schreef RgSalisbury:
> Man O Man
> Answered in *SUPERB DETAIL* within the links
>
> Thanks again Axel

Axel is cool!

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.