I'm sorry. What you are saying doesn't add up to what I know happens
here.
1. When I'd dial in with EPPPD there was no file set up which the FTP &
TELNET programs could access to "know" what was going on.
2. The programs, which you say don't *really* use BOOTP, provide data
that login didn't provide.
3. The FTP & TELNET programs get the information from serverside
because that's where I got the information to finally set up my
dedicated IP address,etc.
4. When I switched over to LAN-type connection I started using the
driver for the NIC. That packet driver doesn't save anything to file,
so how could it "tell" the FTP & TELNET programs what they need to know,
the information they write to screen which isn't in any configuration
file or tmp file on my system?
And there was at least one person on the list who said he used BOOTP
routinely when he dialed in [with EPPPD ??] ... because of dynamic
assignments???
Also, if it were "fake" BOOTP that was actually handled by the existing
packet driver, why did BOOTP stop working when the *serverside* BOOTP
was disabled, yet I had no problems with any other access to the server
and beyond?
Can you understand, now, why I can't buy what you and Howard are saying?
l.d.
====
On Tue, 20 Mar 2001 18:10:55 +0100, Bernie <[EMAIL PROTECTED]> wrote:
> L.D asked Howard:
>> Are you certain about this??
> Well I don't know if Howard is certain but I am sure he's right ;-)
>>> This is not the same as BOOTP. When you use BOOTP with EPPPD (and
>>> LSPPP?), 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.
>>> In order to use real or server-side BOOTP, you have to use PPPD.
>> I use EPPPD. I also use BOOTP. I don't need to use it when I login,
>> because I have a fixed IP address and go that route.
> Correction. You can't use it with epppd when you log in, that's why you
> don't use it.
> You are using fake/simulated BOOTP wheter you like it or not ;-)
>> However when I use the Clarke University FTP and TELNET programs, they
>> don't know I have anything ... and *they* use BOOTP to connect and
>> obtain "server side" information, like DNS.
>> If, as you state, BOOTP requests are intercepted by the packet driver,
>> then could you please explain how the software manages to get the
>> information necessary to connect and do all nice things necessary like
>> send commands, transfer files, etc?
> Because you gave it that information when you started EPPPD.
> Send commands/transfer files (essentially the same thing) are NOT handeld
> by BOOTP. BOOTP is only used to get the DNS server(s), your IP, netmask,
> gateway (what did I forget?). All commands (like "get" or "put") are then
> sent as they always are.
>> Is everything on my website simulated files because I only have
>> "simulated BOOTP" ???
> Depends, you can have "simulated" files (links) if the server is running a
> UNIX-like OS but not because you use BOOTP in those programs.
>> Believe me, I don't even have a pppdrc.cfg file ... and the stand-alone
>> FTP and TELNET programs I use don't read any configuration files I might
>> have, and don't create or need any CFG files of their own.
> That's the point with simulated/fake BOOTP, they think they send a BOOTP
> request out on the Ethernet (both EPPPD and LSPPP are faking as packet
> drivers for Ethernet, wheras the driver built-in with NetTamer doesn't) but
> instead get a response from the packet driver. When I was fooling around
> with EPPPD I wondered if this could be scrapped (it isn't really needed, it
> just makes things easier) but there were too many who said no. But I
> stopped messing with EPPPD not far after anyway.
>> Maybe you're thinking about how Windows works???
> Actually I would assume that it would work in a similar way. However I do
> know that there are diffrences between LAN and modem connections in Windows
> (unlike in DOS), this actually makes your speed somewhat slower in Windows
> on a LAN - *if* you have long "round-trip times" (high ping to the server).
> BTW: Since I had to explain this on another mailinglist a few days ago I'm
> close to mentioning RTFM - or Read The Fine Source in this case ;-)
> //Bernie
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
