Description of Problem:
DHCP packets sent by Cisco VOIP phones cause pxe server on the same network to
crash when listening on dhcp port.
Additional information will be attached...
Created attachment 61184 [details]
Strace of crashing pxe server
Created attachment 61185 [details]
Cisco documentation on dhcp used by voip phone.
Someone with one of these phones will need to do the testing & fixing.
Created attachment 62426 [details]
PXE testing doc
This bug is listed incorrectly. It is not a Cisco issue. The issue was
discovered using an Avaya VoIP phone. However it is not a phone issue, it is a
pxelinux issue. We have done some more testing of this issue in our lab and
determined that the problem arises when the host running the pxe daemon
receives is on the same subnet as the ip phone and the dhcp server. you can use
this link to download a utility that exactly mimics the Avaya IP Phone boot
We have another doc that we have created on this issue that will explain our
While this is indeed not a phone issue, this is also not a PXELinux issue.
The issue is with the PXE Daemon. PXELinux is not even being used at the time
when the problem happens. The PXE Daemon is seg-faulting when it doesn't
understand the PXE Packets.
BootTest is what I'm looking for, except for the fact that it is a Windows program (and won't
run under wine for want of iphlpapi.dll). If someone wants to write a tiny UNIX program to
do the equivalent, that'd be much more useful.
Created attachment 65466 [details]
Required DLL, put in \windows\system32
Also apparently needed is MPRAPI.DLL
Can someone test this under wine to let us know if this is possible to get
working, and ideally if the BootTest will indeed be sufficient to reproduce the
crash of the pxeserver?
Errata probably necessary, *sigh*
The errata is in the queue, I'll pretend I don't have to do anything more on this issue.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.