From owner-freebsd-current@FreeBSD.ORG Tue Oct 14 09:58:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 742F016A4B3 for ; Tue, 14 Oct 2003 09:58:50 -0700 (PDT) Received: from firecrest.mail.pas.earthlink.net (firecrest.mail.pas.earthlink.net [207.217.121.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCE3043FBD for ; Tue, 14 Oct 2003 09:58:49 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfndt.dialup.mindspring.com ([165.247.221.189] helo=mindspring.com) by firecrest.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1A9SVQ-0005fm-00; Tue, 14 Oct 2003 09:58:45 -0700 Message-ID: <3F8C2ACF.7AB166B@mindspring.com> Date: Tue, 14 Oct 2003 09:56:47 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Oberman References: <20031013162838.73FE25D07@ptavv.es.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4af0bd8f8f628f6eba3d8d9e2a2e1697ca2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: Sam Leffler cc: current@freebsd.org cc: Andre Guibert de Bruet Subject: Re: What's up with the IP stack? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 16:58:50 -0000 Kevin Oberman wrote: > When I see this I can reach some LAN hosts, but not others. I can > always seem to reach the access point. I can usually, but not always, > reach most other systems on the LAN, but not the gateway router, a > Sonic Wall firewall. I have logged onto another system and then > connected to the firewall, so it looks like the physical path is OK. > > The problem is intermittent and I have only scattered data. I've been > seeing it sice about the beginning of October. I was blaming it on > hardware, but now that I see these reports, maybe it's not. (I just > replaced my Apple Airport AP with a D-Link, so there is something to > suspect.) > > In may case things just start working again. The pause can vary from a > few seconds to about 10 minutes. netstat -rnf inet and arp -a output > both look to be fine. What about your IP address and default route? I've seen wireless cards, especially IBM ones, fail to get good signal, leaving you with a link.local address, or a valid address, but no default route. This may be your problem here. You might want to "just put the AirPort back"... -- Terry