From owner-freebsd-net Tue Oct 10 1:48:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from mailtoaster2.pipeline.ch (mailtoaster2.pipeline.ch [62.48.0.71]) by hub.freebsd.org (Postfix) with ESMTP id 8E3DE37B66D for ; Tue, 10 Oct 2000 01:48:30 -0700 (PDT) Received: (qmail 88537 invoked from network); 10 Oct 2000 08:49:50 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster2.pipeline.ch (qmail-ldap-1.03) with RC4-MD5 encrypted SMTP for ; 10 Oct 2000 08:49:50 -0000 Message-ID: <39E2D7F5.224188EF@telehouse.ch> Date: Tue, 10 Oct 2000 10:48:53 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: freebsd-net@freebsd.org Subject: Re: netgraph and ar0 (digi sync/570i) References: <39E1E2FB.C397B8EF@telehouse.ch> <39E28E54.7086BA0D@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > Andre Oppermann wrote: > > > > Hello guys > > > > I've got a few problems with a new FreeBSD 4.1 router test setup. > > > > Up until now I was unsing the Digi Sync/570i (V.35) with the native > > driver plus kernel sppp for ppp and/or cisco HDLC mode. No problems > > here. Works fine. > > > > To leverage the new possibilities of VPN's, protocol stacking, etc. > > I now tried to use it with netgraph. > > > > The card is still detected fine and I set up netgraph with the > > following: > > > > $ ngctl mkpeer sync_ar0: cisco rawdata downstream > > $ ngctl mkpeer sync_ar0:rawdata iface inet inet > > > > OK, now the ng0 interface appears in ifconfig -a and can be configured: > > > > $ ifconfig ng0 62.48.31.181 62.48.31.182 netmask 255.255.255.252 > > > > This brings up the interface but leads to an error message like the > > following: > > > > ar0 Receive error, chan 0, stat a4, msci st3 3, rxhind 25, cda40fa > > eda > > > > Has anybody got a hint what might be going wrong here or has got it > > working? Remember, without netgraph is works fine. > > We have never had an AR card to test the netgraph code with. > The netgraph code was done "in theory", but is waiting at the > ("well that's all the hard work done" stage, for someone with a card > to show up..) > Basically it is the same code as in the Sr driver and a prorpretary > card at Whistle. Ah, ok. > I will be out of touch for a day or two but if you would like to help me > get it going > send me some email and we can see what we can do.. Please help me getting this working. I just get used to netgraph but I really like it. > The fact that you have it running in the old format shows that all the > information > needed is there.. I just need to figure out what I've missed out.. I was browsing through the code today and, well, it looks like it is easy to miss something there. > > A few more questions and observations: > > > > 1. With netgraph the ifconfig output shows 'NOARP', without it does > > not. > > > 2. With netgraph the ifconfig output shows 'SIMPLEX', without it does > > not. This is clearly wrong, leased lines are duplex. > > With netgraph, the ar device should not HAVE a ifconfig entry.. > if it doesm that that is coding problem straight away.. Well, with netgraph it does not have an ifconfig entry directly but the ng0 node which shows this behaviour. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message