From 05ef92ff701cf15883d015a122c6d2bbff16eda3 Mon Sep 17 00:00:00 2001 From: Marc Fonvieille Date: Wed, 31 Mar 2004 09:21:33 +0000 Subject: [PATCH] Add a new section: ATM on FreeBSD 5.X I hardly used acronym tags in that section: linguistics.arizona.edu/~hharley/PDFs/HarleyAcronyms2003.pdf is a good explanation of what is and what is not an acronym. Submitted by: harti --- .../handbook/advanced-networking/chapter.sgml | 178 ++++++++++++++++++ 1 file changed, 178 insertions(+) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 863768dbaa..6b30ee786b 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -7845,6 +7845,184 @@ gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 + + + + + Harti + Brandt + Contributed by + + + + + ATM on &os; 5.X + + + Configuring classical IP over ATM (PVCs) + + Classical IP over ATM (CLIP) is the + simplest method to use ATM with IP. It can be used with + switched connections (SVCs) and with permanent connections + (PVCs). This section describes how to setup a network based + on PVCs. + + + Fully meshed configurations + + The first method to setup a CLIP with + PVCs is to connect each machine to each other machine in the + network via a dedicated PVC. While this is simple to + configure it tends to become impractical for larger number + of machines. The example supposes that we have four + machines in the network, each connected to the ATM network + with an ATM adapter card. The first step is the planning of + the IP addresses and the ATM connections between the + machines. We use the following: + + + + + + + + Host + IP Adress + + + + + + hostA + 192.168.173.1 + + + + hostB + 192.168.173.2 + + + + hostC + 192.168.173.3 + + + + hostD + 192.168.173.4 + + + + + + To build a fully meshed net we need one ATM connection + between each pair of machines: + + + + + + + + Machines + VPI.VCI couple + + + + + + hostA - hostB + 0.100 + + + + hostA - hostC + 0.101 + + + + hostA - hostD + 0.102 + + + + hostB - hostC + 0.103 + + + + hostB - hostD + 0.104 + + + + hostC - hostD + 0.105 + + + + + + The VPI and VCI values at each end of the connection may + of course differ, but for simplicity we assume that they are + the same. Next we need to configure the ATM interfaces on + each host: + + hostA&prompt.root; ifconfig hatm0 192.168.173.1 up +hostB&prompt.root; ifconfig hatm0 192.168.173.2 up +hostC&prompt.root; ifconfig hatm0 192.168.173.3 up +hostD&prompt.root; ifconfig hatm0 192.168.173.4 up + + assuming that the ATM interface is + hatm0 on all hosts. Now the PVCs + need to configured on hostA (we assume that + they are already configured on the ATM switches, you need to + consult the manual for the switch on how to do this). + + hostA&prompt.root; atmconfig natm add 192.168.173.2 hatm0 0 100 llc/snap ubr +hostA&prompt.root; atmconfig natm add 192.168.173.3 hatm0 0 101 llc/snap ubr +hostA&prompt.root; atmconfig natm add 192.168.173.4 hatm0 0 102 llc/snap ubr + +hostB&prompt.root; atmconfig natm add 192.168.173.1 hatm0 0 100 llc/snap ubr +hostB&prompt.root; atmconfig natm add 192.168.173.3 hatm0 0 103 llc/snap ubr +hostB&prompt.root; atmconfig natm add 192.168.173.4 hatm0 0 104 llc/snap ubr + +hostC&prompt.root; atmconfig natm add 192.168.173.1 hatm0 0 101 llc/snap ubr +hostC&prompt.root; atmconfig natm add 192.168.173.2 hatm0 0 103 llc/snap ubr +hostC&prompt.root; atmconfig natm add 192.168.173.4 hatm0 0 105 llc/snap ubr + +hostD&prompt.root; atmconfig natm add 192.168.173.1 hatm0 0 102 llc/snap ubr +hostD&prompt.root; atmconfig natm add 192.168.173.2 hatm0 0 104 llc/snap ubr +hostD&prompt.root; atmconfig natm add 192.168.173.3 hatm0 0 105 llc/snap ubr + + Of course other traffic contracts than UBR can be used + given the ATM adapter supports those. In this case the name + of the traffic contract is followed by the parameters of the + traffic. Help for the &man.atmconfig.8; tool can be + obtained with: + + &prompt.root; atmconfig help natm add + + or in the &man.atmconfig.8; manual page. + + The same configuration can also be done via + /etc/rc.conf. + For hostA this would look like: + +network_interfaces="lo0 hatm0" +ifconfig_hatm0="inet 192.168.173.1 up" +natm_static_routes="hostB hostC hostD" +route_hostB="192.168.173.2 hatm0 0 100 llc/snap ubr" +route_hostC="192.168.173.3 hatm0 0 101 llc/snap ubr" +route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr" + + The current state of all CLIP routes + can be obtained with: + + hostA&prompt.root; atmconfig natm show + + +