atom feed6 messages in org.freebsd.freebsd-mobileWireless problems after upgrade to 4....
FromSent OnAttachments
Jesse SheidlowerOct 29, 2004 6:12 am 
Kevin ObermanOct 29, 2004 9:26 am 
Jesse SheidlowerOct 29, 2004 9:54 am 
Kevin ObermanOct 29, 2004 9:58 am 
Arnt GulbrandsenOct 29, 2004 10:00 am 
Jesse SheidlowerOct 29, 2004 6:43 pm 
Subject:Wireless problems after upgrade to 4.10 (fwd)
From:Kevin Oberman (ober@es.net)
Date:Oct 29, 2004 9:58:48 am
List:org.freebsd.freebsd-mobile

Date: Fri, 29 Oct 2004 12:54:29 -0400 From: Jesse Sheidlower <jes@panix.com>

On Fri, Oct 29, 2004 at 09:27:18AM -0700, Kevin Oberman wrote:

From: Jesse Sheidlower <jes@panix.com>

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?