On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de>
wrote:> Hello,
>
> On 23.07.2014 22:46, Alexander Perlis wrote:
>> On Wed, 23 Jul 2014, Philipp Hahn wrote:
>>> [...]
>>> I tried lpxelinux.0, but it fails to resolve the gateway
>>> address via ARP:
>>> 17:25:51.399119 ARP, Request who-has 10.200.17.1 tell
>>> 10.200.17.212, length 46
>>> 17:25:51.399436 ARP, Reply 10.200.17.1 is-at
>>> 00:15:17:f2:f8:b2, length 46
>>> This is repeated until lpxelinux.0 times out.
>>
>> This sounds like the problem discussed earlier this month under the
>> title "lpxelinux.0 hangs under...". Gene has a workaround,
but he'll
>> need: "try 4.10-pre22 and report the value of flags and the first
3
>> octets of the MAC address".
>
> Copied (hopefully correctly) by hand:
>
> CLIENT MAC ADDR: 5C 26 0A 1A 21 5D GUID:
> 44454c4c-4800-1050-8034-c7c04f305031
> CLIENT IP: 10.200.17.212 MASK: 255.255.255.0 DHCP IP: 192.168.0.135
> GATEWAY IP: 10.200.17.1
>
> PXELINUX 4.10.4.10-pre22 ...
> !PXE entry point found (we hope) at 9598:0106 via plan A
> UNDI code segment at 9598 len 5260
> UNDI data segment at 8F5D len 63B0
> UNDI: baseio 7040 int 5 MTU 1500 type 1 "DIX+802.3" flags 0xdc1b
> ...
> UNDI: IRQ 5(0x0d): 8957:50fb -> 0000:8de2
OUI of 5c:26:0a and flags of 0xdc1b is sufficient.
>> (I know that won't solve your original problem, but at least it
will
>> make lpxelinux.0 more robust, and perhaps even give a workaround if
>> lpxelinux.0 then happens to bypass your original problem.)
>
> I'm glad to help.
>
> Philipp
>
> PS: <http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz> did not
work.
As expected. You have a different OUI (the first 3 octets of the MAC
address). Try everything from 6.03-pre18 and then lpxelinux.0 from
here: http://www.zytor.com/~genec/lpxelinux-6.03p18g4.tgz
--
-Gene