From owner-freebsd-questions  Sun Oct 17 10:53:35 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from donhm.calcasieu.com (tcnet02-20.austin.texas.net [209.99.40.83])
	by hub.freebsd.org (Postfix) with ESMTP id 76F5B14A1B
	for <freebsd-questions@FreeBSD.ORG>; Sun, 17 Oct 1999 10:53:29 -0700 (PDT)
	(envelope-from dread@texas.net)
Received: from donhm.calcasieu.com (localhost [127.0.0.1])
	by donhm.calcasieu.com (8.9.3/8.9.3) with ESMTP id MAA93253;
	Sun, 17 Oct 1999 12:53:23 -0500 (CDT)
	(envelope-from dread@texas.net)
Message-ID: <XFMail.991017125323.dread@texas.net>
X-Mailer: XFMail 1.3.1 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <0.29369e68.253aacaa@aol.com>
Date: Sun, 17 Oct 1999 12:53:23 -0500 (CDT)
From: Don Read <dread@texas.net>
To: ATeslik@aol.com
Subject: Re: can't ping win95 machine
Cc: freebsd-questions@FreeBSD.ORG
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 17-Oct-99 ATeslik@aol.com wrote:
>>>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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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 <half-duplex>)
>     supported media: autoselect 100baseT4 100baseTX <full-duplex> 100baseTX 
> <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 
> 10baseT/UTP
> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384    
> inet 127.0.0.1 netmask 0xff000000 
> 
> I just don't know anymore. Going on four days solid of reading...

Well, a last ditch check (for sanity):

1. got link & transmit on the card(s) ?
2.       ""      ""           hub ?
3. packets moving (netstat -bi) ?
4. machine knows where to route (netstat -nr) ?
5. resolution working (arp -a) ?

Regards,
---
Don Read                                 dread@calcasieu.com
EDP Manager                                  dread@texas.net
Calcasieu Lumber Co.                               Austin TX
-- the Y2K bug is not a problem. W2K however ...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message