Mauro Carvalho Chehab | c4ea03f | 2020-05-01 16:44:28 +0200 | [diff] [blame] | 1 | .. SPDX-License-Identifier: GPL-2.0 |
| 2 | |
| 3 | ================== |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 4 | Linux X.25 Project |
Mauro Carvalho Chehab | c4ea03f | 2020-05-01 16:44:28 +0200 | [diff] [blame] | 5 | ================== |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 6 | |
| 7 | As my third year dissertation at University I have taken it upon myself to |
| 8 | write an X.25 implementation for Linux. My aim is to provide a complete X.25 |
| 9 | Packet Layer and a LAPB module to allow for "normal" X.25 to be run using |
| 10 | Linux. There are two sorts of X.25 cards available, intelligent ones that |
| 11 | implement LAPB on the card itself, and unintelligent ones that simply do |
| 12 | framing, bit-stuffing and checksumming. These both need to be handled by the |
| 13 | system. |
| 14 | |
| 15 | I therefore decided to write the implementation such that as far as the |
| 16 | Packet Layer is concerned, the link layer was being performed by a lower |
| 17 | layer of the Linux kernel and therefore it did not concern itself with |
| 18 | implementation of LAPB. Therefore the LAPB modules would be called by |
| 19 | unintelligent X.25 card drivers and not by intelligent ones, this would |
| 20 | provide a uniform device driver interface, and simplify configuration. |
| 21 | |
Xie He | 13458ff | 2020-12-08 19:33:46 -0800 | [diff] [blame] | 22 | To confuse matters a little, an 802.2 LLC implementation is also possible |
| 23 | which could allow X.25 to be run over an Ethernet (or Token Ring) and |
| 24 | conform with the JNT "Pink Book", this would have a different interface to |
| 25 | the Packet Layer but there would be no confusion since the class of device |
| 26 | being served by the LLC would be completely separate from LAPB. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 27 | |
| 28 | Just when you thought that it could not become more confusing, another |
| 29 | option appeared, XOT. This allows X.25 Packet Layer frames to operate over |
| 30 | the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the |
| 31 | format and behaviour of the protocol. If time permits this option will also |
| 32 | be actively considered. |
| 33 | |
| 34 | A linux-x25 mailing list has been created at vger.kernel.org to support the |
| 35 | development and use of Linux X.25. It is early days yet, but interested |
| 36 | parties are welcome to subscribe to it. Just send a message to |
| 37 | majordomo@vger.kernel.org with the following in the message body: |
| 38 | |
| 39 | subscribe linux-x25 |
| 40 | end |
| 41 | |
| 42 | The contents of the Subject line are ignored. |
| 43 | |
| 44 | Jonathan |
| 45 | |
| 46 | g4klx@g4klx.demon.co.uk |