From owner-freebsd-hackers Mon Dec 3 23:14: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cecov.masternet.it (cecov.masternet.it [194.184.65.7]) by hub.freebsd.org (Postfix) with ESMTP id 2A68337B416 for ; Mon, 3 Dec 2001 23:13:57 -0800 (PST) Received: from usul.scotty.masternet.it (modem02.masternet.it [194.184.65.197]) by cecov.masternet.it (8.11.6/8.11.4) with ESMTP id fB47EqL13821; Tue, 4 Dec 2001 08:14:52 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <5.1.0.14.2.20011204080555.01c0c140@194.184.65.7> X-Sender: gmarco@194.184.65.7 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 04 Dec 2001 08:09:48 +0100 To: garyj@jennejohn.org, Len Conrad , freebsd-hackers@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: token ring cards always PROMISC In-Reply-To: <200111071429.fA7ET6238747@peedub.muc.de> References: <5.1.0.14.0.20011107062520.05665790@mail.Go2France.com> <5.1.0.14.0.20011107062520.05665790@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 07/11/2001, Gary Jennejohn wrote: >On Wednesday 07 November 2001 13:29, Len Conrad wrote: > > Sorry to bother you here. No answers from -questions or > > -tokenring. > > > > We didn't turn it on, we can't get PROMISC mode off. The card > > otherwise works fine. > > > > Is it a problem to leave in that mode? > > > > ----------------- > > > > forwarded from the other lists: > > > > Hi list, > > > > When we bring up the 3137 (or 3140), it=B4s always in PROMISC > > mode. This didn=B4t occur on a 4.2R machine where we DL'ed the > > driver ourselves (rather than use the kernel driver of 4.4R or > > ourselves) and has been running +one year error free. > > > >The driver turns it on by default in the init routine. If you >don't want it then you'll have to modify the driver yourself. > >I don't know _why_ the driver does that, so modify it at your >own risk. oltr0: port 0xd000-0xd03f irq 10 at= =20 device 10.0 on pci0 oltr0: MAC address 00:00:83:2b:63:db ed0: port 0xb800-0xb81f irq 11 at=20 device 12.0 on pci0 ed0: address 00:50:ba:ee:48:38, type NE2000 (16 bit) orm0: