FAI-3.2.16 and Broadcom-Ethernet/PXE/DHCP-problem with ipconfig

[Dirk Geschke]

Hi Thomas,

> The one in the tftp directory is used.

ah, thanks for clarification. 

> 
> Do you use an DHCP gateway or DHCP forwarding? There were problems
> with older versions of ipconfig in the initrd, which did not work when
> using a DHCP gateway. Search the mail archive for this.

No, there is no DHCP gateway, they are in the same subnet.

> And check if you can see the DHCP request (and answers) on your install server

That is even strange, a tcpdump shows:

[... a lot of tftp data...]
17:32:50.317394 IP 10.253.1.18.57093 > 10.253.1.17.35690: UDP, length 4
17:32:50.317400 IP 10.253.1.17.35690 > 10.253.1.18.57093: UDP, length
121
17:32:50.317477 IP 10.253.1.18.57093 > 10.253.1.17.35690: UDP, length 4
17:32:54.226209 arp who-has 10.253.1.18 tell 10.253.1.17
17:32:55.226225 arp who-has 10.253.1.18 tell 10.253.1.17
17:32:56.226243 arp who-has 10.253.1.18 tell 10.253.1.17
17:32:59.498484 IP 10.253.1.17.67 > 10.253.1.18.68: BOOTP/DHCP, Reply,
length 300
17:32:59.498644 IP 10.253.1.17.67 > 10.253.1.18.68: BOOTP/DHCP, Reply,
length 300

10.253.1.18 is the client, 10.253.1.17 is the server. For the moment
I am not sure why I can not see the request. Maybe I used the wrong
BPF rule. I will check this...

The last message is still form ipconfig mentioning that it tries
to get the IP address via DHCP RARP, then I see two kernel messages 
regarding tg3: eth0: link is up ... After this the machine hungs,
no crash, no response to a signal. All I can do is CTRL-ALT-DEL 
and reboot. So it seems not to be a kernel problem, I guess.

Best regards

Dirk

-- 
+----------------------------------------------------------------------+
| Dr. Dirk Geschke       / Plankensteinweg 61    / 85435 Erding        |
| Telefon: 08122-559448  / Mobil: 0176-96906350 / Fax: 08122-9818106   |
| dirk at geschke-online.de / dirk at lug-erding.de  / kontakt at lug-erding.de | 
+----------------------------------------------------------------------+