From owner-freebsd-questions Sat Oct 16 21:38:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from imo14.mx.aol.com (imo14.mx.aol.com [198.81.17.4]) by hub.freebsd.org (Postfix) with ESMTP id 4A57614C14 for ; Sat, 16 Oct 1999 21:38:09 -0700 (PDT) (envelope-from ATeslik@aol.com) Received: from ATeslik@aol.com by imo14.mx.aol.com (mail_out_v23.6.) id mXYDa02561 (4543); Sun, 17 Oct 1999 00:38:03 -0400 (EDT) From: ATeslik@aol.com Message-ID: <0.29369e68.253aacaa@aol.com> Date: Sun, 17 Oct 1999 00:38:02 EDT Subject: Re: can't ping win95 machine To: zdenko@cs.uh.edu, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Windows 95 sub 26 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>have you check for irq conflicts? I checked for irq conflicts. No problems. I'm starting to think that mabye it's the pn0 driver. The card is a Linksys LNE100TXII. Now, the pn0 driver gives support for the LNE100TX, but with the LNE100TXII they added the wake on lan feature and, more importantly, started using three different chipsets on the card. The windows driver you download from their site depends on the chipset on the card. This is all according to Linksys's website. Does anyone have this card, and if so, what kind of luck are you having with it? On the other hand I'm thinking no problem because 'ifconfig -a' says: pn0: flags=8843 mtu 1500 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 87:ff:87:ff:87:ff media: autoselect (10baseT/UTP ) supported media: autoselect 100baseT4 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP lp0: flags=8810 mtu 1500 tun0: flags=8010 mtu 1500 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 I just don't know anymore. Going on four days solid of reading... Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message