From owner-freebsd-hackers Wed Sep 8 23:15:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from genesis.setjmp.net (genesis.setjmp.net [208.13.245.195]) by hub.freebsd.org (Postfix) with ESMTP id 0F5B91517D; Wed, 8 Sep 1999 23:15:09 -0700 (PDT) (envelope-from eric@setjmp.com) Received: from Apophis (eric@[10.0.0.193]) by genesis.setjmp.net (8.9.3/8.9.3) with SMTP id CAA24944; Thu, 9 Sep 1999 02:14:46 -0400 (EDT) (envelope-from eric@setjmp.com) Message-ID: <00ab01befa8a$44cba460$c100000a@cfpower.com> From: "Eric A. Griff" To: , , Subject: Sangoma Wanpipe Date: Thu, 9 Sep 1999 02:12:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Sort of off topic, though thought it might bring about some positive response and ideas here... I've successfully avoided a Cisco solution (though not the ADC kentrox one =( ) recently with the Sangoma Wanpipe using FreeBSD 3.2-STABLE (cvsupped last week). Time permitting, I intend to put together an article about this and submitting it to a few places.. This could make FreeBSD look better in the view of the coder that isn't core member material, though capable when needed. Being a little rusty on basic kernel tweaking, it took me about 2 hours total to come to the conclusion that /usr/include/sys/file.h changed the parameters changed slightly in file->filops->fo_read, and that I needed to add a fourth parameter, O_RDONLY, to get it working again =) Could probably have been done in 2 minutes by someone that regularly has there head deep in the FreeBSD kernel sources =) At the same time, sangoma is short on programmers, and hasn't someone to devote to FreeBSD/linux.. The linux community has helped them... Dave MandelSomething (Sales, not the other dave in sales =) at sangoma expressed interest in FreeBSD side help. For more info on there products, see www.sangoma.com. The particular card I used was the S508. Had to still use a ADC kentrox CSU/DSU since the network was splitting 2 channels data(128k), 18 voice, and 4 unused at this time. If it was full data use of the T1, for another $330, would have had a built in CSU/DSU (for a total of $880 or so, plus the cost to build the PC). I don't think it would take to much to match the tools they have for NT, on FreeBSD. Further, I think picoBSD could be used to make a better troubleshooting program on a disk that might help better help debug issues between external CSU/DSU, and the wanpipe. I am going to give them the updated code later today, and talk about if it could be included in the FreeBSD distrib.. CORE: Could this be added by someone b4 3.3 if they agree? Would probably lead to a little more coverage on there home page as well.. They aren't a bad company, and the Wanpipe ptpipe driver worked pretty good, along with the card =).. The main changes are sys/i386/isa/ptpipe.[ch], and an entry in sys/i386/conf/files.i386, and of course a line in the KERNEL CONFIG file. FreeBSD - making routers out of PC's =) Eric A. Griff setjmp Software (315) 734-1668 Extension 205 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message