* [gentoo-user] Atheros kernel driver and my wireless access point setup
@ 2009-06-09 5:21 Jason Carson
2009-06-09 5:46 ` Jason Carson
` (2 more replies)
0 siblings, 3 replies; 41+ messages in thread
From: Jason Carson @ 2009-06-09 5:21 UTC (permalink / raw
To: gentoo-user
Greetings,
I am trying to setup a wireless access point using the atheros kernel
driver (Built into the kernel, not as a module). I am using
Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in
"master mode" but for some reason it is starting up in "managed mode".
When wlan0 starts up I get this error message...
* Bringing up interface wlan0
* configuring wireless network for wlan0
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; invalid argument.
* wlan0 connected to SSID "MyNetwork"
* in managed mode (WEP Disabled)
* null... [ ok ]
then when hostapd starts up I get this error message...
* Starting hostapd...
Configuration file: /etc/hostapd/hostapd.conf
Failed to set interface wlan0 to master mode.
nl80211 driver initialization failed.
ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil)
handler=0x8094b70
* start-stop-daemon: failed to start `/usr/sbin/hostapd'
[ !! ]
* ERROR: hostapd failed to start
Here is my /etc/conf.d/net
config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast 69.196.152.255"
config_eth1="null"
config_wlan0="null"
bridge_br0="eth1 wlan0"
config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255"
channel_wlan0="1"
mode_wlan0="master"
essid_wlan0="MyNetwork"
Here is my hostapd.conf
interface=wlan0
bridge=br0
driver=nl80211
ssid=MyNetwork
hw_mode=g
channel=1
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
country_code=CA
wpa=1
wpa_passphrase=passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
Anyone know how to change my wireless card to "master mode" and make it so
I don't get those error messages?
Thanks
P.S. I have everything working with madwifi and an older kernel so worst
case scenario I stay with that configuration until I get this problem
figured out.
^ permalink raw reply [flat|nested] 41+ messages in thread* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 5:21 [gentoo-user] Atheros kernel driver and my wireless access point setup Jason Carson @ 2009-06-09 5:46 ` Jason Carson 2009-06-09 6:33 ` Dale 2009-06-09 5:50 ` Mick 2009-06-09 10:41 ` Norman Rieß 2 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-09 5:46 UTC (permalink / raw To: gentoo-user Hey all, I think I might know the problem. After doing some reading apparently many distrutions, including Gentoo, don't ship hostapd with support for the nl80211 driver. I checked the Gentoo tarball and this is the case. I tried editing the defconfig file in hostapd.tar.gz (enabling CONFIG_DRIVER_NL80211=y)but when I opened the tarball, edited it, and created a new tarball then tried to emerge it it gave me this... penguin distfiles # emerge hostapd Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) net-wireless/hostapd-0.6.9 Refetching... File renamed to '/usr/portage/distfiles/hostapd-0.6.9.tar.gz._checksum_failure_.70f9W1' ...and then wanted to download hostapd again. Anyone know how I edit the source of the hostapd tarball so it will work? > Greetings, > > I am trying to setup a wireless access point using the atheros kernel > driver (Built into the kernel, not as a module). I am using > Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in > "master mode" but for some reason it is starting up in "managed mode". > > > When wlan0 starts up I get this error message... > > > * Bringing up interface wlan0 > * configuring wireless network for wlan0 > Error for wireless request "Set Mode" (8B06) : > SET failed on device wlan0 ; invalid argument. > * wlan0 connected to SSID "MyNetwork" > * in managed mode (WEP Disabled) > * null... [ ok ] > > > then when hostapd starts up I get this error message... > > > * Starting hostapd... > Configuration file: /etc/hostapd/hostapd.conf > Failed to set interface wlan0 to master mode. > nl80211 driver initialization failed. > ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil) > handler=0x8094b70 > * start-stop-daemon: failed to start `/usr/sbin/hostapd' > [ !! ] > * ERROR: hostapd failed to start > > > Here is my /etc/conf.d/net > > > config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast > 69.196.152.255" > config_eth1="null" > config_wlan0="null" > bridge_br0="eth1 wlan0" > config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" > channel_wlan0="1" > mode_wlan0="master" > essid_wlan0="MyNetwork" > > > Here is my hostapd.conf > > > interface=wlan0 > bridge=br0 > driver=nl80211 > ssid=MyNetwork > hw_mode=g > channel=1 > macaddr_acl=0 > auth_algs=1 > ignore_broadcast_ssid=0 > country_code=CA > wpa=1 > wpa_passphrase=passphrase > wpa_key_mgmt=WPA-PSK > wpa_pairwise=TKIP > rsn_pairwise=CCMP > > > Anyone know how to change my wireless card to "master mode" and make it so > I don't get those error messages? > > > Thanks > > > P.S. I have everything working with madwifi and an older kernel so worst > case scenario I stay with that configuration until I get this problem > figured out. > > > ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 5:46 ` Jason Carson @ 2009-06-09 6:33 ` Dale 2009-06-09 7:15 ` Jason Carson 2009-06-09 7:45 ` Neil Bothwick 0 siblings, 2 replies; 41+ messages in thread From: Dale @ 2009-06-09 6:33 UTC (permalink / raw To: gentoo-user Jason Carson wrote: > Hey all, > > I think I might know the problem. After doing some reading apparently many > distrutions, including Gentoo, don't ship hostapd with support for the > nl80211 driver. I checked the Gentoo tarball and this is the case. I tried > editing the defconfig file in hostapd.tar.gz (enabling > CONFIG_DRIVER_NL80211=y)but when I opened the tarball, edited it, and > created a new tarball then tried to emerge it it gave me this... > > > penguin distfiles # emerge hostapd > Calculating dependencies... done! > > >>>> Verifying ebuild manifests >>>> > > >>>> Emerging (1 of 1) net-wireless/hostapd-0.6.9 >>>> > Refetching... File renamed to > '/usr/portage/distfiles/hostapd-0.6.9.tar.gz._checksum_failure_.70f9W1' > > > ...and then wanted to download hostapd again. > > Anyone know how I edit the source of the hostapd tarball so it will work? > > What it is doing is correct. The package has been changed and portage doesn't know if you did it or some random hacker. That said, man ebuild and check out the manifest section. I have never done this but maybe it will make sense to you. Also, I think emerge used to have the --digest option. Basically it tells emerge to skip checking the digest. I didn't see it in the man page so it may not be there anymore. Dale :-) :-) ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 6:33 ` Dale @ 2009-06-09 7:15 ` Jason Carson 2009-06-09 12:57 ` Stroller 2009-06-09 7:45 ` Neil Bothwick 1 sibling, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-09 7:15 UTC (permalink / raw To: gentoo-user > Jason Carson wrote: >> Hey all, >> >> I think I might know the problem. After doing some reading apparently >> many >> distrutions, including Gentoo, don't ship hostapd with support for the >> nl80211 driver. I checked the Gentoo tarball and this is the case. I >> tried >> editing the defconfig file in hostapd.tar.gz (enabling >> CONFIG_DRIVER_NL80211=y)but when I opened the tarball, edited it, and >> created a new tarball then tried to emerge it it gave me this... >> >> >> penguin distfiles # emerge hostapd >> Calculating dependencies... done! >> >> >>>>> Verifying ebuild manifests >>>>> >> >> >>>>> Emerging (1 of 1) net-wireless/hostapd-0.6.9 >>>>> >> Refetching... File renamed to >> '/usr/portage/distfiles/hostapd-0.6.9.tar.gz._checksum_failure_.70f9W1' >> >> >> ...and then wanted to download hostapd again. >> >> Anyone know how I edit the source of the hostapd tarball so it will >> work? >> >> > > What it is doing is correct. The package has been changed and portage > doesn't know if you did it or some random hacker. That said, man ebuild > and check out the manifest section. I have never done this but maybe it > will make sense to you. > > Also, I think emerge used to have the --digest option. Basically it > tells emerge to skip checking the digest. I didn't see it in the man > page so it may not be there anymore. > > Dale > > :-) :-) > > Hmmmm, I tried emerging hostapd normally and I noticed this... * Enabling Wi-Fi Protected Setup support * Enabling drivers: * HostAP driver enabled * Wired driver enabled * Prism54 driver enabled * Madwifi driver enabled * nl80211 driver enabled ...which says that nl80211 is enabled, yet the defconfig file in the tar ball shows this line commented out so I am confused as to how I fix my problem... #CONFIG_DRIVER_NL80211=y ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 7:15 ` Jason Carson @ 2009-06-09 12:57 ` Stroller 2009-06-09 21:15 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Stroller @ 2009-06-09 12:57 UTC (permalink / raw To: gentoo-user On 9 Jun 2009, at 08:15, Jason Carson wrote: > Hmmmm, I tried emerging hostapd normally and I noticed this... > > * Enabling Wi-Fi Protected Setup support > * Enabling drivers: > * HostAP driver enabled > * Wired driver enabled > * Prism54 driver enabled > * Madwifi driver enabled > * nl80211 driver enabled > > ...which says that nl80211 is enabled, yet the defconfig file in the > tar > ball shows this line commented out so I am confused as to how I fix my > problem... > > #CONFIG_DRIVER_NL80211=y In my experience this notation will be used to suggest the default. I.E. if there's no entry for CONFIG_DRIVER_NL80211 (or it's commented out) then the option will be enabled by default. If the config file said #CONFIG_DRIVER_NL80211=n then I would tend to assume that the option will be disabled by default, and that this line needs uncommenting and changing in order to enable it. I can't say that everyone uses this convention, or even that I've ever read it stated, but 1) if I look at /etc/ssh/sshd_config, for example, all the options that I've set myself are lines I've had to uncomment AND change. 2) the compiler / build tool says it's building your module, anyway. Who cares what the config file says? Stroller. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 12:57 ` Stroller @ 2009-06-09 21:15 ` Jason Carson 2009-06-09 21:27 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-09 21:15 UTC (permalink / raw To: gentoo-user > > On 9 Jun 2009, at 08:15, Jason Carson wrote: >> Hmmmm, I tried emerging hostapd normally and I noticed this... >> >> * Enabling Wi-Fi Protected Setup support >> * Enabling drivers: >> * HostAP driver enabled >> * Wired driver enabled >> * Prism54 driver enabled >> * Madwifi driver enabled >> * nl80211 driver enabled >> >> ...which says that nl80211 is enabled, yet the defconfig file in the >> tar >> ball shows this line commented out so I am confused as to how I fix my >> problem... >> >> #CONFIG_DRIVER_NL80211=y > > In my experience this notation will be used to suggest the default. > > I.E. if there's no entry for CONFIG_DRIVER_NL80211 (or it's commented > out) then the option will be enabled by default. > > If the config file said > #CONFIG_DRIVER_NL80211=n > then I would tend to assume that the option will be disabled by > default, and that this line needs uncommenting and changing in order > to enable it. > > I can't say that everyone uses this convention, or even that I've ever > read it stated, but > 1) if I look at /etc/ssh/sshd_config, for example, all the options > that I've set myself are lines I've had to uncomment AND change. > 2) the compiler / build tool says it's building your module, anyway. > Who cares what the config file says? > > Stroller. > > > ok, I guess it is enabled then. I wonder why its not working. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 21:15 ` Jason Carson @ 2009-06-09 21:27 ` Jason Carson 0 siblings, 0 replies; 41+ messages in thread From: Jason Carson @ 2009-06-09 21:27 UTC (permalink / raw To: gentoo-user >> >> On 9 Jun 2009, at 08:15, Jason Carson wrote: >>> Hmmmm, I tried emerging hostapd normally and I noticed this... >>> >>> * Enabling Wi-Fi Protected Setup support >>> * Enabling drivers: >>> * HostAP driver enabled >>> * Wired driver enabled >>> * Prism54 driver enabled >>> * Madwifi driver enabled >>> * nl80211 driver enabled >>> >>> ...which says that nl80211 is enabled, yet the defconfig file in the >>> tar >>> ball shows this line commented out so I am confused as to how I fix my >>> problem... >>> >>> #CONFIG_DRIVER_NL80211=y >> >> In my experience this notation will be used to suggest the default. >> >> I.E. if there's no entry for CONFIG_DRIVER_NL80211 (or it's commented >> out) then the option will be enabled by default. >> >> If the config file said >> #CONFIG_DRIVER_NL80211=n >> then I would tend to assume that the option will be disabled by >> default, and that this line needs uncommenting and changing in order >> to enable it. >> >> I can't say that everyone uses this convention, or even that I've ever >> read it stated, but >> 1) if I look at /etc/ssh/sshd_config, for example, all the options >> that I've set myself are lines I've had to uncomment AND change. >> 2) the compiler / build tool says it's building your module, anyway. >> Who cares what the config file says? >> >> Stroller. >> >> >> > ok, I guess it is enabled then. I wonder why its not working. > > I came across this... http://wireless.kernel.org/en/users/Documentation/hostapd?action=show&redirect=RTFM-AP and it says... "Now find this line: #CONFIG_DRIVER_NL80211=y and uncomment it by removing the '#' sign. Repeat for other settings that you may be interested in. The basic configuration, with only this line uncommented is enough to get hostapd up and running with WPA/WPA2 authentication and encryption." ...so I don't know what to believe anymore lol :-) ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 6:33 ` Dale 2009-06-09 7:15 ` Jason Carson @ 2009-06-09 7:45 ` Neil Bothwick 1 sibling, 0 replies; 41+ messages in thread From: Neil Bothwick @ 2009-06-09 7:45 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 655 bytes --] On Tue, 09 Jun 2009 01:33:35 -0500, Dale wrote: > Also, I think emerge used to have the --digest option. Basically it > tells emerge to skip checking the digest. I didn't see it in the man > page so it may not be there anymore. It was dangerous, because it ignored digests for all packages emerged, not just the one. Instead use ebuild /path/to/ebuild manifest You should copy the ebuild to an overlay before doing this, or this will be undone at the next sync. -- Neil Bothwick "God created the world in six days. On the seventh day he also decided to create England... just to try out his Practical Joke Weather Machine." [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 5:21 [gentoo-user] Atheros kernel driver and my wireless access point setup Jason Carson 2009-06-09 5:46 ` Jason Carson @ 2009-06-09 5:50 ` Mick 2009-06-09 6:12 ` Jason Carson 2009-06-09 10:41 ` Norman Rieß 2 siblings, 1 reply; 41+ messages in thread From: Mick @ 2009-06-09 5:50 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 2426 bytes --] On Tuesday 09 June 2009, Jason Carson wrote: > Greetings, > > I am trying to setup a wireless access point using the atheros kernel > driver (Built into the kernel, not as a module). I am using > Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in > "master mode" but for some reason it is starting up in "managed mode". > > > When wlan0 starts up I get this error message... > > > * Bringing up interface wlan0 > * configuring wireless network for wlan0 > Error for wireless request "Set Mode" (8B06) : > SET failed on device wlan0 ; invalid argument. > * wlan0 connected to SSID "MyNetwork" > * in managed mode (WEP Disabled) > * null... [ ok ] > > > then when hostapd starts up I get this error message... > > > * Starting hostapd... > Configuration file: /etc/hostapd/hostapd.conf > Failed to set interface wlan0 to master mode. > nl80211 driver initialization failed. > ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil) > handler=0x8094b70 > * start-stop-daemon: failed to start `/usr/sbin/hostapd' > [ !! ] > * ERROR: hostapd failed to start > > > Here is my /etc/conf.d/net > > > config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast 69.196.152.255" > config_eth1="null" > config_wlan0="null" > bridge_br0="eth1 wlan0" > config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" > channel_wlan0="1" > mode_wlan0="master" > essid_wlan0="MyNetwork" > > > Here is my hostapd.conf > > > interface=wlan0 > bridge=br0 > driver=nl80211 > ssid=MyNetwork > hw_mode=g > channel=1 > macaddr_acl=0 > auth_algs=1 > ignore_broadcast_ssid=0 > country_code=CA > wpa=1 > wpa_passphrase=passphrase > wpa_key_mgmt=WPA-PSK > wpa_pairwise=TKIP > rsn_pairwise=CCMP > > > Anyone know how to change my wireless card to "master mode" and make it so > I don't get those error messages? > > > Thanks > > > P.S. I have everything working with madwifi and an older kernel so worst > case scenario I stay with that configuration until I get this problem > figured out. Should you also define in your /etc/conf.d/net the driver? modules=( "wpa_supplicant" ) wpa_supplicant_wlan0="-Dwext" (but I'm not sure of the options because I have never set up the card as master with hostapd). HTH. -- Regards, Mick [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 5:50 ` Mick @ 2009-06-09 6:12 ` Jason Carson 0 siblings, 0 replies; 41+ messages in thread From: Jason Carson @ 2009-06-09 6:12 UTC (permalink / raw To: gentoo-user > On Tuesday 09 June 2009, Jason Carson wrote: >> Greetings, >> >> I am trying to setup a wireless access point using the atheros kernel >> driver (Built into the kernel, not as a module). I am using >> Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in >> "master mode" but for some reason it is starting up in "managed mode". >> >> >> When wlan0 starts up I get this error message... >> >> >> * Bringing up interface wlan0 >> * configuring wireless network for wlan0 >> Error for wireless request "Set Mode" (8B06) : >> SET failed on device wlan0 ; invalid argument. >> * wlan0 connected to SSID "MyNetwork" >> * in managed mode (WEP Disabled) >> * null... [ ok ] >> >> >> then when hostapd starts up I get this error message... >> >> >> * Starting hostapd... >> Configuration file: /etc/hostapd/hostapd.conf >> Failed to set interface wlan0 to master mode. >> nl80211 driver initialization failed. >> ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil) >> handler=0x8094b70 >> * start-stop-daemon: failed to start `/usr/sbin/hostapd' >> [ !! ] >> * ERROR: hostapd failed to start >> >> >> Here is my /etc/conf.d/net >> >> >> config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast >> 69.196.152.255" >> config_eth1="null" >> config_wlan0="null" >> bridge_br0="eth1 wlan0" >> config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" >> channel_wlan0="1" >> mode_wlan0="master" >> essid_wlan0="MyNetwork" >> >> >> Here is my hostapd.conf >> >> >> interface=wlan0 >> bridge=br0 >> driver=nl80211 >> ssid=MyNetwork >> hw_mode=g >> channel=1 >> macaddr_acl=0 >> auth_algs=1 >> ignore_broadcast_ssid=0 >> country_code=CA >> wpa=1 >> wpa_passphrase=passphrase >> wpa_key_mgmt=WPA-PSK >> wpa_pairwise=TKIP >> rsn_pairwise=CCMP >> >> >> Anyone know how to change my wireless card to "master mode" and make it >> so >> I don't get those error messages? >> >> >> Thanks >> >> >> P.S. I have everything working with madwifi and an older kernel so worst >> case scenario I stay with that configuration until I get this problem >> figured out. > > Should you also define in your /etc/conf.d/net the driver? > > modules=( "wpa_supplicant" ) > wpa_supplicant_wlan0="-Dwext" > > (but I'm not sure of the options because I have never set up the card as > master with hostapd). > > HTH. > -- > Regards, > Mick Maybe, I don't know. I thought wpa_supplicant was for clients not wireless access points. I am currently running the madwifi driver and an older kernel. I am not using wpa_supplicant and it works fine as a access point. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 5:21 [gentoo-user] Atheros kernel driver and my wireless access point setup Jason Carson 2009-06-09 5:46 ` Jason Carson 2009-06-09 5:50 ` Mick @ 2009-06-09 10:41 ` Norman Rieß 2009-06-09 21:12 ` Jason Carson 2 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-09 10:41 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: > Greetings, > > I am trying to setup a wireless access point using the atheros kernel > driver (Built into the kernel, not as a module). I am using > Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in > "master mode" but for some reason it is starting up in "managed mode". > > > When wlan0 starts up I get this error message... > > > * Bringing up interface wlan0 > * configuring wireless network for wlan0 > Error for wireless request "Set Mode" (8B06) : > SET failed on device wlan0 ; invalid argument. > * wlan0 connected to SSID "MyNetwork" > * in managed mode (WEP Disabled) > * null... [ ok ] > > > then when hostapd starts up I get this error message... > > > * Starting hostapd... > Configuration file: /etc/hostapd/hostapd.conf > Failed to set interface wlan0 to master mode. > nl80211 driver initialization failed. > ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil) > handler=0x8094b70 > * start-stop-daemon: failed to start `/usr/sbin/hostapd' > [ !! ] > * ERROR: hostapd failed to start > > > Here is my /etc/conf.d/net > > > config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast 69.196.152.255" > config_eth1="null" > config_wlan0="null" > bridge_br0="eth1 wlan0" > config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" > channel_wlan0="1" > mode_wlan0="master" > essid_wlan0="MyNetwork" > > > Here is my hostapd.conf > > > interface=wlan0 > bridge=br0 > driver=nl80211 > ssid=MyNetwork > hw_mode=g > channel=1 > macaddr_acl=0 > auth_algs=1 > ignore_broadcast_ssid=0 > country_code=CA > wpa=1 > wpa_passphrase=passphrase > wpa_key_mgmt=WPA-PSK > wpa_pairwise=TKIP > rsn_pairwise=CCMP > > > Anyone know how to change my wireless card to "master mode" and make it so > I don't get those error messages? > > > Thanks > > > P.S. I have everything working with madwifi and an older kernel so worst > case scenario I stay with that configuration until I get this problem > figured out. > > > Hello, do _NOT_ initialize the master mode of your nic with the rc-script. Let hostapd do that. rc-script will fail! So your /etc/conf.d/net would look like this: config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast 69.196.152.255" config_eth1="null" config_wlan0="null" bridge_br0="eth1 wlan0" config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" Regards Norman ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 10:41 ` Norman Rieß @ 2009-06-09 21:12 ` Jason Carson 2009-06-10 0:35 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-09 21:12 UTC (permalink / raw To: gentoo-user > Jason Carson schrieb: >> Greetings, >> >> I am trying to setup a wireless access point using the atheros kernel >> driver (Built into the kernel, not as a module). I am using >> Vanilla-Sources 2.6.29.4. I need my wireless network card to start up in >> "master mode" but for some reason it is starting up in "managed mode". >> >> >> When wlan0 starts up I get this error message... >> >> >> * Bringing up interface wlan0 >> * configuring wireless network for wlan0 >> Error for wireless request "Set Mode" (8B06) : >> SET failed on device wlan0 ; invalid argument. >> * wlan0 connected to SSID "MyNetwork" >> * in managed mode (WEP Disabled) >> * null... [ ok ] >> >> >> then when hostapd starts up I get this error message... >> >> >> * Starting hostapd... >> Configuration file: /etc/hostapd/hostapd.conf >> Failed to set interface wlan0 to master mode. >> nl80211 driver initialization failed. >> ELOOP: remaining socket: sock=5 eloop_data=0x80f5a38 user_data=(nil) >> handler=0x8094b70 >> * start-stop-daemon: failed to start `/usr/sbin/hostapd' >> [ !! ] >> * ERROR: hostapd failed to start >> >> >> Here is my /etc/conf.d/net >> >> >> config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast >> 69.196.152.255" >> config_eth1="null" >> config_wlan0="null" >> bridge_br0="eth1 wlan0" >> config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" >> channel_wlan0="1" >> mode_wlan0="master" >> essid_wlan0="MyNetwork" >> >> >> Here is my hostapd.conf >> >> >> interface=wlan0 >> bridge=br0 >> driver=nl80211 >> ssid=MyNetwork >> hw_mode=g >> channel=1 >> macaddr_acl=0 >> auth_algs=1 >> ignore_broadcast_ssid=0 >> country_code=CA >> wpa=1 >> wpa_passphrase=passphrase >> wpa_key_mgmt=WPA-PSK >> wpa_pairwise=TKIP >> rsn_pairwise=CCMP >> >> >> Anyone know how to change my wireless card to "master mode" and make it >> so >> I don't get those error messages? >> >> >> Thanks >> >> >> P.S. I have everything working with madwifi and an older kernel so worst >> case scenario I stay with that configuration until I get this problem >> figured out. >> >> >> > Hello, > > do _NOT_ initialize the master mode of your nic with the rc-script. Let > hostapd do that. rc-script will fail! > So your /etc/conf.d/net would look like this: > > config_eth0="69.196.152.151 netmask 255.255.255.0 broadcast > 69.196.152.255" > config_eth1="null" > config_wlan0="null" > bridge_br0="eth1 wlan0" > config_br0="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255" > > > > Regards Norman > > > Hey Norman, I tried changing my /etc/conf.d/net to what you suggested but it resulted in the following errors... *Bringing up interface wlan0 * Configuring wireless network for wlan0 * Scanning for access points * no access points found * Failed to configure wireless for wlan0 Then because wlan0 wouldn't start I got a bunch of errors like... * Error: cannot start named as net.wlan0 would not start * Error: cannot start sshd as net.wlan0 would not start * Error: cannot start apache2 as net.wlan0 would not start etc... ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-09 21:12 ` Jason Carson @ 2009-06-10 0:35 ` Norman Rieß 2009-06-10 4:38 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-10 0:35 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: > Hey Norman, > > I tried changing my /etc/conf.d/net to what you suggested but it resulted > in the following errors... > > *Bringing up interface wlan0 > * Configuring wireless network for wlan0 > * Scanning for access points > * no access points found > * Failed to configure wireless for wlan0 > > Then because wlan0 wouldn't start I got a bunch of errors like... > > * Error: cannot start named as net.wlan0 would not start > * Error: cannot start sshd as net.wlan0 would not start > * Error: cannot start apache2 as net.wlan0 would not start > etc... > > > > > This is still rc-script output... do not use the rc-script. Do not start it! Your errors would be, because you have to detach these services from wlan0 and let them use the bridge. Here is some output from my box: mimir ~ # rc-update -s -v | grep net local | default nonetwork net.br0 | default net.eth0 | default net.lo | boot netmount | default mimir ~ # ifconfig wlan0 wlan0 Protokoll:Ethernet Hardware Adresse 00:80:48:5e:57:3d inet6 Adresse: fe80::280:48ff:fe5e:573d/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:7344 (7.1 KiB) TX bytes:14190 (13.8 KiB) mimir ~ # ls /etc/init.d/net.* /etc/init.d/net.br0 /etc/init.d/net.eth0 /etc/init.d/net.lo As you can see, there is no rc-script on wlan, but it is initialized an running in AP mode. Regards Norman ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 0:35 ` Norman Rieß @ 2009-06-10 4:38 ` Jason Carson 2009-06-10 10:37 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-10 4:38 UTC (permalink / raw To: gentoo-user > Jason Carson schrieb: >> Hey Norman, >> >> I tried changing my /etc/conf.d/net to what you suggested but it >> resulted >> in the following errors... >> >> *Bringing up interface wlan0 >> * Configuring wireless network for wlan0 >> * Scanning for access points >> * no access points found >> * Failed to configure wireless for wlan0 >> >> Then because wlan0 wouldn't start I got a bunch of errors like... >> >> * Error: cannot start named as net.wlan0 would not start >> * Error: cannot start sshd as net.wlan0 would not start >> * Error: cannot start apache2 as net.wlan0 would not start >> etc... >> >> >> >> >> > This is still rc-script output... do not use the rc-script. Do not start > it! > Your errors would be, because you have to detach these services from > wlan0 and let them use the bridge. > > Here is some output from my box: > > mimir ~ # rc-update -s -v | grep net > local | default nonetwork > net.br0 | default > net.eth0 | default > net.lo | boot > netmount | default > mimir ~ # ifconfig wlan0 > wlan0 Protokoll:Ethernet Hardware Adresse 00:80:48:5e:57:3d > inet6 Adresse: fe80::280:48ff:fe5e:573d/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:48 errors:0 dropped:0 overruns:0 frame:0 > TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:7344 (7.1 KiB) TX bytes:14190 (13.8 KiB) > > mimir ~ # ls /etc/init.d/net.* > /etc/init.d/net.br0 /etc/init.d/net.eth0 /etc/init.d/net.lo > > As you can see, there is no rc-script on wlan, but it is initialized an > running in AP mode. > > Regards > Norman > > > Thanks for the clarification Norman :-) ok, I removed net.wlan0 so it doesn't start up anymore. My computer booted up and all the services are working the way they should, however I am having a problem getting hostapd to start. Here is the error I get when I tried to start up hostapd... penguin ~ # /etc/init.d/hostapd start * Bringing up interface wlan0 * Configuring wireless network for wlan0 * Scanning for access points * no access points found * Failed to configure wireless for wlan0 * ERROR: net.wlan0 failed to start * ERROR: cannot start hostapd as net.wlan0 would not start It's suppose to be an access point, not scanning for one so do you have any idea what I should do now? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 4:38 ` Jason Carson @ 2009-06-10 10:37 ` Norman Rieß 2009-06-10 18:20 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-10 10:37 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: > Thanks for the clarification Norman :-) > > ok, I removed net.wlan0 so it doesn't start up anymore. My computer booted > up and all the services are working the way they should, however I am > having a problem getting hostapd to start. Here is the error I get when I > tried to start up hostapd... > > penguin ~ # /etc/init.d/hostapd start > * Bringing up interface wlan0 > * Configuring wireless network for wlan0 > * Scanning for access points > * no access points found > * Failed to configure wireless for wlan0 > * ERROR: net.wlan0 failed to start > * ERROR: cannot start hostapd as net.wlan0 would not start > > It's suppose to be an access point, not scanning for one so do you have > any idea what I should do now? > > > Did you remove wlan0 from the /etc/conf.d/hostapd file? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 10:37 ` Norman Rieß @ 2009-06-10 18:20 ` Jason Carson 2009-06-10 20:04 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-10 18:20 UTC (permalink / raw To: gentoo-user > Jason Carson schrieb: >> Thanks for the clarification Norman :-) >> >> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >> booted >> up and all the services are working the way they should, however I am >> having a problem getting hostapd to start. Here is the error I get when >> I >> tried to start up hostapd... >> >> penguin ~ # /etc/init.d/hostapd start >> * Bringing up interface wlan0 >> * Configuring wireless network for wlan0 >> * Scanning for access points >> * no access points found >> * Failed to configure wireless for wlan0 >> * ERROR: net.wlan0 failed to start >> * ERROR: cannot start hostapd as net.wlan0 would not start >> >> It's suppose to be an access point, not scanning for one so do you have >> any idea what I should do now? >> >> >> > Did you remove wlan0 from the /etc/conf.d/hostapd file? > > No, should I just leave it empty? INTERFACES="" What about /etc/hostapd/hostapd.conf? Do I leave it like this... interface=wlan0 ...or remove that line too? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 18:20 ` Jason Carson @ 2009-06-10 20:04 ` Norman Rieß 2009-06-10 21:38 ` Jason Carson 2009-06-11 22:13 ` Grant 0 siblings, 2 replies; 41+ messages in thread From: Norman Rieß @ 2009-06-10 20:04 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: >> Jason Carson schrieb: >> >>> Thanks for the clarification Norman :-) >>> >>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >>> booted >>> up and all the services are working the way they should, however I am >>> having a problem getting hostapd to start. Here is the error I get when >>> I >>> tried to start up hostapd... >>> >>> penguin ~ # /etc/init.d/hostapd start >>> * Bringing up interface wlan0 >>> * Configuring wireless network for wlan0 >>> * Scanning for access points >>> * no access points found >>> * Failed to configure wireless for wlan0 >>> * ERROR: net.wlan0 failed to start >>> * ERROR: cannot start hostapd as net.wlan0 would not start >>> >>> It's suppose to be an access point, not scanning for one so do you have >>> any idea what I should do now? >>> >>> >>> >>> >> Did you remove wlan0 from the /etc/conf.d/hostapd file? >> >> >> > No, should I just leave it empty? > INTERFACES="" > > What about /etc/hostapd/hostapd.conf? > Do I leave it like this... > interface=wlan0 > ...or remove that line too? > > INTERFACES should at least contain the bridge device. The wired NIC does not hurt either. In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device it has to initialize, so leave it like this. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 20:04 ` Norman Rieß @ 2009-06-10 21:38 ` Jason Carson 2009-06-10 23:33 ` Norman Rieß 2009-06-11 22:13 ` Grant 1 sibling, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-10 21:38 UTC (permalink / raw To: gentoo-user > Jason Carson schrieb: >>> Jason Carson schrieb: >>> >>>> Thanks for the clarification Norman :-) >>>> >>>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >>>> booted >>>> up and all the services are working the way they should, however I am >>>> having a problem getting hostapd to start. Here is the error I get >>>> when >>>> I >>>> tried to start up hostapd... >>>> >>>> penguin ~ # /etc/init.d/hostapd start >>>> * Bringing up interface wlan0 >>>> * Configuring wireless network for wlan0 >>>> * Scanning for access points >>>> * no access points found >>>> * Failed to configure wireless for wlan0 >>>> * ERROR: net.wlan0 failed to start >>>> * ERROR: cannot start hostapd as net.wlan0 would not start >>>> >>>> It's suppose to be an access point, not scanning for one so do you >>>> have >>>> any idea what I should do now? >>>> >>>> >>>> >>>> >>> Did you remove wlan0 from the /etc/conf.d/hostapd file? >>> >>> >>> >> No, should I just leave it empty? >> INTERFACES="" >> >> What about /etc/hostapd/hostapd.conf? >> Do I leave it like this... >> interface=wlan0 >> ...or remove that line too? >> >> > INTERFACES should at least contain the bridge device. The wired NIC does > not hurt either. > In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which > device it has to initialize, so leave it like this. > > Alright, I have done everything you have suggested but when hostapd tries to start I am getting this error... penguin ~ # /etc/init.d/hostapd start * Starting hostapd... Configuration file: /etc/hostapd/hostapd.conf Failed to set interface wlan0 to master mode. nl80211 driver initialization failed. ELOOP: remaining socket: sock=5 eloop_data=0x80f1a38 user_data=(nil) handler=0x8091790 * start-stop-daemon: failed to start `/usr/sbin/hostapd' [ !! ] * ERROR: hostapd failed to start Do you have any idea why this is happening? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 21:38 ` Jason Carson @ 2009-06-10 23:33 ` Norman Rieß 2009-06-10 23:51 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-10 23:33 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: > Alright, I have done everything you have suggested but when hostapd tries > to start I am getting this error... > > penguin ~ # /etc/init.d/hostapd start > * Starting hostapd... > Configuration file: /etc/hostapd/hostapd.conf > Failed to set interface wlan0 to master mode. > nl80211 driver initialization failed. > ELOOP: remaining socket: sock=5 eloop_data=0x80f1a38 user_data=(nil) > handler=0x8091790 > * start-stop-daemon: failed to start `/usr/sbin/hostapd' > [ !! ] > * ERROR: hostapd failed to start > > Do you have any idea why this is happening? > > > Not quite... What kernelsettings do you activate for you wlan? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 23:33 ` Norman Rieß @ 2009-06-10 23:51 ` Jason Carson 2009-06-11 1:34 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Jason Carson @ 2009-06-10 23:51 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 1000 bytes --] > Jason Carson schrieb: >> Alright, I have done everything you have suggested but when hostapd >> tries >> to start I am getting this error... >> >> penguin ~ # /etc/init.d/hostapd start >> * Starting hostapd... >> Configuration file: /etc/hostapd/hostapd.conf >> Failed to set interface wlan0 to master mode. >> nl80211 driver initialization failed. >> ELOOP: remaining socket: sock=5 eloop_data=0x80f1a38 user_data=(nil) >> handler=0x8091790 >> * start-stop-daemon: failed to start `/usr/sbin/hostapd' >> [ !! ] >> * ERROR: hostapd failed to start >> >> Do you have any idea why this is happening? >> >> >> > Not quite... > What kernelsettings do you activate for you wlan? > > I used the kernel settings mentioned here... http://linuxwireless.org/en/users/Drivers/ath5k#Enabling_ath5k ...but I built everything directly into the kernel, NOT as modules. I have attached my .config to this email so you can see if I am missing anything. [-- Attachment #2: kernel.config --] [-- Type: application/octet-stream, Size: 44445 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29.4 # Wed Jun 10 17:22:14 2009 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_RT_GROUP_SCHED is not set CONFIG_USER_SCHED=y # CONFIG_CGROUP_SCHED is not set # CONFIG_CGROUPS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y # CONFIG_RELAY is not set CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_IPC_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_NET_NS is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_COMPAT_BRK=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_BLK_DEV_BSG is not set # CONFIG_BLK_DEV_INTEGRITY is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # CONFIG_FREEZER is not set # # Processor type and features # # CONFIG_NO_HZ is not set # CONFIG_HIGH_RES_TIMERS is not set CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_VSMP is not set # CONFIG_X86_RDC321X is not set CONFIG_SCHED_OMIT_FRAME_POINTER=y # CONFIG_PARAVIRT_GUEST is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set CONFIG_MK7=y # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_GENERIC=y CONFIG_X86_CPU=y CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_USE_3DNOW=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_CYRIX_32=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR_32=y CONFIG_CPU_SUP_TRANSMETA_32=y CONFIG_CPU_SUP_UMC_32=y # CONFIG_X86_DS is not set # CONFIG_HPET_TIMER is not set CONFIG_DMI=y # CONFIG_IOMMU_HELPER is not set # CONFIG_IOMMU_API is not set CONFIG_NR_CPUS=1 CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set CONFIG_X86_CPUID=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_HIGHMEM=y # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_PHYS_ADDR_T_64BIT is not set CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_UNEVICTABLE_LRU=y # CONFIG_HIGHPTE is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set # CONFIG_X86_PAT is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=250 # CONFIG_SCHED_HRTICK is not set # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x100000 # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x100000 CONFIG_COMPAT_VDSO=y # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management and ACPI options # # CONFIG_PM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_IDLE is not set # # Bus options (PCI etc.) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set # CONFIG_PCI_GOOLPC is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_DOMAINS=y # CONFIG_PCIEPORTBUS is not set # CONFIG_ARCH_SUPPORTS_MSI is not set CONFIG_PCI_LEGACY=y # CONFIG_PCI_STUB is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # CONFIG_OLPC is not set # CONFIG_PCCARD is not set # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set CONFIG_HAVE_AOUT=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y CONFIG_HAVE_ATOMIC_IOMAP=y CONFIG_NET=y # # Networking options # CONFIG_COMPAT_NET_DEV_OPS=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y # CONFIG_XFRM_USER is not set # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y # CONFIG_IP_ROUTE_MULTIPATH is not set CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set # CONFIG_INET_TUNNEL is not set CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y CONFIG_INET_XFRM_MODE_BEET=y # CONFIG_INET_LRO is not set CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set # CONFIG_IPV6 is not set # CONFIG_NETWORK_SECMARK is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=y # # Core Netfilter Configuration # # CONFIG_NETFILTER_NETLINK_QUEUE is not set # CONFIG_NETFILTER_NETLINK_LOG is not set CONFIG_NF_CONNTRACK=y # CONFIG_NF_CT_ACCT is not set # CONFIG_NF_CONNTRACK_MARK is not set # CONFIG_NF_CONNTRACK_EVENTS is not set # CONFIG_NF_CT_PROTO_DCCP is not set # CONFIG_NF_CT_PROTO_SCTP is not set # CONFIG_NF_CT_PROTO_UDPLITE is not set # CONFIG_NF_CONNTRACK_AMANDA is not set # CONFIG_NF_CONNTRACK_FTP is not set # CONFIG_NF_CONNTRACK_H323 is not set # CONFIG_NF_CONNTRACK_IRC is not set # CONFIG_NF_CONNTRACK_NETBIOS_NS is not set # CONFIG_NF_CONNTRACK_PPTP is not set # CONFIG_NF_CONNTRACK_SANE is not set # CONFIG_NF_CONNTRACK_SIP is not set # CONFIG_NF_CONNTRACK_TFTP is not set # CONFIG_NF_CT_NETLINK is not set CONFIG_NETFILTER_XTABLES=y # CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set # CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set # CONFIG_NETFILTER_XT_TARGET_MARK is not set # CONFIG_NETFILTER_XT_TARGET_NFLOG is not set # CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set # CONFIG_NETFILTER_XT_TARGET_RATEEST is not set # CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set # CONFIG_NETFILTER_XT_MATCH_COMMENT is not set # CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set # CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set # CONFIG_NETFILTER_XT_MATCH_CONNMARK is not set CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y # CONFIG_NETFILTER_XT_MATCH_DCCP is not set # CONFIG_NETFILTER_XT_MATCH_DSCP is not set # CONFIG_NETFILTER_XT_MATCH_ESP is not set # CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set # CONFIG_NETFILTER_XT_MATCH_HELPER is not set # CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set # CONFIG_NETFILTER_XT_MATCH_LENGTH is not set CONFIG_NETFILTER_XT_MATCH_LIMIT=y # CONFIG_NETFILTER_XT_MATCH_MAC is not set # CONFIG_NETFILTER_XT_MATCH_MARK is not set # CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set # CONFIG_NETFILTER_XT_MATCH_OWNER is not set # CONFIG_NETFILTER_XT_MATCH_POLICY is not set # CONFIG_NETFILTER_XT_MATCH_PHYSDEV is not set # CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set # CONFIG_NETFILTER_XT_MATCH_QUOTA is not set # CONFIG_NETFILTER_XT_MATCH_RATEEST is not set # CONFIG_NETFILTER_XT_MATCH_REALM is not set # CONFIG_NETFILTER_XT_MATCH_RECENT is not set # CONFIG_NETFILTER_XT_MATCH_SCTP is not set CONFIG_NETFILTER_XT_MATCH_STATE=y # CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set # CONFIG_NETFILTER_XT_MATCH_STRING is not set # CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set # CONFIG_NETFILTER_XT_MATCH_TIME is not set # CONFIG_NETFILTER_XT_MATCH_U32 is not set # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=y CONFIG_NF_CONNTRACK_IPV4=y CONFIG_NF_CONNTRACK_PROC_COMPAT=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=y # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_AH is not set # CONFIG_IP_NF_MATCH_ECN is not set # CONFIG_IP_NF_MATCH_TTL is not set CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y # CONFIG_IP_NF_TARGET_LOG is not set # CONFIG_IP_NF_TARGET_ULOG is not set CONFIG_NF_NAT=y CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y # CONFIG_IP_NF_TARGET_NETMAP is not set # CONFIG_IP_NF_TARGET_REDIRECT is not set # CONFIG_NF_NAT_SNMP_BASIC is not set # CONFIG_NF_NAT_FTP is not set # CONFIG_NF_NAT_IRC is not set # CONFIG_NF_NAT_TFTP is not set # CONFIG_NF_NAT_AMANDA is not set # CONFIG_NF_NAT_PPTP is not set # CONFIG_NF_NAT_H323 is not set # CONFIG_NF_NAT_SIP is not set # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_RAW is not set # CONFIG_IP_NF_ARPTABLES is not set # CONFIG_BRIDGE_NF_EBTABLES is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set CONFIG_STP=y CONFIG_BRIDGE=y # CONFIG_NET_DSA is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set CONFIG_LLC=y # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_DCB is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set # CONFIG_PHONET is not set CONFIG_FIB_RULES=y CONFIG_WIRELESS=y CONFIG_CFG80211=y # CONFIG_CFG80211_REG_DEBUG is not set CONFIG_NL80211=y CONFIG_WIRELESS_OLD_REGULATORY=y CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y # CONFIG_LIB80211 is not set CONFIG_MAC80211=y # # Rate control algorithm selection # CONFIG_MAC80211_RC_MINSTREL=y # CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel" # CONFIG_MAC80211_MESH is not set CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUG_MENU is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_SYS_HYPERVISOR is not set # CONFIG_CONNECTOR is not set # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=y # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 # CONFIG_BLK_DEV_XIP is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_ICS932S401 is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_HP_ILO is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_AT24 is not set # CONFIG_EEPROM_LEGACY is not set # CONFIG_EEPROM_93CX6 is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set CONFIG_SCSI_LOWLEVEL=y # CONFIG_ISCSI_TCP is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_HPTIOP is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_LIBFC is not set # CONFIG_FCOE is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_MVSAS is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_SRP is not set # CONFIG_SCSI_DH is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_SATA_PMP=y # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set CONFIG_SATA_VIA=y # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5535 is not set # CONFIG_PATA_CS5536 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_SCH is not set # CONFIG_MD is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # Enable only one of the two stacks, unless you know what you are doing # # CONFIG_FIREWIRE is not set # CONFIG_IEEE1394 is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_DUMMY=m # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set CONFIG_TUN=y # CONFIG_VETH is not set # CONFIG_ARCNET is not set # CONFIG_NET_ETHERNET is not set CONFIG_NETDEV_1000=y # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000E is not set # CONFIG_IP1000 is not set # CONFIG_IGB is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SIS190 is not set # CONFIG_SKGE is not set # CONFIG_SKY2 is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # CONFIG_ATL1E is not set # CONFIG_ATL1C is not set # CONFIG_JME is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set CONFIG_WLAN_80211=y # CONFIG_LIBERTAS is not set # CONFIG_LIBERTAS_THINFIRM is not set # CONFIG_AIRO is not set # CONFIG_HERMES is not set # CONFIG_ATMEL is not set # CONFIG_PRISM54 is not set # CONFIG_USB_ZD1201 is not set # CONFIG_USB_NET_RNDIS_WLAN is not set # CONFIG_RTL8180 is not set # CONFIG_RTL8187 is not set # CONFIG_ADM8211 is not set # CONFIG_MAC80211_HWSIM is not set # CONFIG_P54_COMMON is not set CONFIG_ATH5K=y # CONFIG_ATH5K_DEBUG is not set # CONFIG_ATH9K is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IWLCORE is not set # CONFIG_IWLWIFI_LEDS is not set # CONFIG_IWLAGN is not set # CONFIG_IWL3945 is not set # CONFIG_HOSTAP is not set # CONFIG_B43 is not set # CONFIG_B43LEGACY is not set # CONFIG_ZD1211RW is not set # CONFIG_RT2X00 is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set CONFIG_PPP=y CONFIG_PPP_MULTILINK=y # CONFIG_PPP_FILTER is not set CONFIG_PPP_ASYNC=y CONFIG_PPP_SYNC_TTY=y CONFIG_PPP_DEFLATE=y CONFIG_PPP_BSDCOMP=y CONFIG_PPP_MPPE=y CONFIG_PPPOE=y # CONFIG_PPPOL2TP is not set # CONFIG_SLIP is not set CONFIG_SLHC=y # CONFIG_NET_FC is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # CONFIG_INPUT_POLLDEV is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set CONFIG_DEVKMEM=y # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set CONFIG_FIX_EARLYCON_MEM=y # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # CONFIG_IPMI_HANDLER is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set CONFIG_RTC=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y CONFIG_I2C_HELPER_AUTO=y # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_ISCH is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_VIA is not set CONFIG_I2C_VIAPRO=y # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_OCORES is not set # CONFIG_I2C_SIMTEC is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Graphics adapter I2C/DDC channel drivers # # CONFIG_I2C_VOODOO3 is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_STUB is not set # CONFIG_SCx200_ACB is not set # # Miscellaneous I2C Chip support # # CONFIG_DS1682 is not set # CONFIG_SENSORS_PCF8574 is not set # CONFIG_PCF8575 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 is not set CONFIG_I2C_DEBUG_CORE=y CONFIG_I2C_DEBUG_ALGO=y CONFIG_I2C_DEBUG_BUS=y CONFIG_I2C_DEBUG_CHIP=y # CONFIG_SPI is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set # CONFIG_POWER_SUPPLY is not set CONFIG_HWMON=y CONFIG_HWMON_VID=y # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_K8TEMP is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set CONFIG_SENSORS_IT87=y # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set # CONFIG_THERMAL is not set # CONFIG_THERMAL_HWMON is not set # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_MFD_TMIO is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_REGULATOR is not set # # Multimedia devices # # # Multimedia core support # # CONFIG_VIDEO_DEV is not set # CONFIG_DVB_CORE is not set # CONFIG_VIDEO_MEDIA is not set # # Multimedia drivers # CONFIG_DAB=y # CONFIG_USB_DABUSB is not set # # Graphics support # CONFIG_AGP=y # CONFIG_AGP_ALI is not set # CONFIG_AGP_ATI is not set # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set # CONFIG_AGP_INTEL is not set # CONFIG_AGP_NVIDIA is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set CONFIG_AGP_VIA=y # CONFIG_AGP_EFFICEON is not set # CONFIG_DRM is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_CYBLA is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set CONFIG_FONT_PEARL_8x8=y CONFIG_FONT_ACORN_8x8=y CONFIG_FONT_MINI_4x6=y CONFIG_FONT_SUN8x16=y # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_SOUND is not set CONFIG_HID_SUPPORT=y CONFIG_HID=y # CONFIG_HID_DEBUG is not set # CONFIG_HIDRAW is not set # # USB Input Devices # CONFIG_USB_HID=y # CONFIG_HID_PID is not set # CONFIG_USB_HIDDEV is not set # # Special HID drivers # CONFIG_HID_COMPAT=y CONFIG_HID_A4TECH=y CONFIG_HID_APPLE=y CONFIG_HID_BELKIN=y CONFIG_HID_CHERRY=y CONFIG_HID_CHICONY=y CONFIG_HID_CYPRESS=y CONFIG_HID_EZKEY=y CONFIG_HID_GYRATION=y CONFIG_HID_LOGITECH=y # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_HID_MICROSOFT=y CONFIG_HID_MONTEREY=y CONFIG_HID_NTRIG=y CONFIG_HID_PANTHERLORD=y # CONFIG_PANTHERLORD_FF is not set CONFIG_HID_PETALYNX=y CONFIG_HID_SAMSUNG=y CONFIG_HID_SONY=y CONFIG_HID_SUNPLUS=y # CONFIG_GREENASIA_FF is not set CONFIG_HID_TOPSEED=y # CONFIG_THRUSTMASTER_FF is not set # CONFIG_ZEROPLUS_FF is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y CONFIG_USB_DEVICE_CLASS=y # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_OTG is not set CONFIG_USB_MON=y # CONFIG_USB_WUSB is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_EHCI_HCD=y # CONFIG_USB_EHCI_ROOT_HUB_TT is not set # CONFIG_USB_EHCI_TT_NEWSCHED is not set # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_OHCI_HCD is not set CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_WHCI_HCD is not set # CONFIG_USB_HWA_HCD is not set # # USB Device Class drivers # # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set # CONFIG_USB_WDM is not set # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; # # # see USB_STORAGE Help for more information # # CONFIG_USB_STORAGE is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB port drivers # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_BERRY_CHARGE is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGET is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_VST is not set # CONFIG_USB_GADGET is not set # # OTG and related infrastructure # # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # # CONFIG_LEDS_ALIX2 is not set # CONFIG_LEDS_PCA9532 is not set # CONFIG_LEDS_CLEVO_MAIL is not set # CONFIG_LEDS_PCA955X is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y # CONFIG_LEDS_TRIGGER_TIMER is not set # CONFIG_LEDS_TRIGGER_HEARTBEAT is not set # CONFIG_LEDS_TRIGGER_BACKLIGHT is not set # CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set # CONFIG_RTC_CLASS is not set # CONFIG_DMADEVICES is not set # CONFIG_UIO is not set # CONFIG_STAGING is not set CONFIG_X86_PLATFORM_DEVICES=y # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_DMIID=y # CONFIG_ISCSI_IBFT_FIND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y # CONFIG_EXT2_FS_POSIX_ACL is not set # CONFIG_EXT2_FS_SECURITY is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set # CONFIG_EXT4_FS is not set CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set CONFIG_FILE_LOCKING=y # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y # CONFIG_JOLIET is not set # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y # CONFIG_PROC_KCORE is not set CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set # CONFIG_CONFIGFS_FS is not set CONFIG_MISC_FILESYSTEMS=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_SQUASHFS is not set # CONFIG_VXFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_OMFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y # CONFIG_NFS_V3 is not set # CONFIG_NFS_V4 is not set CONFIG_NFSD=y # CONFIG_NFSD_V3 is not set # CONFIG_NFSD_V4 is not set CONFIG_LOCKD=y CONFIG_EXPORTFS=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y # CONFIG_SUNRPC_REGISTER_V4 is not set # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_RPCSEC_GSS_SPKM3 is not set CONFIG_SMB_FS=y # CONFIG_SMB_NLS_DEFAULT is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=1024 # CONFIG_MAGIC_SYSRQ is not set CONFIG_UNUSED_SYMBOLS=y # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_MEMORY_INIT=y CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_LATENCYTOP is not set CONFIG_SYSCTL_SYSCALL_CHECK=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y # # Tracers # # CONFIG_SYSPROF_TRACER is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_DYNAMIC_PRINTK_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_STRICT_DEVMEM is not set CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set # CONFIG_4KSTACKS is not set CONFIG_DOUBLEFAULT=y CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_OPTIMIZE_INLINING is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_CRYPTO=y # # Crypto core or helper # # CONFIG_CRYPTO_FIPS is not set CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y # CONFIG_CRYPTO_GF128MUL is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_CRYPTD is not set # CONFIG_CRYPTO_AUTHENC is not set # CONFIG_CRYPTO_TEST is not set # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # CONFIG_CRYPTO_CBC=m # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=y # CONFIG_CRYPTO_LRW is not set CONFIG_CRYPTO_PCBC=m # CONFIG_CRYPTO_XTS is not set # # Hash modes # CONFIG_CRYPTO_HMAC=y # CONFIG_CRYPTO_XCBC is not set # # Digest # # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_CRC32C_INTEL is not set # CONFIG_CRYPTO_MD4 is not set # CONFIG_CRYPTO_MD5 is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=y # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # # Ciphers # CONFIG_CRYPTO_AES=y # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_DES is not set # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_586 is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # # Compression # # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_LZO is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set CONFIG_CRYPTO_HW=y # CONFIG_CRYPTO_DEV_PADLOCK is not set CONFIG_CRYPTO_DEV_GEODE=m # CONFIG_CRYPTO_DEV_HIFN_795X is not set CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_VIRTUALIZATION=y # CONFIG_KVM is not set # CONFIG_LGUEST is not set # CONFIG_VIRTIO_PCI is not set # CONFIG_VIRTIO_BALLOON is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=y # CONFIG_CRC16 is not set # CONFIG_CRC_T10DIF is not set # CONFIG_CRC_ITU_T is not set CONFIG_CRC32=y # CONFIG_CRC7 is not set # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 23:51 ` Jason Carson @ 2009-06-11 1:34 ` Norman Rieß 2009-06-11 2:03 ` Jason Carson 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-11 1:34 UTC (permalink / raw To: gentoo-user Jason Carson schrieb: >> Jason Carson schrieb: >> >>> Alright, I have done everything you have suggested but when hostapd >>> tries >>> to start I am getting this error... >>> >>> penguin ~ # /etc/init.d/hostapd start >>> * Starting hostapd... >>> Configuration file: /etc/hostapd/hostapd.conf >>> Failed to set interface wlan0 to master mode. >>> nl80211 driver initialization failed. >>> ELOOP: remaining socket: sock=5 eloop_data=0x80f1a38 user_data=(nil) >>> handler=0x8091790 >>> * start-stop-daemon: failed to start `/usr/sbin/hostapd' >>> [ !! ] >>> * ERROR: hostapd failed to start >>> >>> Do you have any idea why this is happening? >>> >>> >>> >>> >> Not quite... >> What kernelsettings do you activate for you wlan? >> >> >> > I used the kernel settings mentioned here... > http://linuxwireless.org/en/users/Drivers/ath5k#Enabling_ath5k > ...but I built everything directly into the kernel, NOT as modules. > > I have attached my .config to this email so you can see if I am missing > anything. I also activated CONFIG_HOSTAP=y CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y but i think i found the real reason. I checked the 2.6.29.x ath5k base.c and found, that the AP code is still dormant. You need to apply this patch: --- linux-2.6.29/drivers/net/wireless/ath5k/base.c 2009-02-10 06:11:43.186470883 +0100 +++ linux-2.6.29/drivers/net/wireless/ath5k/base.c.old 2008-11-14 09:36:40.000000000 +0100 @@ -522,6 +501,7 @@ hw->wiphy->interface_modes = BIT(NL80211_IFTYPE_STATION) | BIT(NL80211_IFTYPE_ADHOC) | + BIT(NL80211_IFTYPE_AP) | BIT(NL80211_IFTYPE_MESH_POINT); hw->extra_tx_headroom = 2; Open the file /usr/src/linux-<yourversion>/drivers/net/wireless/ath5k/base.c, search for hw->wiphy->interface_modes and the apply the line BIT(NL80211_IFTYPE_AP) | between these lines. Rebuild and install the kernel. Background: The AP code is there, but it is not activated yet. This line activates it. I thought newer 2.6.29er kernels do not have this restriction, so i did not think of this, but apparently they do. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-11 1:34 ` Norman Rieß @ 2009-06-11 2:03 ` Jason Carson 0 siblings, 0 replies; 41+ messages in thread From: Jason Carson @ 2009-06-11 2:03 UTC (permalink / raw To: gentoo-user > Jason Carson schrieb: >>> Jason Carson schrieb: >>> >>>> Alright, I have done everything you have suggested but when hostapd >>>> tries >>>> to start I am getting this error... >>>> >>>> penguin ~ # /etc/init.d/hostapd start >>>> * Starting hostapd... >>>> Configuration file: /etc/hostapd/hostapd.conf >>>> Failed to set interface wlan0 to master mode. >>>> nl80211 driver initialization failed. >>>> ELOOP: remaining socket: sock=5 eloop_data=0x80f1a38 user_data=(nil) >>>> handler=0x8091790 >>>> * start-stop-daemon: failed to start `/usr/sbin/hostapd' >>>> [ !! ] >>>> * ERROR: hostapd failed to start >>>> >>>> Do you have any idea why this is happening? >>>> >>>> >>>> >>>> >>> Not quite... >>> What kernelsettings do you activate for you wlan? >>> >>> >>> >> I used the kernel settings mentioned here... >> http://linuxwireless.org/en/users/Drivers/ath5k#Enabling_ath5k >> ...but I built everything directly into the kernel, NOT as modules. >> >> I have attached my .config to this email so you can see if I am missing >> anything. > I also activated > > CONFIG_HOSTAP=y > CONFIG_HOSTAP_FIRMWARE=y > CONFIG_HOSTAP_FIRMWARE_NVRAM=y > > but i think i found the real reason. > I checked the 2.6.29.x ath5k base.c and found, that the AP code is still > dormant. > You need to apply this patch: > > --- linux-2.6.29/drivers/net/wireless/ath5k/base.c 2009-02-10 > 06:11:43.186470883 +0100 > +++ linux-2.6.29/drivers/net/wireless/ath5k/base.c.old > 2008-11-14 09:36:40.000000000 +0100 > @@ -522,6 +501,7 @@ > hw->wiphy->interface_modes = > BIT(NL80211_IFTYPE_STATION) | > BIT(NL80211_IFTYPE_ADHOC) | > + BIT(NL80211_IFTYPE_AP) | > BIT(NL80211_IFTYPE_MESH_POINT); > > hw->extra_tx_headroom = 2; > > Open the file > /usr/src/linux-<yourversion>/drivers/net/wireless/ath5k/base.c, search for > > hw->wiphy->interface_modes > > and the apply the line > > BIT(NL80211_IFTYPE_AP) | > > between these lines. > Rebuild and install the kernel. > > Background: The AP code is there, but it is not activated yet. This line > activates it. > I thought newer 2.6.29er kernels do not have this restriction, so i did > not think of this, but apparently they do. > > That did the trick. I applied that line, rebuilt & installed the kernel, rebooted and hostapd loaded without any errors. Thanks you very much for your help :-) ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-10 20:04 ` Norman Rieß 2009-06-10 21:38 ` Jason Carson @ 2009-06-11 22:13 ` Grant 2009-06-11 23:32 ` Norman Rieß 1 sibling, 1 reply; 41+ messages in thread From: Grant @ 2009-06-11 22:13 UTC (permalink / raw To: gentoo-user >>>> Thanks for the clarification Norman :-) >>>> >>>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >>>> booted >>>> up and all the services are working the way they should, however I am >>>> having a problem getting hostapd to start. Here is the error I get when >>>> I >>>> tried to start up hostapd... >>>> >>>> penguin ~ # /etc/init.d/hostapd start >>>> * Bringing up interface wlan0 >>>> * Configuring wireless network for wlan0 >>>> * Scanning for access points >>>> * no access points found >>>> * Failed to configure wireless for wlan0 >>>> * ERROR: net.wlan0 failed to start >>>> * ERROR: cannot start hostapd as net.wlan0 would not start >>>> >>>> It's suppose to be an access point, not scanning for one so do you have >>>> any idea what I should do now? >>>> >>>> >>>> >>>> >>> >>> Did you remove wlan0 from the /etc/conf.d/hostapd file? >>> >>> >>> >> >> No, should I just leave it empty? >> INTERFACES="" >> >> What about /etc/hostapd/hostapd.conf? >> Do I leave it like this... >> interface=wlan0 >> ...or remove that line too? >> >> > > INTERFACES should at least contain the bridge device. The wired NIC does not > hurt either. > In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device it > has to initialize, so leave it like this. I've almost got this working, but I don't know what to include in the /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 device or configuration. Do I need one? If I leave INTERFACES empty and I don't start net.wlan0, I don't have a way to define the IP address for the AP, and shorewall's "loc" zone is empty because net.wlan0 hasn't started. - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-11 22:13 ` Grant @ 2009-06-11 23:32 ` Norman Rieß 2009-06-11 23:38 ` Grant 2009-06-12 5:46 ` Graham Murray 0 siblings, 2 replies; 41+ messages in thread From: Norman Rieß @ 2009-06-11 23:32 UTC (permalink / raw To: gentoo-user Grant schrieb: >>>>> Thanks for the clarification Norman :-) >>>>> >>>>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >>>>> booted >>>>> up and all the services are working the way they should, however I am >>>>> having a problem getting hostapd to start. Here is the error I get when >>>>> I >>>>> tried to start up hostapd... >>>>> >>>>> penguin ~ # /etc/init.d/hostapd start >>>>> * Bringing up interface wlan0 >>>>> * Configuring wireless network for wlan0 >>>>> * Scanning for access points >>>>> * no access points found >>>>> * Failed to configure wireless for wlan0 >>>>> * ERROR: net.wlan0 failed to start >>>>> * ERROR: cannot start hostapd as net.wlan0 would not start >>>>> >>>>> It's suppose to be an access point, not scanning for one so do you have >>>>> any idea what I should do now? >>>>> >>>>> >>>>> >>>>> >>>>> >>>> Did you remove wlan0 from the /etc/conf.d/hostapd file? >>>> >>>> >>>> >>>> >>> No, should I just leave it empty? >>> INTERFACES="" >>> >>> What about /etc/hostapd/hostapd.conf? >>> Do I leave it like this... >>> interface=wlan0 >>> ...or remove that line too? >>> >>> >>> >> INTERFACES should at least contain the bridge device. The wired NIC does not >> hurt either. >> In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device it >> has to initialize, so leave it like this. >> > > I've almost got this working, but I don't know what to include in the > /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 > device or configuration. Do I need one? If I leave INTERFACES empty > and I don't start net.wlan0, I don't have a way to define the IP > address for the AP, and shorewall's "loc" zone is empty because > net.wlan0 hasn't started. > > - Grant > > What do you want to do with your accesspoint. You will need a bridge to a wired network if you want your ap attached to that wired network. This is quite usual though... Without a bridge to a wired network, only the wlan systems are connected and can not connect to your wired systems. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-11 23:32 ` Norman Rieß @ 2009-06-11 23:38 ` Grant 2009-06-11 23:59 ` [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) Stroller 2009-06-12 0:42 ` [gentoo-user] Atheros kernel driver and my wireless access point setup Norman Rieß 2009-06-12 5:46 ` Graham Murray 1 sibling, 2 replies; 41+ messages in thread From: Grant @ 2009-06-11 23:38 UTC (permalink / raw To: gentoo-user >>>>>> Thanks for the clarification Norman :-) >>>>>> >>>>>> ok, I removed net.wlan0 so it doesn't start up anymore. My computer >>>>>> booted >>>>>> up and all the services are working the way they should, however I am >>>>>> having a problem getting hostapd to start. Here is the error I get >>>>>> when >>>>>> I >>>>>> tried to start up hostapd... >>>>>> >>>>>> penguin ~ # /etc/init.d/hostapd start >>>>>> * Bringing up interface wlan0 >>>>>> * Configuring wireless network for wlan0 >>>>>> * Scanning for access points >>>>>> * no access points found >>>>>> * Failed to configure wireless for wlan0 >>>>>> * ERROR: net.wlan0 failed to start >>>>>> * ERROR: cannot start hostapd as net.wlan0 would not start >>>>>> >>>>>> It's suppose to be an access point, not scanning for one so do you >>>>>> have >>>>>> any idea what I should do now? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> Did you remove wlan0 from the /etc/conf.d/hostapd file? >>>>> >>>>> >>>>> >>>>> >>>> >>>> No, should I just leave it empty? >>>> INTERFACES="" >>>> >>>> What about /etc/hostapd/hostapd.conf? >>>> Do I leave it like this... >>>> interface=wlan0 >>>> ...or remove that line too? >>>> >>>> >>>> >>> >>> INTERFACES should at least contain the bridge device. The wired NIC does >>> not >>> hurt either. >>> In /etc/hostapd/hostapd.conf wlan0 is needed to tell hostapd which device >>> it >>> has to initialize, so leave it like this. >>> >> >> I've almost got this working, but I don't know what to include in the >> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 >> device or configuration. Do I need one? If I leave INTERFACES empty >> and I don't start net.wlan0, I don't have a way to define the IP >> address for the AP, and shorewall's "loc" zone is empty because >> net.wlan0 hasn't started. >> >> - Grant >> >> > > What do you want to do with your accesspoint. You will need a bridge to a > wired network if you want your ap attached to that wired network. This is > quite usual though... > Without a bridge to a wired network, only the wlan systems are connected and > can not connect to your wired systems. That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right now I just want to get wlan0 working. Do you know how to do that? I can't start net.wlan0 because it chokes on master mode, so I don't know how to specify an IP for the AP or how to fill shorewall's "loc" zone as that is normally filled by net.wlan0. - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) 2009-06-11 23:38 ` Grant @ 2009-06-11 23:59 ` Stroller 2009-06-12 2:10 ` Grant 2009-06-12 0:42 ` [gentoo-user] Atheros kernel driver and my wireless access point setup Norman Rieß 1 sibling, 1 reply; 41+ messages in thread From: Stroller @ 2009-06-11 23:59 UTC (permalink / raw To: gentoo-user On 12 Jun 2009, at 00:38, Grant wrote: >>> ... >>> I've almost got this working, but I don't know what to include in >>> the >>> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 >>> device or configuration. Do I need one? If I leave INTERFACES >>> empty >>> and I don't start net.wlan0, I don't have a way to define the IP >>> address for the AP, and shorewall's "loc" zone is empty because >>> net.wlan0 hasn't started. >> >> What do you want to do with your accesspoint. You will need a >> bridge to a >> wired network if you want your ap attached to that wired network. >> This is >> quite usual though... >> Without a bridge to a wired network, only the wlan systems are >> connected and >> can not connect to your wired systems. > > That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right > now I just want to get wlan0 working. Do you know how to do that? I > can't start net.wlan0 because it chokes on master mode, so I don't > know how to specify an IP for the AP or how to fill shorewall's "loc" > zone as that is normally filled by net.wlan0. Hi there, I haven't used Shorewall, but for this you probably want to use bridging. I fear that may not be available in Shorewall's UI. I originally wrote <http://en.gentoo-wiki.com/wiki/Wireless/ Access_point>, but that was some years ago now. It has had many contributions since, but I have no idea if it's up to date. Anyway, using the "simple NAT-forwarding setup" described in that article (surely possible in Shorewall) the wireless laptop can access the internet and wired PCs on the LAN. However it is not possible for wired PCs to (say) browse to file shares on the laptop without port- forwarding - because you use a NAT, you have exactly the same problem as accessing your home-server from the office. Bridging brings the wireless clients *seamlessly* into the wired LAN - they behave exactly like the wired clients do. One can install Apache on the wireless laptop and immediately connect to it from a wired PC. This is how all standalone ADSL wireless routers (eg Netgear DG834G) operate. I can't be of much practical help, as I have for some time been using a Fon access-point, which is plugged into a network switch near my desk and which gives me NATted wifi. It works, but I sure do miss teleportd <http://abyssoft.com/software/teleport/>, which is crippled without bridging. Stroller. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) 2009-06-11 23:59 ` [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) Stroller @ 2009-06-12 2:10 ` Grant 0 siblings, 0 replies; 41+ messages in thread From: Grant @ 2009-06-12 2:10 UTC (permalink / raw To: gentoo-user >>>> I've almost got this working, but I don't know what to include in the >>>> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 >>>> device or configuration. Do I need one? If I leave INTERFACES empty >>>> and I don't start net.wlan0, I don't have a way to define the IP >>>> address for the AP, and shorewall's "loc" zone is empty because >>>> net.wlan0 hasn't started. >>> >>> What do you want to do with your accesspoint. You will need a bridge to a >>> wired network if you want your ap attached to that wired network. This is >>> quite usual though... >>> Without a bridge to a wired network, only the wlan systems are connected >>> and >>> can not connect to your wired systems. >> >> That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right >> now I just want to get wlan0 working. Do you know how to do that? I >> can't start net.wlan0 because it chokes on master mode, so I don't >> know how to specify an IP for the AP or how to fill shorewall's "loc" >> zone as that is normally filled by net.wlan0. > > Hi there, > > I haven't used Shorewall, but for this you probably want to use bridging. I > fear that may not be available in Shorewall's UI. > > I originally wrote <http://en.gentoo-wiki.com/wiki/Wireless/Access_point>, > but that was some years ago now. It has had many contributions since, but I > have no idea if it's up to date. > > Anyway, using the "simple NAT-forwarding setup" described in that article > (surely possible in Shorewall) the wireless laptop can access the internet > and wired PCs on the LAN. However it is not possible for wired PCs to (say) > browse to file shares on the laptop without port-forwarding - because you > use a NAT, you have exactly the same problem as accessing your home-server > from the office. > > Bridging brings the wireless clients *seamlessly* into the wired LAN - they > behave exactly like the wired clients do. One can install Apache on the > wireless laptop and immediately connect to it from a wired PC. This is how > all standalone ADSL wireless routers (eg Netgear DG834G) operate. > > I can't be of much practical help, as I have for some time been using a Fon > access-point, which is plugged into a network switch near my desk and which > gives me NATted wifi. It works, but I sure do miss teleportd > <http://abyssoft.com/software/teleport/>, which is crippled without > bridging. > > Stroller. Thanks Stroller. I'm into bridging eth1 and wlan0, but the truth is I don't even have an eth1 right now, although I plan to in the future. When I get eth1 going I'll bridge em for sure. - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-11 23:38 ` Grant 2009-06-11 23:59 ` [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) Stroller @ 2009-06-12 0:42 ` Norman Rieß 2009-06-12 2:04 ` Grant 1 sibling, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-12 0:42 UTC (permalink / raw To: gentoo-user >> What do you want to do with your accesspoint. You will need a bridge to a >> wired network if you want your ap attached to that wired network. This is >> quite usual though... >> Without a bridge to a wired network, only the wlan systems are connected and >> can not connect to your wired systems. >> > > That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right > now I just want to get wlan0 working. Do you know how to do that? I > can't start net.wlan0 because it chokes on master mode, so I don't > know how to specify an IP for the AP or how to fill shorewall's "loc" > zone as that is normally filled by net.wlan0. > > - Grant > > Leave INTERFACES blank. As you keep the networks seperated, hostapd does not depend on any other devices. wlan0 is initialized by hostapd. So you are good to go. The accesspoint itself, so to say the wlan part does not have any IP adress, at it is merely a connectionpoint for normal wlan systems. The IP adress to your device however is defined by the other nics. In your case eth1. For the shorewall business, you have to tell, what you want to do with shorewall exactely. I dare say you have a wlan zone as your AP and a loc zone with eth1. As i am using bridging i can not tell you if and how shorewall responds. But if you want to keep eth1 an wlan0 seperate, what so you need shorewall for? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 0:42 ` [gentoo-user] Atheros kernel driver and my wireless access point setup Norman Rieß @ 2009-06-12 2:04 ` Grant 2009-06-12 10:35 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Grant @ 2009-06-12 2:04 UTC (permalink / raw To: gentoo-user >>> What do you want to do with your accesspoint. You will need a bridge to a >>> wired network if you want your ap attached to that wired network. This is >>> quite usual though... >>> Without a bridge to a wired network, only the wlan systems are connected >>> and >>> can not connect to your wired systems. >>> >> >> That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right >> now I just want to get wlan0 working. Do you know how to do that? I >> can't start net.wlan0 because it chokes on master mode, so I don't >> know how to specify an IP for the AP or how to fill shorewall's "loc" >> zone as that is normally filled by net.wlan0. >> >> - Grant >> >> > > Leave INTERFACES blank. As you keep the networks seperated, hostapd does not > depend on any other devices. > wlan0 is initialized by hostapd. So you are good to go. > The accesspoint itself, so to say the wlan part does not have any IP adress, > at it is merely a connectionpoint for normal wlan systems. The IP adress to > your device however is defined by the other nics. In your case eth1. I don't have eth1 set up yet. For now I just want eth0 on the WAN and wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a local IP address for my LAN somewhere right? > For the shorewall business, you have to tell, what you want to do with > shorewall exactely. > I dare say you have a wlan zone as your AP and a loc zone with eth1. As i am > using bridging i can not tell you if and how shorewall responds. > But if you want to keep eth1 an wlan0 seperate, what so you need shorewall > for? Since the AP system is also the router, I use shorewall for NAT, port closing, port forwarding, and packet shaping. shorewall gives an empty loc zone error if I don't have net.wlan0 started because wlan0 is the only loc interface. - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 2:04 ` Grant @ 2009-06-12 10:35 ` Norman Rieß 2009-06-12 13:17 ` Grant 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-12 10:35 UTC (permalink / raw To: gentoo-user Grant schrieb: >> Leave INTERFACES blank. As you keep the networks seperated, hostapd does not >> depend on any other devices. >> wlan0 is initialized by hostapd. So you are good to go. >> The accesspoint itself, so to say the wlan part does not have any IP adress, >> at it is merely a connectionpoint for normal wlan systems. The IP adress to >> your device however is defined by the other nics. In your case eth1. >> > > I don't have eth1 set up yet. For now I just want eth0 on the WAN and > wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a > local IP address for my LAN somewhere right? > > wlan0 in master mode does _not_ have an IP adress. So far eth0 is the only ip adress your device has. If you do not spezify a local ip adress on eth1, you will not have any local ip adress. >> For the shorewall business, you have to tell, what you want to do with >> shorewall exactely. >> I dare say you have a wlan zone as your AP and a loc zone with eth1. As i am >> using bridging i can not tell you if and how shorewall responds. >> But if you want to keep eth1 an wlan0 seperate, what so you need shorewall >> for? >> > > Since the AP system is also the router, I use shorewall for NAT, port > closing, port forwarding, and packet shaping. shorewall gives an > empty loc zone error if I don't have net.wlan0 started because wlan0 > is the only loc interface. > > - Grant > > You can let shorewall depend on hostapd, so your shorewall starts after hostapd and your wlan0. Check the "depend()" section in shorewalls rc-script. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 10:35 ` Norman Rieß @ 2009-06-12 13:17 ` Grant 2009-06-12 15:24 ` Norman Rieß 2009-06-12 15:47 ` Stroller 0 siblings, 2 replies; 41+ messages in thread From: Grant @ 2009-06-12 13:17 UTC (permalink / raw To: gentoo-user >>> Leave INTERFACES blank. As you keep the networks seperated, hostapd does >>> not >>> depend on any other devices. >>> wlan0 is initialized by hostapd. So you are good to go. >>> The accesspoint itself, so to say the wlan part does not have any IP >>> adress, >>> at it is merely a connectionpoint for normal wlan systems. The IP adress >>> to >>> your device however is defined by the other nics. In your case eth1. >>> >> >> I don't have eth1 set up yet. For now I just want eth0 on the WAN and >> wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a >> local IP address for my LAN somewhere right? >> >> > > wlan0 in master mode does _not_ have an IP adress. So far eth0 is the only > ip adress your device has. > If you do not spezify a local ip adress on eth1, you will not have any local > ip adress. I'm very confused. I've been running wlan0 in master mode for about 3 years with IP 192.168.0.1 and no eth1. Here was my entire /etc/conf.d/net: config_eth0=( "dhcp" ) mode_wlan0=( "master" ) essid_wlan0=( "networkname" ) channel_wlan0=( "11" ) config_wlan0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" ) All I'm trying to do is switch wireless drivers from madwifi-ng to the in-kernel ath5k. With madwifi-ng, I started net.wlan0, started hostapd, and started shorewall and everything worked perfectly. Now with ath5k, net.wlan0 won't start in master mode. This causes 2 problems: 1. I can't specify a local IP for wlan0 in /etc/conf.d/net like I've been doing for years. 2. shorewall checks whether or not net.wlan0 has started because wlan0 is the only device in zone loc, so shorewall won't start. So I'm required to have an eth1 because I'm switching from madwifi-ng to ath5k? That doesn't seem right. >>> For the shorewall business, you have to tell, what you want to do with >>> shorewall exactely. >>> I dare say you have a wlan zone as your AP and a loc zone with eth1. As i >>> am >>> using bridging i can not tell you if and how shorewall responds. >>> But if you want to keep eth1 an wlan0 seperate, what so you need >>> shorewall >>> for? >>> >> >> Since the AP system is also the router, I use shorewall for NAT, port >> closing, port forwarding, and packet shaping. shorewall gives an >> empty loc zone error if I don't have net.wlan0 started because wlan0 >> is the only loc interface. >> >> - Grant >> >> > > You can let shorewall depend on hostapd, so your shorewall starts after > hostapd and your wlan0. > Check the "depend()" section in shorewalls rc-script. I'm confused here too. shorewall seems to be checking whether or not net.wlan0 has started, not whether the wlan0 interface is up. Trying to start shorewall after hostapd has started results in the same error described above because net.wlan0 hasn't been started. - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 13:17 ` Grant @ 2009-06-12 15:24 ` Norman Rieß 2009-06-12 15:38 ` Grant 2009-06-12 15:47 ` Stroller 1 sibling, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-12 15:24 UTC (permalink / raw To: gentoo-user Grant schrieb: >>>> Leave INTERFACES blank. As you keep the networks seperated, hostapd does >>>> not >>>> depend on any other devices. >>>> wlan0 is initialized by hostapd. So you are good to go. >>>> The accesspoint itself, so to say the wlan part does not have any IP >>>> adress, >>>> at it is merely a connectionpoint for normal wlan systems. The IP adress >>>> to >>>> your device however is defined by the other nics. In your case eth1. >>>> >>>> >>> I don't have eth1 set up yet. For now I just want eth0 on the WAN and >>> wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a >>> local IP address for my LAN somewhere right? >>> >>> >>> >> wlan0 in master mode does _not_ have an IP adress. So far eth0 is the only >> ip adress your device has. >> If you do not spezify a local ip adress on eth1, you will not have any local >> ip adress. >> > > I'm very confused. I've been running wlan0 in master mode for about 3 > years with IP 192.168.0.1 and no eth1. Here was my entire > /etc/conf.d/net: > > config_eth0=( "dhcp" ) > mode_wlan0=( "master" ) > essid_wlan0=( "networkname" ) > channel_wlan0=( "11" ) > config_wlan0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" ) > > All I'm trying to do is switch wireless drivers from madwifi-ng to the > in-kernel ath5k. With madwifi-ng, I started net.wlan0, started > hostapd, and started shorewall and everything worked perfectly. Now > with ath5k, net.wlan0 won't start in master mode. This causes 2 > problems: > > 1. I can't specify a local IP for wlan0 in /etc/conf.d/net like I've > been doing for years. > 2. shorewall checks whether or not net.wlan0 has started because wlan0 > is the only device in zone loc, so shorewall won't start. > > So I'm required to have an eth1 because I'm switching from madwifi-ng > to ath5k? That doesn't seem right. > > >>>> For the shorewall business, you have to tell, what you want to do with >>>> shorewall exactely. >>>> I dare say you have a wlan zone as your AP and a loc zone with eth1. As i >>>> am >>>> using bridging i can not tell you if and how shorewall responds. >>>> But if you want to keep eth1 an wlan0 seperate, what so you need >>>> shorewall >>>> for? >>>> >>>> >>> Since the AP system is also the router, I use shorewall for NAT, port >>> closing, port forwarding, and packet shaping. shorewall gives an >>> empty loc zone error if I don't have net.wlan0 started because wlan0 >>> is the only loc interface. >>> >>> - Grant >>> >>> >>> >> You can let shorewall depend on hostapd, so your shorewall starts after >> hostapd and your wlan0. >> Check the "depend()" section in shorewalls rc-script. >> > > I'm confused here too. shorewall seems to be checking whether or not > net.wlan0 has started, not whether the wlan0 interface is up. Trying > to start shorewall after hostapd has started results in the same error > described above because net.wlan0 hasn't been started. > > - Grant > > Well, madwifi-ng is a matured project with an insanely great featureset. ath5k ap mode till this day is not activated in the kernel. You have to activate it with a code patch, the gentoo rc-script can not cope with it yet. hostapd needs to be a new version and has to initialize the device itself. Of course you can not expect the same features and easy to use behaviour from such an experimental software. You seem to have a working setup, which suits your needs. Unless you have a serious reason i would not change a running and supported system. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 15:24 ` Norman Rieß @ 2009-06-12 15:38 ` Grant 2009-06-12 15:56 ` Stroller 0 siblings, 1 reply; 41+ messages in thread From: Grant @ 2009-06-12 15:38 UTC (permalink / raw To: gentoo-user >>>>> Leave INTERFACES blank. As you keep the networks seperated, hostapd >>>>> does >>>>> not >>>>> depend on any other devices. >>>>> wlan0 is initialized by hostapd. So you are good to go. >>>>> The accesspoint itself, so to say the wlan part does not have any IP >>>>> adress, >>>>> at it is merely a connectionpoint for normal wlan systems. The IP >>>>> adress >>>>> to >>>>> your device however is defined by the other nics. In your case eth1. >>>>> >>>>> >>>> >>>> I don't have eth1 set up yet. For now I just want eth0 on the WAN and >>>> wlan0 on the LAN. eth0 dhcp's from my ISP, but I need to specify a >>>> local IP address for my LAN somewhere right? >>>> >>>> >>>> >>> >>> wlan0 in master mode does _not_ have an IP adress. So far eth0 is the >>> only >>> ip adress your device has. >>> If you do not spezify a local ip adress on eth1, you will not have any >>> local >>> ip adress. >>> >> >> I'm very confused. I've been running wlan0 in master mode for about 3 >> years with IP 192.168.0.1 and no eth1. Here was my entire >> /etc/conf.d/net: >> >> config_eth0=( "dhcp" ) >> mode_wlan0=( "master" ) >> essid_wlan0=( "networkname" ) >> channel_wlan0=( "11" ) >> config_wlan0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" >> ) >> >> All I'm trying to do is switch wireless drivers from madwifi-ng to the >> in-kernel ath5k. With madwifi-ng, I started net.wlan0, started >> hostapd, and started shorewall and everything worked perfectly. Now >> with ath5k, net.wlan0 won't start in master mode. This causes 2 >> problems: >> >> 1. I can't specify a local IP for wlan0 in /etc/conf.d/net like I've >> been doing for years. >> 2. shorewall checks whether or not net.wlan0 has started because wlan0 >> is the only device in zone loc, so shorewall won't start. >> >> So I'm required to have an eth1 because I'm switching from madwifi-ng >> to ath5k? That doesn't seem right. >> >> >>>>> >>>>> For the shorewall business, you have to tell, what you want to do with >>>>> shorewall exactely. >>>>> I dare say you have a wlan zone as your AP and a loc zone with eth1. As >>>>> i >>>>> am >>>>> using bridging i can not tell you if and how shorewall responds. >>>>> But if you want to keep eth1 an wlan0 seperate, what so you need >>>>> shorewall >>>>> for? >>>>> >>>>> >>>> >>>> Since the AP system is also the router, I use shorewall for NAT, port >>>> closing, port forwarding, and packet shaping. shorewall gives an >>>> empty loc zone error if I don't have net.wlan0 started because wlan0 >>>> is the only loc interface. >>>> >>>> - Grant >>>> >>>> >>>> >>> >>> You can let shorewall depend on hostapd, so your shorewall starts after >>> hostapd and your wlan0. >>> Check the "depend()" section in shorewalls rc-script. >>> >> >> I'm confused here too. shorewall seems to be checking whether or not >> net.wlan0 has started, not whether the wlan0 interface is up. Trying >> to start shorewall after hostapd has started results in the same error >> described above because net.wlan0 hasn't been started. >> >> - Grant >> >> > > Well, madwifi-ng is a matured project with an insanely great featureset. > ath5k ap mode till this day is not activated in the kernel. You have to > activate it with a code patch, the gentoo rc-script can not cope with it > yet. hostapd needs to be a new version and has to initialize the device > itself. > Of course you can not expect the same features and easy to use behaviour > from such an experimental software. > > You seem to have a working setup, which suits your needs. Unless you have a > serious reason i would not change a running and supported system. OK, thank you Norman. The reason I'm trying to switch (this is my third serious attempt) is some kind of a bug that crashes the system when SMP is enabled and the madwifi driver is in master mode. I've been running without SMP, but I could really use the extra power. Do you know if there is better Gentoo support for this on the horizon? - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 15:38 ` Grant @ 2009-06-12 15:56 ` Stroller 2009-06-12 16:21 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Stroller @ 2009-06-12 15:56 UTC (permalink / raw To: gentoo-user On 12 Jun 2009, at 16:38, Grant wrote: > ... > OK, thank you Norman. The reason I'm trying to switch (this is my > third serious attempt) is some kind of a bug that crashes the system > when SMP is enabled and the madwifi driver is in master mode. I've > been running without SMP, but I could really use the extra power. That's interesting. I had an old 4 x processor machine running as an access-point (madwifi or madwifi-ng) running in master mode for at least a year or two. It was unstable as heck, and I never attributed it to this. It would, however, stay up for days or weeks at a time. Maybe this bug has crept in more recently? I'm not sure that it will apply to my new system (on which I'd like to run an AP, as soon as I get round to it) as that is a single processor P4. > Do you know if there is better Gentoo support for this on the horizon? I did find the dev uberlord immensely helpful when I was first doing this. He was the baselayout guy at the time, although I don't know if he still is or if you might be able to get hold of him. IMO the first thing to do is get the AP up & running without resort to the Gentoo init.d scripts. Try allocating an IP address to wlan0 just using `ifconfig` as root. If that works then you know the hardware & principles of operation are all ok. Stroller. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 15:56 ` Stroller @ 2009-06-12 16:21 ` Norman Rieß 2009-06-12 20:27 ` Grant 0 siblings, 1 reply; 41+ messages in thread From: Norman Rieß @ 2009-06-12 16:21 UTC (permalink / raw To: gentoo-user Stroller schrieb: > > On 12 Jun 2009, at 16:38, Grant wrote: >> ... >> OK, thank you Norman. The reason I'm trying to switch (this is my >> third serious attempt) is some kind of a bug that crashes the system >> when SMP is enabled and the madwifi driver is in master mode. I've >> been running without SMP, but I could really use the extra power. > > That's interesting. I had an old 4 x processor machine running as an > access-point (madwifi or madwifi-ng) running in master mode for at > least a year or two. It was unstable as heck, and I never attributed > it to this. It would, however, stay up for days or weeks at a time. > > Maybe this bug has crept in more recently? I'm not sure that it will > apply to my new system (on which I'd like to run an AP, as soon as I > get round to it) as that is a single processor P4. > >> Do you know if there is better Gentoo support for this on the horizon? > > I did find the dev uberlord immensely helpful when I was first doing > this. He was the baselayout guy at the time, although I don't know if > he still is or if you might be able to get hold of him. > > IMO the first thing to do is get the AP up & running without resort to > the Gentoo init.d scripts. Try allocating an IP address to wlan0 just > using `ifconfig` as root. If that works then you know the hardware & > principles of operation are all ok. > > Stroller. > > I would recomment the same thing. Play around manualy. Find out what works and what does not. And if you found a manual way, you can start scriptworkarounds and automating things. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 16:21 ` Norman Rieß @ 2009-06-12 20:27 ` Grant 0 siblings, 0 replies; 41+ messages in thread From: Grant @ 2009-06-12 20:27 UTC (permalink / raw To: gentoo-user >>> OK, thank you Norman. The reason I'm trying to switch (this is my >>> third serious attempt) is some kind of a bug that crashes the system >>> when SMP is enabled and the madwifi driver is in master mode. I've >>> been running without SMP, but I could really use the extra power. >> >> That's interesting. I had an old 4 x processor machine running as an >> access-point (madwifi or madwifi-ng) running in master mode for at least a >> year or two. It was unstable as heck, and I never attributed it to this. It >> would, however, stay up for days or weeks at a time. >> >> Maybe this bug has crept in more recently? I'm not sure that it will apply >> to my new system (on which I'd like to run an AP, as soon as I get round to >> it) as that is a single processor P4. >> >>> Do you know if there is better Gentoo support for this on the horizon? >> >> I did find the dev uberlord immensely helpful when I was first doing this. >> He was the baselayout guy at the time, although I don't know if he still is >> or if you might be able to get hold of him. >> >> IMO the first thing to do is get the AP up & running without resort to the >> Gentoo init.d scripts. Try allocating an IP address to wlan0 just using >> `ifconfig` as root. If that works then you know the hardware & principles of >> operation are all ok. >> >> Stroller. >> >> > I would recomment the same thing. Play around manualy. Find out what works > and what does not. And if you found a manual way, you can start > scriptworkarounds and automating things. Thanks everyone. This system is critical so I think I'm better off sticking with madwifi and no SMP for now. I just upgraded to 2.6.29 so I thought things might be ready. Which software component should I be on the lookout for as far as Gentoo being ready to integrate smoothly with ath5k? baselayout? - Grant ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 13:17 ` Grant 2009-06-12 15:24 ` Norman Rieß @ 2009-06-12 15:47 ` Stroller 2009-06-12 22:16 ` Mick 1 sibling, 1 reply; 41+ messages in thread From: Stroller @ 2009-06-12 15:47 UTC (permalink / raw To: gentoo-user On 12 Jun 2009, at 14:17, Grant wrote: >> ... >> wlan0 in master mode does _not_ have an IP adress. So far eth0 is >> the only >> ip adress your device has. >> If you do not spezify a local ip adress on eth1, you will not have >> any local >> ip adress. > > I'm very confused. I've been running wlan0 in master mode for about 3 > years with IP 192.168.0.1 and no eth1. Here was my entire > /etc/conf.d/net: > > config_eth0=( "dhcp" ) > mode_wlan0=( "master" ) > essid_wlan0=( "networkname" ) > channel_wlan0=( "11" ) > config_wlan0=( "192.168.0.1 broadcast 192.168.0.255 netmask > 255.255.255.0" ) > > All I'm trying to do is switch wireless drivers from madwifi-ng to the > in-kernel ath5k. With madwifi-ng, I started net.wlan0, started > hostapd, and started shorewall and everything worked perfectly. Now > with ath5k, net.wlan0 won't start in master mode. This causes 2 > problems: > > 1. I can't specify a local IP for wlan0 in /etc/conf.d/net like I've > been doing for years. > 2. shorewall checks whether or not net.wlan0 has started because wlan0 > is the only device in zone loc, so shorewall won't start. > > So I'm required to have an eth1 because I'm switching from madwifi-ng > to ath5k? That doesn't seem right. For master mode AP to work, you should indeed be allocating it an IP address, just as you did before. My experience was with madwifi some years ago, when it was the only driver for Atheros chips (am I remembering correctly?) and this combination was absolutely the best for an access-point setup. At that time the only other 802.11g driver that did master mode was, I think, Prism54 and it was a little difficult to get hold of cards featuring that chipset (consequently I got into the side-business of selling them, and probably have 20 left here). madwifi was better because it featured "virtual APs" (VAPs) and allowed you to run separate WEP & unencrypted wireless networks on the same card (and run iptables rules on the interface allocated to each VAP). So I'm not sure why you're changing from madwifi to ath5k. But it _should_ be possible to assign an address to the wireless interface in master mode. And in the situation you describe - a router with only 2 interfaces, WAN & wLAN, then that's exactly what you want to do. The client machines on the wLAN will have IP addresses and they must be told the IP address of the gateway. The WAN IP address will be issued by your ISP, and of course the wLAN IP addresses must be in a private range. The gateway's LAN IP address must be on the same subnet as all the client PCs on the wLAN. Stroller. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 15:47 ` Stroller @ 2009-06-12 22:16 ` Mick 0 siblings, 0 replies; 41+ messages in thread From: Mick @ 2009-06-12 22:16 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 855 bytes --] On Friday 12 June 2009, Stroller wrote: > At that time the only other 802.11g driver that did master mode was, I > think, Prism54 and it was a little difficult to get hold of cards > featuring that chipset (consequently I got into the side-business of > selling them, and probably have 20 left here). madwifi was better > because it featured "virtual APs" (VAPs) and allowed you to run > separate WEP & unencrypted wireless networks on the same card (and run > iptables rules on the interface allocated to each VAP). > > So I'm not sure why you're changing from madwifi to ath5k. Well, I understand that once you move to 2.6.29 there's no choice of madwifi any more? I tried to emerge it and from what I recall was told to enable ath5k in the kernel - which as you say is not as powerful as madwifi was. -- Regards, Mick [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-11 23:32 ` Norman Rieß 2009-06-11 23:38 ` Grant @ 2009-06-12 5:46 ` Graham Murray 2009-06-12 7:39 ` Matt Causey 1 sibling, 1 reply; 41+ messages in thread From: Graham Murray @ 2009-06-12 5:46 UTC (permalink / raw To: gentoo-user Norman Rieß <norman@smash-net.org> writes: > What do you want to do with your accesspoint. You will need a bridge > to a wired network if you want your ap attached to that wired > network. This is quite usual though... > Without a bridge to a wired network, only the wlan systems are > connected and can not connect to your wired systems. Would it not normally be better to route between the wireless and wired networks, with appropriate firewall rules in place, rather than bridging them? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 5:46 ` Graham Murray @ 2009-06-12 7:39 ` Matt Causey 2009-06-12 10:53 ` Norman Rieß 0 siblings, 1 reply; 41+ messages in thread From: Matt Causey @ 2009-06-12 7:39 UTC (permalink / raw To: gentoo-user@lists.gentoo.org; +Cc: gentoo-user@lists.gentoo.org On 12 Jun 2009, at 06:46, Graham Murray <graham@gmurray.org.uk> wrote: > Norman Rieß <norman@smash-net.org> writes: > >> What do you want to do with your accesspoint. You will need a bridge >> to a wired network if you want your ap attached to that wired >> network. This is quite usual though... >> Without a bridge to a wired network, only the wlan systems are >> connected and can not connect to your wired systems. > > Would it not normally be better to route between the wireless and > wired > networks, with appropriate firewall rules in place, rather than > bridging > them? > That is the intent of a project I'm working on, and I think it will work well. However most folks don't need the additional complexity of multiple networks. In that case just bridging to the existing subnet is sufficient. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [gentoo-user] Atheros kernel driver and my wireless access point setup 2009-06-12 7:39 ` Matt Causey @ 2009-06-12 10:53 ` Norman Rieß 0 siblings, 0 replies; 41+ messages in thread From: Norman Rieß @ 2009-06-12 10:53 UTC (permalink / raw To: gentoo-user Matt Causey schrieb: > > On 12 Jun 2009, at 06:46, Graham Murray <graham@gmurray.org.uk> wrote: > >> Norman Rieß <norman@smash-net.org> writes: >> >>> What do you want to do with your accesspoint. You will need a bridge >>> to a wired network if you want your ap attached to that wired >>> network. This is quite usual though... >>> Without a bridge to a wired network, only the wlan systems are >>> connected and can not connect to your wired systems. >> >> Would it not normally be better to route between the wireless and wired >> networks, with appropriate firewall rules in place, rather than bridging >> them? >> > That is the intent of a project I'm working on, and I think it will > work well. However most folks don't need the additional complexity of > multiple networks. In that case just bridging to the existing subnet > is sufficient. It really depends on the users needs. I said this was quite usual because with bridging produces the behaviour someone expects from an out of the box accesspoint. If someone wants to control the connections or create a dmz or whatever, routing would be the way, yes. In Grant's situation routing should be the better choice, as he seems to want to have a router with wlan, rather than a simple accesspoint. The wlan becomes the local network and the wired nic, the web. So this would again produce the behavious one expects from a out of the box router. If he later one create a wlan-router setup, i dare say he would bridge wlan and local wired and NAT/route that to the wired web nic. But that are my views... as i said, it depends on the users needs. ^ permalink raw reply [flat|nested] 41+ messages in thread
end of thread, other threads:[~2009-06-12 22:16 UTC | newest] Thread overview: 41+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-06-09 5:21 [gentoo-user] Atheros kernel driver and my wireless access point setup Jason Carson 2009-06-09 5:46 ` Jason Carson 2009-06-09 6:33 ` Dale 2009-06-09 7:15 ` Jason Carson 2009-06-09 12:57 ` Stroller 2009-06-09 21:15 ` Jason Carson 2009-06-09 21:27 ` Jason Carson 2009-06-09 7:45 ` Neil Bothwick 2009-06-09 5:50 ` Mick 2009-06-09 6:12 ` Jason Carson 2009-06-09 10:41 ` Norman Rieß 2009-06-09 21:12 ` Jason Carson 2009-06-10 0:35 ` Norman Rieß 2009-06-10 4:38 ` Jason Carson 2009-06-10 10:37 ` Norman Rieß 2009-06-10 18:20 ` Jason Carson 2009-06-10 20:04 ` Norman Rieß 2009-06-10 21:38 ` Jason Carson 2009-06-10 23:33 ` Norman Rieß 2009-06-10 23:51 ` Jason Carson 2009-06-11 1:34 ` Norman Rieß 2009-06-11 2:03 ` Jason Carson 2009-06-11 22:13 ` Grant 2009-06-11 23:32 ` Norman Rieß 2009-06-11 23:38 ` Grant 2009-06-11 23:59 ` [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver) Stroller 2009-06-12 2:10 ` Grant 2009-06-12 0:42 ` [gentoo-user] Atheros kernel driver and my wireless access point setup Norman Rieß 2009-06-12 2:04 ` Grant 2009-06-12 10:35 ` Norman Rieß 2009-06-12 13:17 ` Grant 2009-06-12 15:24 ` Norman Rieß 2009-06-12 15:38 ` Grant 2009-06-12 15:56 ` Stroller 2009-06-12 16:21 ` Norman Rieß 2009-06-12 20:27 ` Grant 2009-06-12 15:47 ` Stroller 2009-06-12 22:16 ` Mick 2009-06-12 5:46 ` Graham Murray 2009-06-12 7:39 ` Matt Causey 2009-06-12 10:53 ` Norman Rieß
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox