On Wed, 21 Mar 2001 21:42:03 -0500, "Samuel W. Heywood" <[EMAIL PROTECTED]> wrote: > > >> 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. > > Are you absolutely certain of this? Yes. I just tried it. But you don't have to use the dynamic DNS numbers that LSPPP puts in IP-UP.BAT, although there shouldn't be any reason not to. On 21 March, 2001, you quoted > Dale Mentzer as having written a couple of days earlier as follows: > > DM > Even if you don't use LSPPP with it's dynamic DNS addressing, you can > DM > always use any other servers DNS numbers. I have used Microsoft > DM > Network DNS server numbers so I know it works. There are sites on the > DM > net that have these server numbers (they are public information) > DM > available so they are not difficult to find. > > You replied saying: > > HE > It works, but I believe it is not really proper to do this > HE > without permission. Domain registration records, including DNS, > HE > are public information for other reasons. > > Does this kind of trick work to fool your ISP only if it *does not* > support dynamic DNS addressing? It's not a trick to fool your ISP. In order to resolve domain names you need to use a domain name server. This is part of the service that an ISP provides. Either they tell you what they are or they are given during the PPP handshake. It really doesn't matter all that much, unless your software does not support dynamic DNS and your ISP doesn't tell you what they are, in which case they're pulling a trick on you by taking your money and not providing DNS service. > > 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 > > The first line of all my WATTCP.CFGs looks like this: > > include=path.cfg You can accomplish the same thing by writing the values that are in path.cfg directly into wattcp.cfg, without using include=path.cfg. > The files I use for holding the arguments used to load EPPPD are batch > files similar to the ones recently posted by Alejandro Lieber and myself. > I programmed my batch files according to the models used by John Lewis of > the VE3LGS Home Page, http://members.kingston.net/lewis Whatever method you use, you should be able to see the difference between the arguments to EPPPD and the values that go into path.cfg or wattcp.cfg after the packet driver is loaded. > Another question for you: Of the four environmental variables set by > IP-UP.BAT, one is called "peermru" and it is set equal to a number. Do you > know what this environmental variable is for, and how it may be used by the > program? All I know is that it's the MRU (maximum receive unit) on the remote side. It is almost always 1500, which means you can set your MSS up to 1460. I'm really not up on this stuff. I have MSS commented out in my wattcp.cfg and just run with the defaults. Howard E. -- DOS TCP/IP * <URL:http://www.ncf.ca/~ag221/dosppp.html>
