Re: [gentoo-user] MADWIFI driver...
Hi Steve, * Steve <[EMAIL PROTECTED]>, Saturday, April 2, 2005, 6:21:18 PM: > I realised that the madwifi-driver package is masked and that this > indicates that I may experience problems, but I suspect I'm more > problems than others - considering that loads of people appear to have > the madwifi drivers working with other distributions. I've hunted on the > web for definitive information about the madwifi-driver and while I can > find a fair bit of information I can't find a specific gentoo sample > configuration against which I can compare mine - nor can I find people > reporting the same fault. There is the madwifi FAQ http://www.mattfoster.clara.co.uk/madwifi-faq.htm the madwifi-homepage http://madwifi.sf.net the madwifi mailinglist http://sourceforge.net/mail/?group_id=82936 and the madwifi IRC-channel irc://irc.freenode.net/#madwifi > So far I've used emerge to merge the madwifi-driver > (madwifi-driver-0.1_pre20050224) which went without a glitch. This version is fairly old... Since madwifi is in constant development, perhaps you could try a cvs-snapshot from http://madwifi.otaku42.de > I then > added a few lines (details below - which I assumed appropriate from a > weblog-style "howto") to my /etc/modules.autoload.d/kernel-2.6 (I am > using the 2.6 "development" kernel): [snap] as already noted, ath_pci is enough > When I reboot I get as far as probing modules then see a load of errors... [snap] > Noting that the first error is generated by the wlan module, following a > session with Google I suspected that my kernel needed wireless network > support... I used menuconfig and made these selections: [snap] (see other posts for comments on this) > Can anyone tell me if they've got the madwifi-drivers working under > Gentoo (with a 2.6 kernel)? If so - where do our approaches differ? I have madwifi working with 2.6.11.5, on multiple cards (even at the same time). In fact, I had it working with about all kernels except 2.6.10, IIRC. The problem is to find state of the madwifi cvs that supports your choice of kernel. Obvious solution to that is to take a new kernel, and use a recent cvs-snapshot. > What kernel options are actually required? (already discussed) > Do I really need all the modules I've got in my autoloading (already discussed) > (I don't care about security Bad, but with below stated explaination ok. > - the only service I'll expose over this interface will be SSH - the > same one as I expose to the internet at large)? Timo -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper wrote: try: # find /lib/modules/`uname -r`/ -name "wlan.ko" -print 'locate' is only accurate as of the last time you updated its database. OK - I was just being lazy - which happened not to matter because I knew my locate database was up-to-date. [ I'd included the grep line for the explicit file to show it didn't give an error that the file wasn't found etc. ] -- # locate wlan.ko /lib/modules/2.6.9-gentoo-r1/net/wlan.ko # find /lib/modules/`uname -r`/ -name "wlan.ko" -print /lib/modules/2.6.9-gentoo-r1/net/wlan.ko # -- If the find command doesn't show wlan.ko, re-merge madwifi and run 'depmod -ae'. Otherwise, just run 'depmod -ae'. So I do have a wlan.ko - but it doesn't contain the symbol - which seems to be the significant difference between our installs. As you might expect "depmod -ae" appears to have no effect... the problem seems to be with my wlan.ko not containing the symbol in the first place rather than a problem detecting the dependency between ath_pci.ko and wlan.ko etc. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > Jason Cooper wrote: > >Steve ([EMAIL PROTECTED]) scribbled: > >>While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!) > >>but they are now... However I still get a (now single) error "ath_pci: > >>Unknown symbol ieee80211_ioctl" - about which I'm as unclear as I was > >>about the dozens of unknown symbols I saw previously. > >> > >> > >Here is the result of 'grep -rn ieee80211_ioctl /lib/modules/`uname -r`/' > > > >[snip misc bs] > >modules.symbols:579:alias symbol:ieee80211_ioctl wlan > >[snip more misc bs] > >Binary file net/ath_pci.ko matches > >Binary file net/wlan.ko matches > > > > > OK... this seems to be relevant... > -- > # grep -rn ieee80211_ioctl /lib/modules/`uname -r`/ > Binary file /lib/modules/2.6.9-gentoo-r1/net/ath_pci.ko matches > # locate wlan.ko try: # find /lib/modules/`uname -r`/ -name "wlan.ko" -print 'locate' is only accurate as of the last time you updated its database. > /lib/modules/2.6.9-gentoo-r1/net/ath_hal.ko > # grep ieee80211_ioctl /lib/modules/2.6.9-gentoo-r1/net/wlan.ko > # locate modules.symbols > /lib/modules/2.6.9-gentoo-r1/modules.symbols > # grep ieee80211_ioctl /lib/modules/2.6.9-gentoo-r1/modules.symbols > # > > Have you any idea why youe wlan.ko matches but mine doesn't? > My modules.symbols does mention wlan - but doesn't mention > ieee80211_ioctl at all. If the find command doesn't show wlan.ko, re-merge madwifi and run 'depmod -ae'. Otherwise, just run 'depmod -ae'. hth, Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper wrote: Steve ([EMAIL PROTECTED]) scribbled: While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!) but they are now... However I still get a (now single) error "ath_pci: Unknown symbol ieee80211_ioctl" - about which I'm as unclear as I was about the dozens of unknown symbols I saw previously. Here is the result of 'grep -rn ieee80211_ioctl /lib/modules/`uname -r`/' [snip misc bs] modules.symbols:579:alias symbol:ieee80211_ioctl wlan [snip more misc bs] Binary file net/ath_pci.ko matches Binary file net/wlan.ko matches OK... this seems to be relevant... -- # grep -rn ieee80211_ioctl /lib/modules/`uname -r`/ Binary file /lib/modules/2.6.9-gentoo-r1/net/ath_pci.ko matches # locate wlan.ko /lib/modules/2.6.9-gentoo-r1/net/ath_hal.ko # grep ieee80211_ioctl /lib/modules/2.6.9-gentoo-r1/net/wlan.ko # locate modules.symbols /lib/modules/2.6.9-gentoo-r1/modules.symbols # grep ieee80211_ioctl /lib/modules/2.6.9-gentoo-r1/modules.symbols # -- Have you any idea why youe wlan.ko matches but mine doesn't? My modules.symbols does mention wlan - but doesn't mention ieee80211_ioctl at all. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > Jason Cooper wrote: > > >aha? In you kernel .config, what is CONFIG_KMOD set to? If set, it > > > >allows the kernel to autoload modules as needed, for example, when they > >are dependencies of ath_pci.ko ... If unset, and wlan.ko isn't listed > >first in /etc/modules.autoload.d/kernel-2.6, this could be the problem. > > > >I think it's under: > > > >Loadable Module Support -> Automatic kernel module loading > > > > > > I've got that: > # grep CONFIG_KMOD .config > CONFIG_KMOD=y > > Which I suppose explains why wlan and ath_hal seem to be loaded for me > without an explicit inclusion. damn. I suppose you could try re-merging madwifi... I'm running out of ideas. If you decide to do that, make sure the currently running kernel is the same one /usr/src/linux points to. What was the output of: # grep -rn ieee80211_ioctl /lib/modules/`uname -r` Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
> >>By any chance can you point me at documentation which explains what > >>facilities are presented by ath_hal and wlan (as a previous post > >>suggests these two aren't strictly necessary.) Is it possible that > >>ath_hal and wlan are loaded anyway as dependencies of ath_pci? > >> > >> > > > >I think that's exactly what happens. The only module I autload is > >ath_pci and it works perfectly. > > > > > That seems to be how it works to me too :-) Though I still can't fathom > the remaining undefined symbol "ieee80211_ioctl" :-S > > >Are you using the latest available kernel? > > > > > > > # uname -srv > Linux 2.6.9-gentoo-r1 #5 Sat Apr 2 18:05:01 BST 2005 I don't know if it will help, but if I were in your situation I would upgrade to the latest. - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper wrote: aha? In you kernel .config, what is CONFIG_KMOD set to? If set, it allows the kernel to autoload modules as needed, for example, when they are dependencies of ath_pci.ko ... If unset, and wlan.ko isn't listed first in /etc/modules.autoload.d/kernel-2.6, this could be the problem. I think it's under: Loadable Module Support -> Automatic kernel module loading I've got that: # grep CONFIG_KMOD .config CONFIG_KMOD=y Which I suppose explains why wlan and ath_hal seem to be loaded for me without an explicit inclusion. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Grant ([EMAIL PROTECTED]) scribbled: > > By any chance can you point me at documentation which explains what > > facilities are presented by ath_hal and wlan (as a previous post > > suggests these two aren't strictly necessary.) Is it possible that > > ath_hal and wlan are loaded anyway as dependencies of ath_pci? > > I think that's exactly what happens. The only module I autload is > ath_pci and it works perfectly. aha? In you kernel .config, what is CONFIG_KMOD set to? If set, it allows the kernel to autoload modules as needed, for example, when they are dependencies of ath_pci.ko ... If unset, and wlan.ko isn't listed first in /etc/modules.autoload.d/kernel-2.6, this could be the problem. I think it's under: Loadable Module Support -> Automatic kernel module loading Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Grant wrote: By any chance can you point me at documentation which explains what facilities are presented by ath_hal and wlan (as a previous post suggests these two aren't strictly necessary.) Is it possible that ath_hal and wlan are loaded anyway as dependencies of ath_pci? I think that's exactly what happens. The only module I autload is ath_pci and it works perfectly. That seems to be how it works to me too :-) Though I still can't fathom the remaining undefined symbol "ieee80211_ioctl" :-S Are you using the latest available kernel? # uname -srv Linux 2.6.9-gentoo-r1 #5 Sat Apr 2 18:05:01 BST 2005 Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper ([EMAIL PROTECTED]) scribbled: > '/lib/modules/`uname-r`/' and then run depmaod -ae again just in case. That should've been 'depmod -ae', sorry. Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!) > but they are now... However I still get a (now single) error "ath_pci: > Unknown symbol ieee80211_ioctl" - about which I'm as unclear as I was > about the dozens of unknown symbols I saw previously. Here is the result of 'grep -rn ieee80211_ioctl /lib/modules/`uname -r`/' [snip misc bs] modules.symbols:579:alias symbol:ieee80211_ioctl wlan [snip more misc bs] Binary file net/ath_pci.ko matches Binary file net/wlan.ko matches This tells me wlan.ko provides the symbol 'ieee80211_ioctl'. Make sure it is the first in the list in '/etc/modules.autoload.d/kernel-2.6'. If you still get the error, make sure wlan.ko is in your '/lib/modules/`uname-r`/' and then run depmaod -ae again just in case. hth, Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
> By any chance can you point me at documentation which explains what > facilities are presented by ath_hal and wlan (as a previous post > suggests these two aren't strictly necessary.) Is it possible that > ath_hal and wlan are loaded anyway as dependencies of ath_pci? I think that's exactly what happens. The only module I autload is ath_pci and it works perfectly. > While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!) > but they are now... However I still get a (now single) error "ath_pci: > Unknown symbol ieee80211_ioctl" - about which I'm as unclear as I was > about the dozens of unknown symbols I saw previously. Are you using the latest available kernel? - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > Jason Cooper wrote: > > >Bad move. Exposing a single port to the internet is more than enough. I > > > >also only expose a few ports (including ssh) to the net. My logs are > >full of knucklehead script kiddies trying to get in through ssh. At a > >minimum, disallow root login, and listen on a port other than 22. (At > >least on the net-facing side). Also, set AllowUsers to just yourself. > > > >btw - all those log entries were when I was listening on port 22... > > > > > I understand your concerns - I had _exactly_ those concerns too - and > yes - I can see script kiddy evidence in my logs too. > > I've disabled remote root login - and in fact only one user can > authenticate via SSH - and that user can't do so using only a password. Yep, I do the same. > I can't easily move to a non-standard port though (as I want to access > it from sites which only allow outbound connections to port 22 (don't Are you planning on providing https connections? If not, most places allow outbound port 80 and port 443 requests. It wouldn't be hidden from automated scans, but at least it would be the wrong scans. :) > ask me why!)) and in any case - I know I get port-scanned and security > through an obscure port number is likely to be as effective as a > chocolate tea-pot. I suppose I could constrain the IP addresses of "security through obscurity" is only bad when it is the _only_ security. However, the few hours it might buy you (on discovery of a new vulnerability) against automated scans so you can shutdown/upgrade could be a life-saver. As long as it's understood that's all it's good for... > hosts which can connect... but I'm not entirely sure that the trade-off > between usefulness to me and improved security makes that worthwhile... > > I realise I run the risk of being compromised if another exploit is > found in SSH - but my fingers are firmly crossed there... I'm trusting > for now that I can keep my keys safe and that there isn't a SSH > back-door... Time will tell I suppose. A neat thing to remember is that in the event of a new vulnerability being discovered, shutting down sshd _doesn't_ kill your current session. I've used that the last time the hole was discovered in openssh. > I understand that I need a stringent firewall in order to make sure my > wireless connection can only effect connection to the SSH service. firewall good. script kiddie bad. :) Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper wrote: The relevant portion of my '/etc/modules.autoload.d/kernel-2.6': wlan ath_hal ath_pci everything else autoloads from these three. By any chance can you point me at documentation which explains what facilities are presented by ath_hal and wlan (as a previous post suggests these two aren't strictly necessary.) Is it possible that ath_hal and wlan are loaded anyway as dependencies of ath_pci? When I reboot I get as far as probing modules then see a load of errors... What are CONFIG_NET_WIRELESS and CONFIG_NET_RADIO set to in your kernel config? While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!) but they are now... However I still get a (now single) error "ath_pci: Unknown symbol ieee80211_ioctl" - about which I'm as unclear as I was about the dozens of unknown symbols I saw previously. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Jason Cooper wrote: Bad move. Exposing a single port to the internet is more than enough. I also only expose a few ports (including ssh) to the net. My logs are full of knucklehead script kiddies trying to get in through ssh. At a minimum, disallow root login, and listen on a port other than 22. (At least on the net-facing side). Also, set AllowUsers to just yourself. btw - all those log entries were when I was listening on port 22... I understand your concerns - I had _exactly_ those concerns too - and yes - I can see script kiddy evidence in my logs too. I've disabled remote root login - and in fact only one user can authenticate via SSH - and that user can't do so using only a password. I can't easily move to a non-standard port though (as I want to access it from sites which only allow outbound connections to port 22 (don't ask me why!)) and in any case - I know I get port-scanned and security through an obscure port number is likely to be as effective as a chocolate tea-pot. I suppose I could constrain the IP addresses of hosts which can connect... but I'm not entirely sure that the trade-off between usefulness to me and improved security makes that worthwhile... I realise I run the risk of being compromised if another exploit is found in SSH - but my fingers are firmly crossed there... I'm trusting for now that I can keep my keys safe and that there isn't a SSH back-door... Time will tell I suppose. I understand that I need a stringent firewall in order to make sure my wireless connection can only effect connection to the SSH service. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Grant wrote: The only module you need to autoload is ath_pci. The kernel option you must be missing is: That is a surprise - I used the same card under FreeBSD and that definitely also needed ATH_HAL - but I bow to your greater experience with Gentoo... I'm guessing from the output from dmesg that ath_hal is actually loaded - though it is not explicitly listed. Device Drivers -> Networking support -> Wireless LAN -> Wireless LAN drivers Ah-ha... That was an obvious error on my part... (I'll learn to read one of these days!) I've now enabled Wireless LAN drivers (though none of the sub-options) and I've made a bit of progress (there are far fewer error messages - though it is still broken...) The output from dmesg now reads like this: -- ath_hal: module license 'Proprietary' taints kernel. ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) wlan: 0.8.4.5 (EXPERIMENTAL) ath_rate_onoe: 1.0 ath_pci: Unknown symbol ieee80211_ioctl -- Maybe there is something else I need to enable in my kernel config? There is probably another one if your wireless card is PCMCIA. You don't need the WAN support. I'm using a DLink DWL-G510 (PCI card) - so PCMCIA shouldn't be relevant to me. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
On Saturday 02 April 2005 08:21, Steve wrote: > Noting that the first error is generated by the wlan module, following a > session with Google I suspected that my kernel needed wireless network > support... I used menuconfig and made these selections: > > -- > â [*] Wan interfaces support > â < > Comtrol Hostess SV-11 support > â < > COSA/SRP sync serial boards support > â < > Etinc PCISYNC serial board support > â < > LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards > â < > Sealevel Systems 4021 support > â < > SyncLink HDLC/SYNCPPP support > â < > Generic HDLC layer > â < > Frame Relay DLCI support > â < > Granch SBNI12 Leased Line adapter support NB: I don't have this kind of card, or actually any wireless network card at all. That said, however, you're looking in the wrong place in the kernel config. What you selected is Wide Area Network support. That's not what you want. Assuming a 2.6 kernel, this is what I believe you want: -> Device Drivers -> Networking support -> Network device support (NETDEVICES [=y]) -> Wireless LAN (non-hamradio) [*] Wireless LAN drivers (non-hamradio) & Wireless Extensions pgpfwvO9DdVD1.pgp Description: PGP signature
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > I realised that the madwifi-driver package is masked and that this > indicates that I may experience problems, but I suspect I'm more > problems than others - considering that loads of people appear to have > the madwifi drivers working with other distributions. I've hunted on the > web for definitive information about the madwifi-driver and while I can > find a fair bit of information I can't find a specific gentoo sample > configuration against which I can compare mine - nor can I find people > reporting the same fault. > > So far I've used emerge to merge the madwifi-driver > (madwifi-driver-0.1_pre20050224) which went without a glitch. I then > added a few lines (details below - which I assumed appropriate from a > weblog-style "howto") to my /etc/modules.autoload.d/kernel-2.6 (I am > using the 2.6 "development" kernel): > > -- > ath_hal > ath_rate_amrr > ath_rate_onoe > ath_pci > wlan > wlan_acl > wlan_ccmp > wlan_tkip > wlan_wep > wlan_xauth > -- The relevant portion of my '/etc/modules.autoload.d/kernel-2.6': wlan ath_hal ath_pci everything else autoloads from these three. > > When I reboot I get as far as probing modules then see a load of errors... [snip error msgs] What are CONFIG_NET_WIRELESS and CONFIG_NET_RADIO set to in your kernel config? Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
Steve ([EMAIL PROTECTED]) scribbled: > Can anyone tell me if they've got the madwifi-drivers working under > Gentoo (with a 2.6 kernel)? If so - where do our approaches differ? What > kernel options are actually required? Do I really need all the modules > I've got in my autoloading (I don't care about security - the only Bad move. Exposing a single port to the internet is more than enough. I also only expose a few ports (including ssh) to the net. My logs are full of knucklehead script kiddies trying to get in through ssh. At a minimum, disallow root login, and listen on a port other than 22. (At least on the net-facing side). Also, set AllowUsers to just yourself. btw - all those log entries were when I was listening on port 22... > service I'll expose over this interface will be SSH - the same one as I > expose to the internet at large)? Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MADWIFI driver...
> I realised that the madwifi-driver package is masked and that this > indicates that I may experience problems, but I suspect I'm more > problems than others - considering that loads of people appear to have > the madwifi drivers working with other distributions. I've hunted on the > web for definitive information about the madwifi-driver and while I can > find a fair bit of information I can't find a specific gentoo sample > configuration against which I can compare mine - nor can I find people > reporting the same fault. > > So far I've used emerge to merge the madwifi-driver > (madwifi-driver-0.1_pre20050224) which went without a glitch. I then > added a few lines (details below - which I assumed appropriate from a > weblog-style "howto") to my /etc/modules.autoload.d/kernel-2.6 (I am > using the 2.6 "development" kernel): > > -- > ath_hal > ath_rate_amrr > ath_rate_onoe > ath_pci > wlan > wlan_acl > wlan_ccmp > wlan_tkip > wlan_wep > wlan_xauth > -- > > When I reboot I get as far as probing modules then see a load of errors... > > -- > ath_hal: module license 'Proprietary' taints kernel. > ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) > wlan: Unknown symbol wireless_send_event > ath_rate_amrr: Unknown symbol ether_sprintf > ath_rate_amrr: Unknown symbol ieee80211_iterate_nodes > wlan: Unknown symbol wireless_send_event > ath_rate_onoe: Unknown symbol ether_sprintf > ath_rate_onoe: Unknown symbol ieee80211_iterate_nodes > wlan: Unknown symbol wireless_send_event > ath_rate_onoe: Unknown symbol ether_sprintf > ath_rate_onoe: Unknown symbol ieee80211_iterate_nodes > ath_pci: Unknown symbol ath_rate_tx_complete > ath_pci: Unknown symbol ieee80211_encap > ath_pci: Unknown symbol ieee80211_input > ath_pci: Unknown symbol ieee80211_ifattach > ath_pci: Unknown symbol ieee80211_sysctl_register > ath_pci: Unknown symbol ieee80211_beacon_update > ath_pci: Unknown symbol ath_rate_attach > ath_pci: Unknown symbol ether_sprintf > ath_pci: Unknown symbol ieee80211_ifdetach > ath_pci: Unknown symbol ieee80211_free_node > ath_pci: Unknown symbol ath_rate_newassoc > ath_pci: Unknown symbol ieee80211_notify_michael_failure > ath_pci: Unknown symbol ieee80211_dump_pkt > ath_pci: Unknown symbol ath_rate_node_copy > ath_pci: Unknown symbol ieee80211_media_change > ath_pci: Unknown symbol ieee80211_beacon_alloc > ath_pci: Unknown symbol ieee80211_find_node > ath_pci: Unknown symbol ieee80211_mhz2ieee > ath_pci: Unknown symbol ath_rate_node_cleanup > ath_pci: Unknown symbol ath_rate_detach > ath_pci: Unknown symbol ieee80211_next_scan > ath_pci: Unknown symbol ieee80211_media_init > ath_pci: Unknown symbol ieee80211_ioctl > ath_pci: Unknown symbol ieee80211_media_status > ath_pci: Unknown symbol ieee80211_announce > ath_pci: Unknown symbol ieee80211_chan2ieee > ath_pci: Unknown symbol ieee80211_state_name > ath_pci: Unknown symbol ath_rate_node_init > ath_pci: Unknown symbol ath_rate_findrate > ath_pci: Unknown symbol ieee80211_crypto_encap > ath_pci: Unknown symbol ieee80211_chan2mode > ath_pci: Unknown symbol ieee80211_getrssi > ath_pci: Unknown symbol ath_rate_newstate > ath_pci: Unknown symbol ath_rate_setupxtxdesc > wlan: Unknown symbol wireless_send_event > wlan: Unknown symbol wireless_send_event > wlan_acl: Unknown symbol ieee80211_aclator_unregister > ath_pci: Unknown symbol ath_rate_node_cleanup > ath_pci: Unknown symbol ath_rate_detach > ath_pci: Unknown symbol ieee80211_next_scan > ath_pci: Unknown symbol ieee80211_media_init > ath_pci: Unknown symbol ieee80211_ioctl > ath_pci: Unknown symbol ieee80211_media_status > ath_pci: Unknown symbol ieee80211_announce > ath_pci: Unknown symbol ieee80211_chan2ieee > ath_pci: Unknown symbol ieee80211_state_name > ath_pci: Unknown symbol ath_rate_node_init > ath_pci: Unknown symbol ath_rate_findrate > ath_pci: Unknown symbol ieee80211_crypto_encap > ath_pci: Unknown symbol ieee80211_chan2mode > ath_pci: Unknown symbol ieee80211_getrssi > ath_pci: Unknown symbol ath_rate_newstate > ath_pci: Unknown symbol ath_rate_setupxtxdesc > wlan: Unknown symbol wireless_send_event > wlan: Unknown symbol wireless_send_event > wlan_acl: Unknown symbol ieee80211_aclator_unregister > wlan_acl: Unknown symbol ether_sprintf > wlan_acl: Unknown symbol ieee80211_aclator_register > wlan: Unknown symbol wireless_send_event > wlan_ccmp: Unknown symbol ether_sprintf > wlan_ccmp: Unknown symbol ieee80211_crypto_unregister > wlan_ccmp: Unknown symbol ieee80211_notify_replay_failure > wlan_ccmp: Unknown symbol ieee80211_crypto_register > wlan: Unknown symbol wireless_send_event > wlan_tkip: Unknown symbol ether_sprintf > wlan_tkip: Unknown symbol ieee80211_notify_michael_failure > wlan_tkip: Unknown symbol ieee80211_crypto_unregister > wlan_tkip: Unknown symbol ieee80211_notify_replay_failure > wlan_tkip: Unknown symbol ieee80211_crypto_register > wlan: Unknown symbol wireless_send_event > wlan_wep: Unknown symbol ether_sprintf > wlan_wep: Unknown symbol rc4_init > wlan_wep: Un
