From owner-freebsd-questions@FreeBSD.ORG Fri Jan 20 20:13:50 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4428F16A41F for ; Fri, 20 Jan 2006 20:13:50 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id C066143D45 for ; Fri, 20 Jan 2006 20:13:49 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from [172.26.2.238] ([172.26.2.238]) by mail.scls.lib.wi.us (8.12.9p2/8.12.9) with ESMTP id k0KKDhR4089766; Fri, 20 Jan 2006 14:13:43 -0600 (CST) (envelope-from nalists@scls.lib.wi.us) Message-ID: <43D14477.8010803@scls.lib.wi.us> Date: Fri, 20 Jan 2006 14:13:43 -0600 From: Greg Barniskis User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derek Ragona References: <6.0.0.22.2.20060120123154.025c07c0@mail.computinginnovations.com> <3782a16465b4e0bec305f4b151acc8fe@lanoticia.com> <6.0.0.22.2.20060120133722.025b9850@mail.computinginnovations.com> In-Reply-To: <6.0.0.22.2.20060120133722.025b9850@mail.computinginnovations.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?=22Alvaro_J=2E_Gurdi=E1n=22?= , FreeBSD-Questions Questions Subject: Re: cannot ping anything X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 20:13:50 -0000 Derek Ragona wrote: > See if you can ping your own interface. You should be able to ping it > on both the loop back 127.0.0.1 and the 192.168.1.128 address. Well, he said he'd tried the loopback, but it's worth double checking of course. A finger fumble and a resulting false negative can lead to hours of useless troubleshooting. Fun for some, pain for most! The OP wrote: >>>> The output of netstat and ifconfig aboe are from today. I began >>>> having this problem yesterday, and left the box on over night. >>>> Yesterday's output was different in that the BSD box had a different >>>> IP address, 192.168.1.122. That is fine I understand that the box >>>> is communicating with the router and negotiating leases when they >>>> expire. However, why has the gateway to 192.168.1.1 changed from >>>> link#1 to the MAC address of my router. I am certain that if I >>>> restart the computer that same gateway will revert to link#1. If I'm not mistaken (warning: lately I have been mistaken more than is usual ;) you're going to get the link#1 indicator prior to your box having had any reason to arp for the router, meaning "generally, that IP address should be somewhere in that direction". You'll see the MAC address after the box has tried and succeeded with an arp request, meaning "that IP address is precisely right there". That the indicator changes to a MAC address is a sure sign of basic NIC functionality as well as cabling that transmits and receives OK, at least some of the time. >>>> I was previously using this HD in another machine to test IPF, with NAT also, and it worked peerfectly there. The fact that you can use arp and DHCP but not ping smells like there is leftover ipf/nat configuration or related kernel/module issues that are preventing appropriate packet flow. Ensuring that such features are disabled is the only thing I can suggest short of reinstalling, which I am fairly confident would solve the problem. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348