From owner-freebsd-isp Thu May 28 10:25:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12534 for freebsd-isp-outgoing; Thu, 28 May 1998 10:25:24 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12521 for ; Thu, 28 May 1998 10:25:14 -0700 (PDT) (envelope-from luiz@nlink.com.br) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by mirage.nlink.com.br (8.8.8/8.8.5) with SMTP id OAA08703; Thu, 28 May 1998 14:22:39 -0300 (EST) Date: Thu, 28 May 1998 14:22:39 -0300 (EST) From: Luiz de Barros To: Dennis cc: isp@FreeBSD.ORG Subject: Re: Cabling problems with etinc? In-Reply-To: <199805281523.LAA02497@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Dennis and All, What i cannot undertand is WHY this CSU works with Cisco, IBM, Cyclades Router but not with etinc. Isn't it a quite strange "Electrical problem"? I will try to get a V.35 breakout box with the Telco and see what i get. Luiz On Thu, 28 May 1998, Dennis wrote: > At 09:34 AM 5/28/98 -0300, Luiz de Barros wrote: > >Dear ALL, > > > >We purchased an Etinc 5025PQ PCI quad syncronous E1/T1/Fractional card and > >are havind a few problems putting it to work with more than 64Kbps. > >We have a 256Kbps fractional E1 link provided by the TELCO via an HDSL > >Termination Unit and a G.703 to V.35 E1 converter. > > > >We would like to make a FreeBSD router, connecting our various networks > >and holding our connection to internet. > > > >The whole setup works fine with a cisco on the other side and IBM, Cisco > >and Cyclades routers here at our ISP (Same CSU/DSU cable, connecting the > >V.35 cable with the V.35 DTE cable from the router ). Etinc keeps saying > >it is a clable problem, CSU/DSU problem, but how does it work with any > >router? > > > >I configured etinc port to PPP, HDLC, internal, external clock, changed > >ifconfig parameters according to the manual and i am not being able to put > >the link up and IP packets going from one side to the other at 256Kbps. > > > >I purchased etinc because of good recomendations here on the list but as i > >could see, the support from etinc is not as good as it should be. Did > >anybody already experienced any similar situation? Do i need to change > >etinc's cable? Does anybody know of any other card that can work in this > >situation? > > > >I have heard of many other choices of Sync cards and maybe next time i > >will use another card, that can give me support to work with more than > >64Kbps. I used to recomend etinc to my friends because of its support to > >FreeBSD, a Robust system with full support from the developers, etc but > >now i am quite disappointed with etinc's support. > > We cannot "support" an electrical problem, because we cannot do anything > for you over the phone. V.35 is V.35, we've sold thousands of cards, so what > can we do if you are using some hokey converter? > > Get (rent/borrow/whateva) a V.35 breakout box and look at the signals to make > certain you are getting clocks on both transmit and receive. When you run > hdlccfg and there is transmit clock present, the processor will begin > sending data > so you should see transmit data. Its very simple...no clock, no data. All > the board > wants is clock to send, and it will clock in any data in the presence of > receive clock. > > Dont screw around with the settings, which is why i gave up on you, because > you > dont know what they do and all you are doing is making the problem more > difficult > to debug. With a CSU you use external clock, period. > > Unfortunatly most people in this business dont understand datacomm, and > this kind > of problem requires skills on your end. If you cant do it, find someone who > can. I can't > do it on the phone. > > Dennis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message