Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!ssbell!mcmi!unocss!tdavis
From: tdavis@unocss.UUCP (Thomas Davis)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Bootp and 3C501
Message-ID: <2105@unocss.UUCP>
Date: 12 Oct 89 13:26:17 GMT
References: <8910092133.AAsunic17654@sunic.sunet.se> <160@cica.cica.indiana.edu>
Organization: U. of Nebraska at Omaha
Lines: 13


    Interesting..  I've also seen the same problem with the 3c501
cards, with the packet drivers.  We are running bootp on a VMS machine
under Wollogong TCP/IP.  Now, without the packet drivers, it works.  
So it _is_ the packet driver.  Unfortunely, we don't have a sniffer
here at UNO (and we don't know anybody with one).  Oh, I also remember
now that when I was playing with it, (packet drivers and bootp), our
bootp daemon would see the packets, reply to them, but the packet drivers
would ignore them.

           Tom Davis,
           EET TA, University Of Nebraska Lincoln @ Omaha Campus