From owner-freebsd-questions Sat May 19 3:12:15 2001 Delivered-To: freebsd-questions@freebsd.org Received: from newgate.miami.home (ip109-192.the-beach.net [12.43.109.192]) by hub.freebsd.org (Postfix) with ESMTP id 0A1B037B422 for ; Sat, 19 May 2001 03:11:09 -0700 (PDT) (envelope-from sam2539@the-beach.net) Received: from [10.0.0.103] (g3p1.miami.home [10.0.0.103]) by newgate.miami.home (8.11.1/8.11.1) with ESMTP id f4J99M008096 for ; Sat, 19 May 2001 05:09:47 -0400 (EDT) (envelope-from sam2539@the-beach.net) User-Agent: Microsoft-Entourage/9.0.2509 Date: Sat, 19 May 2001 06:10:37 -0400 Subject: NIC troubleshooting? From: the-beach To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD machine with 2 NICs doing the nat thing, all was working fine. One NIC died, so I replaced it with some card I just had lying around, a cheapy. Had to reconfigure all the nat, rc.conf and rc.firewall stuff because the new cheapy card is a dc type, whatever that means. The working config before the card failed was NICs de0 & de1, now it's dc0 and de0 (just in case that's important). Now the connection from the nated out workstations to the internet show a lot of packet loss pinging anywhere outside the private network. I wouldn't know what to do other than go buy another NIC and try it. Are there some cool tools to check what's wrong? thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message