From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 29 16:58:07 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96FBE16A4CE for ; Fri, 29 Oct 2004 16:58:07 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77CF843D1D for ; Fri, 29 Oct 2004 16:58:07 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP id IBA74465; Fri, 29 Oct 2004 09:58:07 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id F3B0D5D09; Fri, 29 Oct 2004 09:58:06 -0700 (PDT) To: Jesse Sheidlower In-reply-to: Your message of "Fri, 29 Oct 2004 12:54:29 EDT." <20041029165428.GA25837@panix.com> Date: Fri, 29 Oct 2004 09:58:06 -0700 From: "Kevin Oberman" Message-Id: <20041029165806.F3B0D5D09@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Wireless problems after upgrade to 4.10 (fwd) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 16:58:07 -0000 > Date: Fri, 29 Oct 2004 12:54:29 -0400 > From: Jesse Sheidlower > > On Fri, Oct 29, 2004 at 09:27:18AM -0700, Kevin Oberman wrote: > > > From: Jesse Sheidlower > > > > > > I'm running FreeBSD on an IBM ThinkPad X23. For wireless access, I've > > > been using an Orinoco Gold 802.11b card that's been working fine for > > > two years or so. > > > > > > I just got around to upgrading from 4.9 to 4.10, and in the process > > > something seems to have gotten screwed up with my wireless networking. > > > I've made buildworld and made kernel, but not installworld or > > > mergemaster yet. > > [...] > > > > When I run dhclient, I get an IP address from my Linksys > > > router, but am unable to reach anything outside. I can > > > successfully ping the router, but trying to hit any outside > > > address, by name or IP, just hangs indefinitely. My usual > > > array of troubleshooting tips--killing the dhclient process, > > > deleting the dhclient.leases file, flushing the routing > > > table--has no effect. > > [...] > > > The fact that DHCP get an address and that you can ping the gateway > > indicates that the card is working. Sounds like you might not have a > > correct default route. > > > > Do you see a reasonable response to 'netstat -rnf inet'? > > Yes, I do--looks perfectly normal. > > I have since brought the computer into my office, where I was > instantly able to hop on to an open access point that seems to > be in the neighborhood. This suggests that the problem must be > with my home router/AP. I don't know why this would be, as > it's been running fine for years, has the most basic > configuration, and is working with several other computers. But > I'm not sure what else to think about. I have no idea what AP you are using, but, if it's got a firewall, that my be unhappy with something. Does the AP log anything? -- 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