[gentoo-user] Gentoo and Madwifi contradict each other

[gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

I'm trying to set up ath5k in master mode.  I get this from the hostapd ebuild:

 * In order to use hostapd you need to set up your wireless card
 * for master mode in /etc/conf.d/net and then start
 * /etc/init.d/hostapd.
 *
 * Example configuration:
 *
 * config_wlan0=( "192.168.1.1/24" )
 * channel_wlan0="6"
 * essid_wlan0="test"
 * mode_wlan0="master"

But doing that I get:

ath0 does not support setting the mode to "master"

and madwifi IRC says:

"you can't use iwconfig to set master mode you need to do that with hostapd"

Does anyone know how to reconcile this?

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

On Sat, 21 Feb 2009 10:33:17 -0800, Grant wrote:

> I'm trying to set up ath5k in master mode.  I get this from the hostapd
> ebuild:
> 
>  * In order to use hostapd you need to set up your wireless card
>  * for master mode in /etc/conf.d/net and then start
>  * /etc/init.d/hostapd.
>  *
>  * Example configuration:
>  *
>  * config_wlan0=( "192.168.1.1/24" )
>  * channel_wlan0="6"
>  * essid_wlan0="test"
>  * mode_wlan0="master"
> 
> But doing that I get:
> 
> ath0 does not support setting the mode to "master"

You're using the wrong interface name. MadWifi uses ath0, ath5k uses
wlan0.


-- 
Neil Bothwick

Maybe... How much are you bribing me this time?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>> I'm trying to set up ath5k in master mode.  I get this from the hostapd
>> ebuild:
>>
>>  * In order to use hostapd you need to set up your wireless card
>>  * for master mode in /etc/conf.d/net and then start
>>  * /etc/init.d/hostapd.
>>  *
>>  * Example configuration:
>>  *
>>  * config_wlan0=( "192.168.1.1/24" )
>>  * channel_wlan0="6"
>>  * essid_wlan0="test"
>>  * mode_wlan0="master"
>>
>> But doing that I get:
>>
>> ath0 does not support setting the mode to "master"
>
> You're using the wrong interface name. MadWifi uses ath0, ath5k uses
> wlan0.
>
>
> --
> Neil Bothwick

Yes but I have:

udev: renamed network interface wlan0 to ath0

Could that be a problem?

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

On Sat, 21 Feb 2009 12:03:17 -0800, Grant wrote:

> >>  * In order to use hostapd you need to set up your wireless card
> >>  * for master mode in /etc/conf.d/net and then start
> >>  * /etc/init.d/hostapd.
> >>  *
> >>  * Example configuration:
> >>  *
> >>  * config_wlan0=( "192.168.1.1/24" )
> >>  * channel_wlan0="6"
> >>  * essid_wlan0="test"
> >>  * mode_wlan0="master"
> >>
> >> But doing that I get:
> >>
> >> ath0 does not support setting the mode to "master"
> >
> > You're using the wrong interface name. MadWifi uses ath0, ath5k uses
> > wlan0.

> Yes but I have:
> 
> udev: renamed network interface wlan0 to ath0
> 
> Could that be a problem?

I don't understand why you need to rename the interface from the standard
kernel nomenclature to something non-standard, but that's by the by.

You still have conflicting names if you have wlan0 in conf.d/net. Another
possibility is that ath5k does not support master mode yet, I get an
error trying to switch it to Master here. 


-- 
Neil Bothwick

WinErr 00D: Window closed - Do not look outside

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>> >>  * In order to use hostapd you need to set up your wireless card
>> >>  * for master mode in /etc/conf.d/net and then start
>> >>  * /etc/init.d/hostapd.
>> >>  *
>> >>  * Example configuration:
>> >>  *
>> >>  * config_wlan0=( "192.168.1.1/24" )
>> >>  * channel_wlan0="6"
>> >>  * essid_wlan0="test"
>> >>  * mode_wlan0="master"
>> >>
>> >> But doing that I get:
>> >>
>> >> ath0 does not support setting the mode to "master"
>> >
>> > You're using the wrong interface name. MadWifi uses ath0, ath5k uses
>> > wlan0.
>
>> Yes but I have:
>>
>> udev: renamed network interface wlan0 to ath0
>>
>> Could that be a problem?
>
> I don't understand why you need to rename the interface from the standard
> kernel nomenclature to something non-standard, but that's by the by.

The wireless card uses madwifi right now, as I try to get ath5k
working, so there's a udev rule that matches the hardware address with
the ath0 label.

> You still have conflicting names if you have wlan0 in conf.d/net. Another

That's taken care of.

> possibility is that ath5k does not support master mode yet, I get an
> error trying to switch it to Master here.

The madwifi/ath5k guys say it should work in 2.6.28 which I'm on.  The
latest is I'm getting this directly from hostapd:

Failed to set interface ath0 to master mode.
nl80211 driver initialization failed.
rmdir[ctrl_interface]: No such file or directory
ELOOP: remaining socket: sock=5 eloop_data=...

I'm sure my procedure is correct now, but I don't know why ath0 won't
go into master mode.

- Grant

> Neil Bothwick

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Norman Rieß]

Grant schrieb:
> The madwifi/ath5k guys say it should work in 2.6.28 which I'm on.  The
> latest is I'm getting this directly from hostapd:
>
> Failed to set interface ath0 to master mode.
> nl80211 driver initialization failed.
> rmdir[ctrl_interface]: No such file or directory
> ELOOP: remaining socket: sock=5 eloop_data=...
>
> I'm sure my procedure is correct now, but I don't know why ath0 won't
> go into master mode.
>
> - Grant
>
>   
>

Hi,
i have been, through that lately an it is not that out of the box. Here
is what i put together from linux-wireless mailinglist and trial and error:

1. Master mode on ath5k is there, but not activated and not in 2.6.28.
Mainly from this thread i got the kernel stuff and settings
http://marc.info/?t=122652720700004&r=1&w=2
I use the latest git pull from http://linuxwireless.org/. The AP mode
needs still to be activated:

--- wireless-testing/drivers/net/wireless/ath5k/base.c      2009-02-10
06:11:43.186470883 +0100
+++ wireless-testing/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;

Now you have a kernel and a ath5k module capable of master mode.

2. You need ~arch version of hostapd. Stable version did not do the
trick for me.
3. I needed to modify the startscripts. I removed the net.wlan0 link
completely, as it does not seem to be able to initialize the ap mode,
but is loaded automaticaly even when it is not set to boot in a spezific
runlevel. So you need hostapd to initialize the wlan-nic. hostapd script
wants to start all networkinterfaces with the rc-scripts, so i edited
the script, to start my bridge an the wired card only and leave out the
wlan-nic. I think this is a little redundant to removing the net.wlan0
script.

Sometimes while testing, the interface did not shut down properly and
hostapd could not initialize them any more. So i had to set them down
manually with iwconfig. After that hostapd could use them again.

This is clearly not yet meant to be used in a productive environment, as
the devs clearly stated in the postet threads on wireless-linux.


Regards,
Norman

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>> The madwifi/ath5k guys say it should work in 2.6.28 which I'm on.  The
>> latest is I'm getting this directly from hostapd:
>>
>> Failed to set interface ath0 to master mode.
>> nl80211 driver initialization failed.
>> rmdir[ctrl_interface]: No such file or directory
>> ELOOP: remaining socket: sock=5 eloop_data=...
>>
>> I'm sure my procedure is correct now, but I don't know why ath0 won't
>> go into master mode.
>>
>> - Grant
>>
>>
>>
>
> Hi,
> i have been, through that lately an it is not that out of the box. Here
> is what i put together from linux-wireless mailinglist and trial and error:
>
> 1. Master mode on ath5k is there, but not activated and not in 2.6.28.
> Mainly from this thread i got the kernel stuff and settings
> http://marc.info/?t=122652720700004&r=1&w=2
> I use the latest git pull from http://linuxwireless.org/. The AP mode
> needs still to be activated:
>
> --- wireless-testing/drivers/net/wireless/ath5k/base.c      2009-02-10
> 06:11:43.186470883 +0100
> +++ wireless-testing/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;
>
> Now you have a kernel and a ath5k module capable of master mode.
>
> 2. You need ~arch version of hostapd. Stable version did not do the
> trick for me.
> 3. I needed to modify the startscripts. I removed the net.wlan0 link
> completely, as it does not seem to be able to initialize the ap mode,
> but is loaded automaticaly even when it is not set to boot in a spezific
> runlevel. So you need hostapd to initialize the wlan-nic. hostapd script
> wants to start all networkinterfaces with the rc-scripts, so i edited
> the script, to start my bridge an the wired card only and leave out the
> wlan-nic. I think this is a little redundant to removing the net.wlan0
> script.
>
> Sometimes while testing, the interface did not shut down properly and
> hostapd could not initialize them any more. So i had to set them down
> manually with iwconfig. After that hostapd could use them again.
>
> This is clearly not yet meant to be used in a productive environment, as
> the devs clearly stated in the postet threads on wireless-linux.
>
>
> Regards,
> Norman

Thanks a lot Norman.  I've got to remember not to ride the bleeding
edge.  Removing wlan0 from /etc/conf.d/hostapd didn't prevent hostapd
from starting it?

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Norman Rieß]

[-- Attachment #1: Type: text/plain, Size: 3089 bytes --]

Grant schrieb:
>> Hi,
>> i have been, through that lately an it is not that out of the box. Here
>> is what i put together from linux-wireless mailinglist and trial and error:
>>
>> 1. Master mode on ath5k is there, but not activated and not in 2.6.28.
>> Mainly from this thread i got the kernel stuff and settings
>> http://marc.info/?t=122652720700004&r=1&w=2
>> I use the latest git pull from http://linuxwireless.org/. The AP mode
>> needs still to be activated:
>>
>> --- wireless-testing/drivers/net/wireless/ath5k/base.c      2009-02-10
>> 06:11:43.186470883 +0100
>> +++ wireless-testing/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;
>>
>> Now you have a kernel and a ath5k module capable of master mode.
>>
>> 2. You need ~arch version of hostapd. Stable version did not do the
>> trick for me.
>> 3. I needed to modify the startscripts. I removed the net.wlan0 link
>> completely, as it does not seem to be able to initialize the ap mode,
>> but is loaded automaticaly even when it is not set to boot in a spezific
>> runlevel. So you need hostapd to initialize the wlan-nic. hostapd script
>> wants to start all networkinterfaces with the rc-scripts, so i edited
>> the script, to start my bridge an the wired card only and leave out the
>> wlan-nic. I think this is a little redundant to removing the net.wlan0
>> script.
>>
>> Sometimes while testing, the interface did not shut down properly and
>> hostapd could not initialize them any more. So i had to set them down
>> manually with iwconfig. After that hostapd could use them again.
>>
>> This is clearly not yet meant to be used in a productive environment, as
>> the devs clearly stated in the postet threads on wireless-linux.
>>
>>
>> Regards,
>> Norman
>>     
>
> Thanks a lot Norman.  I've got to remember not to ride the bleeding
> edge.  Removing wlan0 from /etc/conf.d/hostapd didn't prevent hostapd
> from starting it?
>
> - Grant
>
>   
Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as
you wish hostapd to use wlan0.
The init scripts are not able to set up master mode correctly and bring
up an error or set up wlan0 interface in a false mode so hostapd can not
set it up any more.
So i set up my init to completely ignore wlan0 till hostapd handles it.
Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i
removed it completely.
Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.

One thing,you might stumble accross later on. In hostapd.conf provide
the wpa key in hex, not in phrase. phrase coused authentication errors
for me an for one guy in the thread i talked about earlier.
Otherwise the system runs fine and stable now. I hope there will be a
less messy init-setting soon, as this functions get stabilized.

Norman



[-- Attachment #2: Type: text/html, Size: 3586 bytes --]

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

> Hi,
> i have been, through that lately an it is not that out of the box. Here
> is what i put together from linux-wireless mailinglist and trial and error:
>
> 1. Master mode on ath5k is there, but not activated and not in 2.6.28.
> Mainly from this thread i got the kernel stuff and settings
> http://marc.info/?t=122652720700004&r=1&w=2
> I use the latest git pull from http://linuxwireless.org/. The AP mode
> needs still to be activated:
>
> --- wireless-testing/drivers/net/wireless/ath5k/base.c      2009-02-10
> 06:11:43.186470883 +0100
> +++ wireless-testing/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;
>
> Now you have a kernel and a ath5k module capable of master mode.
>
> 2. You need ~arch version of hostapd. Stable version did not do the
> trick for me.
> 3. I needed to modify the startscripts. I removed the net.wlan0 link
> completely, as it does not seem to be able to initialize the ap mode,
> but is loaded automaticaly even when it is not set to boot in a spezific
> runlevel. So you need hostapd to initialize the wlan-nic. hostapd script
> wants to start all networkinterfaces with the rc-scripts, so i edited
> the script, to start my bridge an the wired card only and leave out the
> wlan-nic. I think this is a little redundant to removing the net.wlan0
> script.
>
> Sometimes while testing, the interface did not shut down properly and
> hostapd could not initialize them any more. So i had to set them down
> manually with iwconfig. After that hostapd could use them again.
>
> This is clearly not yet meant to be used in a productive environment, as
> the devs clearly stated in the postet threads on wireless-linux.
>
>
> Regards,
> Norman
>
>
> Thanks a lot Norman.  I've got to remember not to ride the bleeding
> edge.  Removing wlan0 from /etc/conf.d/hostapd didn't prevent hostapd
> from starting it?
>
> - Grant
>
>
>
> Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as you
> wish hostapd to use wlan0.
> The init scripts are not able to set up master mode correctly and bring up
> an error or set up wlan0 interface in a false mode so hostapd can not set it
> up any more.
> So i set up my init to completely ignore wlan0 till hostapd handles it.
> Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i
> removed it completely.

Can you be more specific about what you did?  Did you just remove the
wlan0 initscript, or did you also make an initscript modification?  If
so, could you share your modification?

> Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.

That's why I thought removing wlan0 from /etc/conf.d/hostapd would be
appropriate.

- Grant

> One thing,you might stumble accross later on. In hostapd.conf provide the
> wpa key in hex, not in phrase. phrase coused authentication errors for me an
> for one guy in the thread i talked about earlier.
> Otherwise the system runs fine and stable now. I hope there will be a less
> messy init-setting soon, as this functions get stabilized.
>
> Norman

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Norman Rieß]

Grant schrieb:
>> Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as you
>> wish hostapd to use wlan0.
>> The init scripts are not able to set up master mode correctly and bring up
>> an error or set up wlan0 interface in a false mode so hostapd can not set it
>> up any more.
>> So i set up my init to completely ignore wlan0 till hostapd handles it.
>> Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i
>> removed it completely.
>>     
>
> Can you be more specific about what you did?  Did you just remove the
> wlan0 initscript, or did you also make an initscript modification?  If
> so, could you share your modification?
>
>   
Sure.
I removed the net.wlan0 script, or better, i never created it.
I modified the init.d/hostapd script, not to depend on all interfaces
but on only those, which i need:

/etc/init.d/hostapd
depend() {
        need net.br0
        need net.eth0
        use logger
}

As i said earlier, this is kind of redundant as it is possible, that
without the script, hostapd would not start that interface. But i can
not tell, i never tested it.

>> Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.
>>     
>
> That's why I thought removing wlan0 from /etc/conf.d/hostapd would be
> appropriate.
>
> - Grant
>   
Damnit, you are right, i should have read the text.

After looking over this setting with a little distance for this thread,
10 days after setting this up and with yout hint, i feel this could be
smoothed up significantly ;-). So thanks for that. I think i will put
some energy in it tomorrow.

Norman

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>>> Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as you
>>> wish hostapd to use wlan0.
>>> The init scripts are not able to set up master mode correctly and bring up
>>> an error or set up wlan0 interface in a false mode so hostapd can not set it
>>> up any more.
>>> So i set up my init to completely ignore wlan0 till hostapd handles it.
>>> Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i
>>> removed it completely.
>>>
>>
>> Can you be more specific about what you did?  Did you just remove the
>> wlan0 initscript, or did you also make an initscript modification?  If
>> so, could you share your modification?
>>
>>
> Sure.
> I removed the net.wlan0 script, or better, i never created it.
> I modified the init.d/hostapd script, not to depend on all interfaces
> but on only those, which i need:
>
> /etc/init.d/hostapd
> depend() {
>        need net.br0
>        need net.eth0
>        use logger
> }
>
> As i said earlier, this is kind of redundant as it is possible, that
> without the script, hostapd would not start that interface. But i can
> not tell, i never tested it.
>
>>> Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.
>>>
>>
>> That's why I thought removing wlan0 from /etc/conf.d/hostapd would be
>> appropriate.
>>
>> - Grant
>>
> Damnit, you are right, i should have read the text.
>
> After looking over this setting with a little distance for this thread,
> 10 days after setting this up and with yout hint, i feel this could be
> smoothed up significantly ;-). So thanks for that. I think i will put
> some energy in it tomorrow.
>
> Norman

Still no luck for me with master mode, even after editing
wireless-testing/drivers/net/wireless/ath5k/base.c.  2.6.28 is
supposed to work but I'm wondering if it's not in 2.6.28-hardened or
something.  I still get "Failed to set interface ath0 to master mode"
from hostapd.

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Norman Rieß]

Grant schrieb:
> Still no luck for me with master mode, even after editing
> wireless-testing/drivers/net/wireless/ath5k/base.c.  2.6.28 is
> supposed to work but I'm wondering if it's not in 2.6.28-hardened or
> something.  I still get "Failed to set interface ath0 to master mode"
> from hostapd.
>
> - Grant
>
>   
2.6.28 did not work for me either.
Get the wireless-testing kernel as described here:
http://linuxwireless.org/en/developers/Documentation/git-guide
Apply the modification to ath5k/base.c.

You will have a 2.6.29-rc kernel with wireless-testing modifications.
This one should do the trick.

Norman

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>> Still no luck for me with master mode, even after editing
>> wireless-testing/drivers/net/wireless/ath5k/base.c.  2.6.28 is
>> supposed to work but I'm wondering if it's not in 2.6.28-hardened or
>> something.  I still get "Failed to set interface ath0 to master mode"
>> from hostapd.
>>
>> - Grant
>>
>>
> 2.6.28 did not work for me either.
> Get the wireless-testing kernel as described here:
> http://linuxwireless.org/en/developers/Documentation/git-guide
> Apply the modification to ath5k/base.c.
>
> You will have a 2.6.29-rc kernel with wireless-testing modifications.
> This one should do the trick.
>
> Norman

Thanks Norman.

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Grant]

>> Still no luck for me with master mode, even after editing
>> wireless-testing/drivers/net/wireless/ath5k/base.c.  2.6.28 is
>> supposed to work but I'm wondering if it's not in 2.6.28-hardened or
>> something.  I still get "Failed to set interface ath0 to master mode"
>> from hostapd.
>>
>> - Grant
>>
>>
> 2.6.28 did not work for me either.
> Get the wireless-testing kernel as described here:
> http://linuxwireless.org/en/developers/Documentation/git-guide
> Apply the modification to ath5k/base.c.
>
> You will have a 2.6.29-rc kernel with wireless-testing modifications.
> This one should do the trick.
>
> Norman

I'm a step closer in 2.6.28 after applying this patch:

--- wireless-testing.orig/net/mac80211/cfg.c 2008-10-28 10:32:35.000000000 +0200
+++ wireless-testing/net/mac80211/cfg.c 2008-10-28 10:32:40.000000000 +0200

@@ -26,6 +26,8 @@

#ifdef CONFIG_MAC80211_MESH
case NL80211_IFTYPE_MESH_POINT:
#endif
+ case NL80211_IFTYPE_AP:
+ case NL80211_IFTYPE_AP_VLAN:
case NL80211_IFTYPE_WDS:
return true;
default:

The interface will go into master mode now but it errors when trying
to set the channel.  Are you using an AR5xxx?

- Grant

Re: [gentoo-user] Gentoo and Madwifi contradict each other

[Norman Rieß]

Grant schrieb:
>>
>
> I'm a step closer in 2.6.28 after applying this patch:
>
> --- wireless-testing.orig/net/mac80211/cfg.c 2008-10-28 10:32:35.000000000 +0200
> +++ wireless-testing/net/mac80211/cfg.c 2008-10-28 10:32:40.000000000 +0200
>
> @@ -26,6 +26,8 @@
>
> #ifdef CONFIG_MAC80211_MESH
> case NL80211_IFTYPE_MESH_POINT:
> #endif
> + case NL80211_IFTYPE_AP:
> + case NL80211_IFTYPE_AP_VLAN:
> case NL80211_IFTYPE_WDS:
> return true;
> default:
>
> The interface will go into master mode now but it errors when trying
> to set the channel.  Are you using an AR5xxx?
>
> - Grant
>
>   
 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC
(rev 01)