802.11 vap support and ndis
Weongyo Jeong
weongyo.jeong at gmail.com
Fri Jul 11 02:24:29 UTC 2008
On Thu, Jul 10, 2008 at 08:04:47PM +0200, Matteo Riondato wrote:
> Hi folks,
> I just upgraded one of my amd64 boxes from HEAD as of around March to
> HEAD as of this morning CEST and my ndis(4) card no longer works
> although I modified rc.conf as suggested (added wlans_ndis0="wlan0"
> and changed ifconfig_ndis0 to ifconfig_wlan0).
>
> The card doesn't seem to associate, or, better said, the wlan0
> interface doesn't seem to associate, because the ndis0 interface says
> it is associated: (output copied by hand)
> #ifconfig ndis0
> ndis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
> ether 00:0c:41:xx:xx:xx
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
> status: associated
> #ifconfig wlan0
> wlan0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
> ether 00:0c:41:xx:xx:xx
> inet6 fe80::20:xxxx:xxxx:xxxx%wlan0 prefixlen 64 scopeid 0x8
> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> status: no carrier
> ssid ambassador channel 1 (2412 Mhz 11g)
> country US authmode open privacy ON deftxkey 1 wepkey 1:104-bit
> txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 protmode CTS
> bintval 0
>
> My wireless lan is on channel 6, so I though there could be problems
> with scanning, but..
> #ifconfig wlan0 channel 6
> doesn't print any error message but the output of ifconfig wlan0 is the
> same, with channel 1.
>
> Any hints?
Can you try to turn on debug level of if_ndis(4) then re-associate to
your AP? Please show me the output.
# kldload if_ndis
# sysctl debug.ndis=1
regards,
Weongyo Jeong
More information about the freebsd-current
mailing list