On Fri, May 16, 2008 at 4:03 PM, Stefanik G=E1bor <netrolller.3d@gmail.=
com> wrote:
On Fri, May 16, 2008 at 3:27 PM, Martin Dubuc [off-list ref]=
wrote:
quoted
You are right pointing out that it is possible to perform monitor mo=
de
quoted
configuration using startup scripts. However, to fit nicely in exist=
ing
quoted
frameworks, such as the ones available from Fedora, it would be nice=
that
quoted
the driver be enhanced. Madwifi allows users to put a configuration =
like
quoted
this one in the modprobe.conf.:
options ath_pci autocreate=3Dmonitor
The nice thing about such a configuration is that it decouples the d=
evice
quoted
type configuration from the interface management function. One does =
not need
quoted
to worry which interface (wlan0, wlan1, wlan2, etc.) a device will c=
ome up
quoted
on, the system configures any device of a given type using a common =
set of
quoted
configuration. For systems that have only one Wi-Fi device, your met=
hod is
quoted
as good as this one, but for systems that have more than one Wi-Fi d=
evice,
quoted
some of them coming off and on while the system is running, possibly=
using
quoted
different interface names, the modprobe.conf solution is better.
Martin
This might better be done in the stack, rather than the driver. This =
way,
all drivers would get this functionality. CCing the linux-wireless ma=
iling
list.
Also, since an userspace solution might be preferred by Linville and =
the
other wireless maintainers, it might be wise to add an "aggregate dev=
ice" or
a "supermaster" which can be targeted by iw so that all devices gover=
ned by
that driver get a new interface.
Alternatively, a script can be made that creates a monitor interface =
on monX
or rtapX for all wmasterX devices. This is equivalent to madwifi's so=
lution,
except that it's userspace, which is preferred now.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
BTW, here is a script that automatically creates a "monX" interface
for every "wmasterX" master device it encounters:
#!/bin/sh
for a in $(iwconfig 2>&1 | grep wmaster | sed -e 's/wmaster//' | cut -b=
1); do
iw dev wmaster$a interface add mon$a type monitor
ifconfig mon$a up
done
--=20
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, May 16, 2008 at 4:28 PM, Stefanik G=E1bor <netrolller.3d@gmail.=
com> wrote:
On Fri, May 16, 2008 at 4:03 PM, Stefanik G=E1bor <netrolller.3d@gmai=
l.com> wrote:
quoted
On Fri, May 16, 2008 at 3:27 PM, Martin Dubuc <martind1111@gmail.com=
wrote:
quoted
quoted
You are right pointing out that it is possible to perform monitor m=
ode
quoted
quoted
configuration using startup scripts. However, to fit nicely in exis=
ting
quoted
quoted
frameworks, such as the ones available from Fedora, it would be nic=
e that
quoted
quoted
the driver be enhanced. Madwifi allows users to put a configuration=
like
quoted
quoted
this one in the modprobe.conf.:
options ath_pci autocreate=3Dmonitor
The nice thing about such a configuration is that it decouples the =
device
quoted
quoted
type configuration from the interface management function. One does=
not need
quoted
quoted
to worry which interface (wlan0, wlan1, wlan2, etc.) a device will =
come up
quoted
quoted
on, the system configures any device of a given type using a common=
set of
quoted
quoted
configuration. For systems that have only one Wi-Fi device, your me=
thod is
quoted
quoted
as good as this one, but for systems that have more than one Wi-Fi =
device,
quoted
quoted
some of them coming off and on while the system is running, possibl=
y using
quoted
quoted
different interface names, the modprobe.conf solution is better.
Martin
This might better be done in the stack, rather than the driver. This=
way,
quoted
all drivers would get this functionality. CCing the linux-wireless m=
ailing
quoted
list.
Also, since an userspace solution might be preferred by Linville and=
the
quoted
other wireless maintainers, it might be wise to add an "aggregate de=
vice" or
quoted
a "supermaster" which can be targeted by iw so that all devices gove=
rned by
quoted
that driver get a new interface.
Alternatively, a script can be made that creates a monitor interface=
on monX
quoted
or rtapX for all wmasterX devices. This is equivalent to madwifi's s=
olution,
quoted
except that it's userspace, which is preferred now.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-=
)
BTW, here is a script that automatically creates a "monX" interface
for every "wmasterX" master device it encounters:
#!/bin/sh
for a in $(iwconfig 2>&1 | grep wmaster | sed -e 's/wmaster//' | cut =
-b 1); do
iw dev wmaster$a interface add mon$a type monitor
ifconfig mon$a up
done
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
Oops... this is enough:
#!/bin/sh
for a in $(iwconfig 2>&1 | grep wmaster | cut -b 8); do
iw dev wmaster$a interface add mon$a type monitor
ifconfig mon$a up
done
--=20
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html