From owner-freebsd-current@FreeBSD.ORG Tue Oct 14 10:10:56 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 EE79116A4C0 for ; Tue, 14 Oct 2003 10:10:56 -0700 (PDT) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5452043FCB for ; Tue, 14 Oct 2003 10:10:55 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id MUA74016; Tue, 14 Oct 2003 10:10:53 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 799C55D07; Tue, 14 Oct 2003 10:10:52 -0700 (PDT) To: Terry Lambert In-Reply-To: Message from Terry Lambert of "Tue, 14 Oct 2003 09:56:47 PDT." <3F8C2ACF.7AB166B@mindspring.com> Date: Tue, 14 Oct 2003 10:10:52 -0700 From: "Kevin Oberman" Message-Id: <20031014171052.799C55D07@ptavv.es.net> 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 17:10:57 -0000 > Date: Tue, 14 Oct 2003 09:56:47 -0700 > From: Terry Lambert > > 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"... The problem is that the Airport died. Looks like a power supply issue or a bad cap as it fails whenever it's moving lots of data and then recovers after several quite seconds. My wife's laptop link dies at the same time, so that's why I bought the Linksys. (Sorry for saying D-Link. I get them confused too often.) No. I am monitoring signal strength and it is excellent. I use a static address and gateway and they're fine, too. Both 'arp -a' and 'netstat -rnf inet' show what I would expect including the proper MAC address for the firewall and the hub. I've been using this card for about a year and a half and this problem has just shown up in the past few weeks. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634