ANNABLE@THORIN.HSCSA.UTEXAS.EDU (conni annable) (04/10/90)
I am trying to get a terminal server to boot using bootp and tftp through a cisco router. The server boots fine when it is on the same ethernet as the load host. It also boots fine when it is on the other ethernet but is told the IP address of the load host - it ARPs for the host, the cisco answers 'that's me' and tftp is then used for the load. The router has been told it has a helper address for ethernet 2 - which is the load host residing on ethernet 0. This helper address appears in a show config, but not in a show interface ethernet 2. I mention this because the cisco documentation shows an example of a show interface that indicates a helper address - that example is for a serial interface however. Should I be able to see the helper address with show interface? If I use debug packet-events, the cisco indicates: BOOTP: opcode 1 from host 0.0.0.0 on Ethernet2, 0 secs, 0 hops I have put my lanalyzer on that ethernet - the cisco never responds to the server. Has anyone out there done this? Can you see what I am doing wrong? conni network manager University of Texas Health Science Center at San Antonio Internet: annable@thorin.hscsa.utexas.edu BITnet: annable@uthscsa THEnet: shire::annable Ma Bell: (512) 567-2091
ww0n+@andrew.cmu.edu (Walter Lloyd Wimer III) (04/11/90)
I recently had problems with BOOTP through a cisco gateway to a PC running PC/TCP. It seemed that the cisco was ignoring BOOTP requests whose IP source address was 0.0.0.0. As soon as I set the PC's IP address to *any* non-zero address (e.g. 0.0.0.1 worked on our class B net!), the BOOTP requests made it through the cisco. (Note that I also forced the request's IP destination to be the all-ones broadcast address, 255.255.255.255.) I was running 8.0(6) at the time. I've since upgraded to 8.0(13) and the problem seems to have disappeared. Walt Wimer Networking and Communications Carnegie Mellon University