From owner-freebsd-atm Mon Apr 26 23: 1:33 1999 Delivered-To: freebsd-atm@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 61DD914DEB for ; Mon, 26 Apr 1999 23:01:30 -0700 (PDT) (envelope-from ggm@azure.dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id QAA10625 for ; Tue, 27 Apr 1999 16:01:29 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id QAA09673 for freebsd-atm@freebsd.org; Tue, 27 Apr 1999 16:01:28 +1000 (EST) Date: Tue, 27 Apr 1999 16:01:28 +1000 (EST) From: George Michaelson Message-Id: <199904270601.QAA09673@azure.dstc.edu.au> To: freebsd-atm@freebsd.org Subject: help getting back-to-back PCA200E working Sender: owner-freebsd-atm@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just got subscribed to the list, and in the last 2 weeks also have just got two Fore PCA200E cards compiled into my FreeBSD-3.1 kernels. wired 'em up back-to-back with a crossover fibre patchlead. I can bring each up to a point, but I can't seem to get SIGPVC and subsequent atm commands to bring up a PVC with any kind of upper payload to do IP. anybody got a canned instance of how to make this work? If its too painful to do this, and I'm better off using SPANs or some other signalling, as long as it works over a PVC tunnelled through my provider, I'm cool. I do need to be able to do RFC compliant IP-over-ATM with a GDC switch as well as tie two distant LANS together, so I'm kinda hoping this is as simple as it should be :-) cheers, and sorry for an annoyingly dumb request. -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-atm" in the body of the message