WLAN issue

[_]

The router supports DHCP perfectly fine and there is no MAC address
filtering or blocking or anything of that sort. I know this for a fact since
I administer it. There are several hosts connected to it. These are cable or
WLAN connections based on Windows or Apple machines and there has never been
an issue. I am aware that my NIC can't get the IP-Address. Why this is so
puzzles me, for I have already tried all the other alternatives
I know.

These are:

1. /etc/rc.d/netif start.
2. wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf
3. dhclient wi0

and they don't work either. My kernel even crashed a few times when I ran
the netif script.




On Sun, Jul 3, 2011 at 7:21 PM, Robert Bonomi <bonomi at mail.r-bonomi.com>wrote:

>
> > Date: Sun, 3 Jul 2011 18:03:35 +0200
> > To: freebsd-questions at freebsd.org
> > Subject: WLAN issue
> >
> > Hi List,
> >
> > I can't get my WLAN (WPA) to work and I am somewhat at a loss, as to what
> > else to try...
> >
> >
> > The /etc/rc.conf portion looks like this:
> >
> > ifconfig_wi0="WPA DHCP"
> >
> >
> > My /etc/wpa_supplicant.conf looks like this:
> >
> > network={
> >   ssid="my_ssid"
> >   psk="my_psk"
> > }
> >
> > The above should be fine in terms of how it is set up.
> >
> >
> > Invoking ifconfig on the interface tells me that it is connected,
> however,
> > there's still no internet connection.
> >
> > # ifconfig wi0
> > wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >    ether 00:02:2d:0f:4f:99
> >    inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> >    media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps)
> >    status: associated
> >    ssid WLAN-5C7E88 channel 11 (2462 Mhz 11b) bssid 88:25:2c:5c:7e:38
> >    stationname "FreeBSD WaveLAN/IEEE node"
> >    authmode WPA1+WPA2/802.11i privacy MIXED deftxkey UNDEF bmiss 7
> >    scanvalid 60 roaming MANUAL
> >
> >
> > My OS is FreeBSD 7.0.
> >
> >
> > Any support is greatly appreciated.
>
> The 'problem' is obvious -- you don't have an IP address.
>
> _Why_ that is the case is not so obvious.  <wry grin>
>
> _I_ have always run the DHCP client manually -- can't give you the
> exeuctable
> name off the top of my head, and don't have easy access to the machine to
> look it up.  There is undobtedly a 'better' way -- e.g., to run it
> 'automagically' when the wifi connection goes 'associated' -- but I don't
> know what it is.   doing it manually has sufficied for my needs. <wry grin>
>
>
>
>
>
>