"Samuel W. Heywood" <[EMAIL PROTECTED]> wrote:
>
>On Mon, 22 May 2000 03:33:19 -0400 (EDT), Thomas Mueller wrote:
>>
>>> Real BOOTP is run on the server. To see if your server is using
>>> it, use PPPD and tcpinfo. In most cases, it will fail.
>>
>> I suppose most ISPs would be stumped if asked whether they had real
>> BOOTP.
>
>Very interesting info here. Could someone please expand on this point
>and please post an example of how to do this? What is tcpinfo?
This subject was discussed in some detail on this list back in Jan 98.
I'm not sure if the archives go back that far, but I have saved a few
messages from that discussion and put them in a file at:
http://www.ncf.ca/~ag221/bootp.txt.
You can find tcpinfo.exe along with other individual programs from
the 1994 version of the Wattcp apps.zip and Erick Engelke's readme,
"Waterloo TCP Installation Notes" at:
http://mvmpc9.ciw.uni-karlsruhe.de/d:/public/tcp_ip/wattcp/apps/
>Also, please explain what is meant by "real BOOTP", as opposed to psuedo
>BOOTP or simulated BOOTP, or whatever other "non-real" kinds as may
>exist. Please excuse me if my questions may seem ignorant or stupid.
>I confess that I am very lacking in knowledge as to how BOOTP is supposed
>to work. The only thing I think I know about BOOTP is that it is one of
>several kinds of various processes by which an IP number may be
>dynamically assigned.
The way I understand it, with "real" BOOTP, BOOTP requests from the
application are answered directly by the server. On the other hand,
EPPPD intercepts and answers these requests, thus performing "fake"
or simulated BOOTP. As long as you're using EPPPD, "real" BOOTP does
not come into play at all, and it doesn't matter whether or not your
ISP is running BOOTP.
Howard Eisenberger
Ottawa, Canada
--
DOS TCP/IP * <URL:http://www.ncf.ca/~ag221/dosppp.html>
