aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/framerelay.txt
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
commit1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch)
tree0bba044c4ce775e45a88a51686b5d9f90697ea9d /Documentation/networking/framerelay.txt
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
Diffstat (limited to 'Documentation/networking/framerelay.txt')
-rw-r--r--Documentation/networking/framerelay.txt39
1 files changed, 39 insertions, 0 deletions
diff --git a/Documentation/networking/framerelay.txt b/Documentation/networking/framerelay.txt
new file mode 100644
index 000000000000..1a0b720440dd
--- /dev/null
+++ b/Documentation/networking/framerelay.txt
@@ -0,0 +1,39 @@
1Frame Relay (FR) support for linux is built into a two tiered system of device
2drivers. The upper layer implements RFC1490 FR specification, and uses the
3Data Link Connection Identifier (DLCI) as its hardware address. Usually these
4are assigned by your network supplier, they give you the number/numbers of
5the Virtual Connections (VC) assigned to you.
6
7Each DLCI is a point-to-point link between your machine and a remote one.
8As such, a separate device is needed to accommodate the routing. Within the
9net-tools archives is 'dlcicfg'. This program will communicate with the
10base "DLCI" device, and create new net devices named 'dlci00', 'dlci01'...
11The configuration script will ask you how many DLCIs you need, as well as
12how many DLCIs you want to assign to each Frame Relay Access Device (FRAD).
13
14The DLCI uses a number of function calls to communicate with the FRAD, all
15of which are stored in the FRAD's private data area. assoc/deassoc,
16activate/deactivate and dlci_config. The DLCI supplies a receive function
17to the FRAD to accept incoming packets.
18
19With this initial offering, only 1 FRAD driver is available. With many thanks
20to Sangoma Technologies, David Mandelstam & Gene Kozin, the S502A, S502E &
21S508 are supported. This driver is currently set up for only FR, but as
22Sangoma makes more firmware modules available, it can be updated to provide
23them as well.
24
25Configuration of the FRAD makes use of another net-tools program, 'fradcfg'.
26This program makes use of a configuration file (which dlcicfg can also read)
27to specify the types of boards to be configured as FRADs, as well as perform
28any board specific configuration. The Sangoma module of fradcfg loads the
29FR firmware into the card, sets the irq/port/memory information, and provides
30an initial configuration.
31
32Additional FRAD device drivers can be added as hardware is available.
33
34At this time, the dlcicfg and fradcfg programs have not been incorporated into
35the net-tools distribution. They can be found at ftp.invlogic.com, in
36/pub/linux. Note that with OS/2 FTPD, you end up in /pub by default, so just
37use 'cd linux'. v0.10 is for use on pre-2.0.3 and earlier, v0.15 is for
38pre-2.0.4 and later.
39