Beruflich Dokumente
Kultur Dokumente
SLIP modifies a standard Internet datagram by appending a special SLIP END character to it,
which allows datagrams to be distinguished as separate. SLIP requires a port configuration of 8
data bits, no parity, and EIA or hardware flow control. SLIP does not provide error detection,
being reliant on other high-layer protocols for this. Over a particularly error-prone dial-up link
therefore, SLIP on its own would not be satisfactory.
A SLIP connection needs to have its IP address configuration set each time before it is
established whereas Point-to-Point Protocol (PPP) can determine it automatically once it has
started.
The Serial Line Internet Protocol (SLIP) is a mostly obsolete encapsulation of the Internet
Protocol designed to work over serial ports and modem connections. It is documented in RFC
1055. SLIP has been largely replaced by the Point-to-Point Protocol (PPP), which is better
engineered, has more features and does not require its IP address configuration to be set before
it is established.
A version of SLIP with header compression is called CSLIP (Compressed SLIP).
The Parallel Line Internet Protocol (PLIP) is very similar to SLIP, but works at higher speeds via
a parallel port.
Both SLIP and PLIP have been replaced by increasingly-common networks, including home
networking – and by other peer-to-peer connections such as USB, used to transfer files to a
second computer where a network is not necessary or available.
SLIP is a STREAMS-based computer networking facility that provides for the transmission and
reception of IP packets over serial lines. SLIP allows the use of TCP/IP networking applications
such as rlogin and telnet over serial lines. SCO SLIP is an implementation of the Serial Line
Internet Protocol (SLIP) as defined in RFC 1055 and RFC 1144.
SLIP can be used to connect one host to another via a single, physical serial line connection
between serial ports or over longer distances using a modem at each end of a telephone line. A
computer that is running SLIP over one or more serial lines and that is also connected to a
computer network (such as an Ethernet) can serve as a communication gateway between
computers on a network and computers at the far end of each serial line.
An IP datagram is passed down to SLIP, which breaks it into bytes and sends them one at a time
over the link. After the last byte of the datagram, a special byte value is sent that tells the
receiving device that the datagram has ended. This is called the SLIP END character , and has a
byte value of 192 decimal (C0 hexadecimal, 11000000 binary). And that's basically it: take the
whole datagram, send it one byte at a time, and then send the byte 192 to delimit the end of
the datagram.
A minor enhancement to this basic operation is to precede the datagram by an END character as
well. The benefit of this is that, it clearly separates the start of the datagram from anything that
preceded it. To see why this might be needed, suppose at a particular time one has only one
datagram to send, datagram #1. So, the user sends #1 and then sends the END character to
delimit it. Now, suppose there is a pause before the next datagram shows up. During that time,
there is no transmission, but if there is line noise, the other device might pick up spurious bytes
here and there. If the user later receives datagram #2 and just starts sending it, the receiving
device might think the noise bytes were part of datagram #2.
Starting datagram #2 off with an END character tells the recipient that anything received
between this END character and the previous one is a separate datagram. If that's just noise,
then this “noise datagram” is just gibberish that will be rejected at the IP layer. Meanwhile, it
doesn't corrupt the real datagram one wishes to send. If no noise occurred on the line between
datagrams, then the recipient will just see the END at the start of datagram #2 right after the
one at the end of #1 and will ignore the “null datagram” between the two.
JS 8500:
https://www.daxnetworks.com/Dax/Products/ras_asp/JS8500.asp
DXMP-801:
https://www.daxnetworks.com/Dax/Products/router_asp/dxmp801.asp
DXMP-1700:
https://www.daxnetworks.com/Dax/Products/router_asp/dxmp1700.asp
DXMP-2600E:
https://www.daxnetworks.com/Dax/Products/router_asp/dxmp2600E.asp
DXMP-2630 series:
https://www.daxnetworks.com/Dax/Products/router_asp/dxmp2630.asp
DXMP-2691/92:
https://www.daxnetworks.com/Dax/Products/router_asp/dxmp2690.asp
DXMP-3600 series:
http://www.daxnetworks.com/Dax/Products/router_asp/dxmp3600.asp
If you have been forwarded this e-mail and wish to recommend this Newsletter, please click here.
www.daxnetworks.com