home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!uwm.edu!linac!att!ucbvax!TIGGER.JVNC.NET!johnson
- From: johnson@TIGGER.JVNC.NET ("Steven L. Johnson")
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: CryNwr EtherSlip & Slip8250
- Message-ID: <199211070127.AA09266@tigger.jvnc.net>
- Date: 7 Nov 92 01:27:52 GMT
- Article-I.D.: tigger.199211070127.AA09266
- References: <1992Oct29.205747.60224@cc.usu.edu>
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 29
-
- Joe D. writes:
-
- > Peter,
- > I think bootp is a moot point on SLIP. There is no MAC address for
- > the requester on a serial line and that makes life a little difficult for
- > the Bootp server to find an address in its tables.
-
- It is my understanding that in order for bootp to work on a slip
- connection the equipment terminating the SLIP link on the 'server'
- side must have some special support to map a physical port to
- an IP address and either alter the bootp request to include the
- IP address or be the bootp server itself.
-
- For example on the cisco terminal server that I connect through,
- if the request does not contain an IP address it processes it itself,
- otherwise it forwards the request out the ethernet port on the
- other side to see if any other bootp servers want to respond with
- additional information. In this case it can take two requests to
- fully configure.
-
- > At least in the Kermit code Bootp is stubbed off when SLIP is
- > active, since there is no physical layer addressing involved.
-
- Some people would find it valuable to have it left on. What's the
- harm?
-
- > Joe D.
-
- -Steve
-