L.D wrote:
> 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.
I never said there was any file with the information.
> 2. The programs, which you say don't *really* use BOOTP, provide data
> that login didn't provide.
The programs (FTP and TelNet) use BOOTP correct.
> 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.
No, they asked the packet driver (but they didn't know this, they thought
they sent a BOOTP request).
> 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?
That's another story, but first let me correct one thing that you seem to
concentrate on. I am NOT talking about reading a file the programs send
the data (BOOTP request) as normal and then EPPPD sees what it is that
it's going to send and answer without asking the server. You know the data
sent to the packet drivers isn't sent in files they are sent by interupts.
On the other hand in a LAN a server (known as a DHCP and/or BOOTP
server) answers on BOOTP requests. This can be set up to just give you the
next available IP, or to give you a specific one (based on your MAC
address).
> 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???
Since I'm not sure which mail (and person) you are refering to it's a bit
hard to answer. However if you use BOOTP (and EPPPD) you dial in as
normally and then ask EPPPD what the settings are (with a BOOTP request,
thereby making existent programs work). The diffrent programs (Arachne for
instance) then sends a BOOTP request to get the values but the packet
driver (IF this is a modem connection) answers.
> 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?
I thought you were using a LAN connection? If so then *you* are using
BOOTP, however EPPPD uses "emulated/fake" BOOTP since it answers instead
of a server (it isn't the server).
//Bernie
http://bernie.arachne.cz/
