D1749@applelink.apple.com (Disini SW, Emmanuel Disini,PRT) (08/18/90)
>Hmm, I've not heard of MacTCP being able to talk to SLIP. Do have >reason to think it will? The A/UX 2.0 documentation claims that MacTCP will work over both localtalk and serial lines(SLIP), as well as Ethertalk. Obviously, from the various messages posted in response to my query, the documentation got way ahead of R&D. Now, I'm wondering if MacTCP works at all over localtalk? Joel Disini
urlichs@smurf.sub.org (Matthias Urlichs) (08/20/90)
In comp.protocols.appletalk, article <3017547@AppleLink.Apple.COM>,
D1749@applelink.apple.com (Disini SW, Emmanuel Disini,PRT) writes:
< >Hmm, I've not heard of MacTCP being able to talk to SLIP. Do have
< >reason to think it will?
<
<The A/UX 2.0 documentation claims that MacTCP will work over both localtalk and
<serial lines(SLIP), as well as Ethertalk. Obviously, from the various messages
<posted in response to my query, the documentation got way ahead of R&D. Now,
<I'm wondering if MacTCP works at all over localtalk?
<
While the current version of MacTCP is extensible, there seem to be problems
with letting it talk SLIP (I suppose that it can't deal with receiving
anything other than a whole packet at a time, or something like that?? Anyone
know exactly?) and, accoring to a posting a few weeks back, a revision is in
the works.
The A/UX version of MacTCP simply uses the kernel networking support and just
translates the MacTCP interface to the Unix world. If you have SLIP configured
into the kernel, then obviously MacTCP can talk SLIP that way.
--
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)lefty@OBELIX.TWG.COM (08/21/90)
> While the current version of MacTCP is extensible, there seem to be problems > with letting it talk SLIP (I suppose that it can't deal with receiving > anything other than a whole packet at a time, or something like that?? > Anyone know exactly?) and, accoring to a posting a few weeks back, a > revision is in the works. My understanding (John V., care to clarify this?) is that the timeout values used by MacTCP are too quick for the (relatively) extremely slow speeds at which SLIP and PPP transfer data. While MacTCP _is_ designed to accomodate a variety of link access protocols, the timer values cannot currently be scaled to allow for a wide enough range of transfer rates... |<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>| | David N. Schlesinger || "When I have nothing to say, | | The Wollongong Group || my lips are sealed; | | Internet: Lefty@twg.com || say something once, | | DoD #: 0152 || why say it again?" -- David Byrne | |<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>|
lefty@OBELIX.TWG.COM (08/21/90)
> The A/UX 2.0 documentation claims that MacTCP will work over both localtalk > and serial lines(SLIP), as well as Ethertalk. Obviously, from the various > messages posted in response to my query, the documentation got way ahead of > R&D. Now, I'm wondering if MacTCP works at all over localtalk? I _can_ verify that MacTCP works just fine over LocalTalk. We do that all the time around here, in conjunction with our MacGateWay IP forwarder. |<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>| | David N. Schlesinger || "When I have nothing to say, | | The Wollongong Group || my lips are sealed; | | Internet: Lefty@twg.com || say something once, | | DoD #: 0152 || why say it again?" -- David Byrne | |<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>|
daven@svc.portal.com (08/21/90)
In article <3017547@AppleLink.Apple.COM> D1749@applelink.apple.com (Disini SW, Emmanuel Disini,PRT) writes: >I'm wondering if MacTCP works at all over localtalk? Yup, it does. Dave -- ------------------------------------------------------------------------------- Dave Newman - Sofware Ventures | daven@svc.portal.com | AppleLink: D0025 Berkeley, CA (415) 644-3232 | AOL: MicroPhone | CIS: 76004,2161 -------------------------------------------------------------------------------
Gavin_Eadie@UM.CC.UMICH.EDU (08/21/90)
> My understanding (John V., care to clarify this?) is that the timeout values > used by MacTCP are too quick for the (relatively) extremely slow speeds at > which SLIP and PPP transfer data. This may be true for SLIP in which the initial requests for an IP address are pumped out rather fast - too fast for one frame to have been completely sent before the next is started - but it is not true for SLFP (an old MIT variant we use in the Merit network) because SLFP delivers an IP address to the Mac immediately, with no poll. We have a working SLFP LAP for MacTCP which we wrote early in the year and we have been working on a PPP implementation recently. There are some problem though. It's impossible to tell when you can hang up the phone since the Close calls to the TCP layer are not passed down to the LAP (not to mention the fact that you could get UDP data at any time without warning. I believe large packets cause problems sometimes (probably a timing issue) and there are some strange aspects to the MacTCP cdef interface that cause multiple LAPs to be highlighted simultaneously! Gavin Eadie, U of Michigan Information Systems (speaking for others). Internet: Gavin_Eadie@ummts.cc.umich.edu