On Mon, 19 Mar 2001 23:12:05 -0500, "Samuel W. Heywood" <[EMAIL PROTECTED]> wrote: > > > Exactly. LSPPP gets the DNS numbers as part of the PPP negotiation > > and writes them to IP-UP.BAT. EPPPD does not do this. > > Agreed. > > > This is not the same as BOOTP. When you use BOOTP with EPPPD (and > > LSPPP?), > > It is possible to use LSPPP in a mode similar to EPPPD, whereby you would > specify the DNS numbers in your command line parameters for LSPPP. Yes, but this only works if the ISP does not use dynamic or server assigned DNS. If they do use dynamic DNS, LSPPP puts the dynamic DNS numbers in IP-UP.BAT no matter what you specify on the command line. > With > LSPPP it is not necessary to indicate the DNS numbers if the ISP supports > dynamic DNS addressing. It is always necessary to specify the DNS numbers > when using EPPPD, regardless of whether the ISP supports dynamic DNS > addressing. Correct. > > BOOTP requests are intercepted by the packet driver and > > don't go to the server. This is why it is called fake or simulated > > BOOTP. Thus, in order to use BOOTP with EPPPD for DNS, you must put > > the DNS numbers in pppdrc.cfg (or similar) before loading EPPPD. > My question is this: Would a PPPDRC.CFG file have the same contents > as PATH.CFG? No. PPPDRC.CFG (or simular) is the file that holds the arguments used to load EPPPD. PATH.CFG (really WATTCP.CFG) is updated after it is loaded using the values that EPPPD puts in IP-UP.BAT. When you use BOOTP with EPPPD, you put DNS numbers in PPPDRC.CFG and myip=bootp in WATTCP.CFG. > > In order to use real or server-side BOOTP, you have to use PPPD. > > Is PPPD the same as EPPPD? Not quite. This whole subject of server-side vs simulated BOOTP and PPPD vs EPPPD was discussed in some detail on this list back in Jan 98 (Subject: Re: SLIP/PPP). I'm not sure if the archives go back that far, but I have saved several messages from that discussion in a file at http://www.ncf.ca/~ag221/ppp/bootp.txt. You might want to have a look at it. > I can understand the need for changing the > names of the config files in order to accomodate different programs, but I > never did understand why it was necessary in some cases to change the names > of the packet driver programs. That was only neccessary to load the packet driver with Arachne. Howard E. -- DOS TCP/IP * <URL:http://www.ncf.ca/~ag221/dosppp.html>
