Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
>>> 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
>>> 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
Matt Causey schrieb: On 12 Jun 2009, at 06:46, Graham Murray wrote: Norman Rieß 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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
On 12 Jun 2009, at 06:46, Graham Murray wrote: Norman Rieß 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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
Norman Rieß 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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
>>> 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
>> 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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.0 +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-/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 :-)
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.0 +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-/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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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?
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
>> >> On 9 Jun 2009, at 08:15, Jason Carson wrote: >>> H, 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 :-)
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> > On 9 Jun 2009, at 08:15, Jason Carson wrote: >> H, 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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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...
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
On 9 Jun 2009, at 08:15, Jason Carson wrote: H, 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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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." signature.asc Description: PGP signature
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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 > > :-) :-) > > H, 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
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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 :-) :-)
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
> 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.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Atheros kernel driver and my wireless access point setup
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. > > >
