From owner-freebsd-net@FreeBSD.ORG Tue Jun 29 12:19:31 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3298616A4CE for ; Tue, 29 Jun 2004 12:19:31 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C23D43D5A for ; Tue, 29 Jun 2004 12:19:30 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) i5TCJQj125444; Tue, 29 Jun 2004 14:19:27 +0200 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) i5TCJQD112516; Tue, 29 Jun 2004 14:19:26 +0200 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id i5TCJQV10366; Tue, 29 Jun 2004 14:19:26 +0200 (MET DST) Date: Tue, 29 Jun 2004 15:30:53 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Donatas_G./LRTC@lrtc.net In-Reply-To: Message-ID: <20040629151941.S16097@beagle.kn.op.dlr.de> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-net@freebsd.org Subject: Re: problems in NATM0 and NG0 interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 12:19:31 -0000 On Tue, 29 Jun 2004 Donatas_G./LRTC@lrtc.net wrote: > we have HE155 Series ForeRunner adapters used with intel rack systems. > hatm0 driver is not supported by harp, so in order to use atm interfaces, > we've decided to configure hetgraph interfaces (ng) on FreeBsd 5.2.1 You CAN use hatm with harp. Just list your interfaces in the natm_interfaces variable in /etc/rc.conf. For example: natm_interfaces="hatm0 hatm1" will load the if_harp driver (that is the glue between the NgATM drivers and harp, and it will issue an ifconfig up for both hatm0 and hatm1. You'll then find physical HARP interfaces with the same names. > interfaces are needed to split common internet flow to the national and > world flows. Also different interfaces are needed to support different > types of clients. I can't parse this. Do you mean you need several virtual interfaces on top of a physical interface? > We've tried to attach iface type ng nodes (inet or atm hooks) to hatm0, but > no atm parametres was possible to set to ng interfaces. > can anyone tell a short way in crating different ng atm interfaces? Generally this is done with the atmconfig tool (see natmip(4) and the natm sub-command of atmconfig(8)). It is also possible to put virtual interfaces on top of single ATM PVCs, although there is no single configuration tool for this yet: you just connect your interface NG node to any hook of the ATM node (use any name except the four fixed in ng_atm(4)). Then you issue an cpcsinit command to the ng_atm node to initialize the PVC. This goes something like this: ngctl connect hatm0: iface: foo link (given that the hook 'link' of the node 'iface:' is the lower end of the virtual interface). ngctl msg hatm0: cpcsinit '{aal=5 vci=77 name="foo"} you can also specify traffic parameters. See ng_atm(4). ng_eiface might be a candidate node type for the virtual interface although I didn't try this. harti