AW: arp timeout from ROM, not from floppy

["Burkhard Greeb" <bg@grove.de>]

Hi,

 

seems to be a problem of the "gw=" entry in bootptab. The client is able to optain its ip since the router is configured for forwarding bootp requests, but there is obviously no gateway-ip provided in the bootp-reply so that the client doesn't know how to contact the TFTP-server which lies beyond the router

 

mit freundlichem Gruß

Burkhard Greeb

  |N |O |C |
--|--|--|--|-------------
  |          GROVE
  Network Operation Center

http://www.grove.de             Tel. +49 2773-8167-0
http://www.iag-net.de           Fax  +49 2773-8167-20

-----Ursprüngliche Nachricht-----
Von: owner-netboot Im Auftrag von Vollmar, Juergen, G44
Gesendet: Freitag, 9. Juni 2000 13:03
An: 'netboot@baghira.han.de'
Betreff: arp timeout from ROM, not from floppy

Hello,

 

im trying to boot my clients across a router from a FreeBSD box.

 

When booting within the same c-class (no router between bootp-server and client) everything works fine,

from disk and from EPROM, when booting from floopy booting works also across the router.

 

When i write the SAME image as on the disk to an EPROM an try to boot from EPROM with bootp-server in a different subnet

, the client recieves the configuration from bootp (local IP, Server IP. filename) correctly, after that the client reports

 

TFTP: ARP Timeout

 

As said before, the same image always works fine when booted from disk, it also works when booted from EPROM within the same subnet.

Any suggestions what could be the problem?

 

Thanks

 

Juergen