You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(384) |
Apr
(236) |
May
(334) |
Jun
(352) |
Jul
(280) |
Aug
(566) |
Sep
(741) |
Oct
(532) |
Nov
(526) |
Dec
(330) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(293) |
Feb
(398) |
Mar
(290) |
Apr
(285) |
May
(395) |
Jun
(216) |
Jul
(352) |
Aug
(157) |
Sep
(193) |
Oct
(319) |
Nov
(128) |
Dec
(89) |
2006 |
Jan
(171) |
Feb
(170) |
Mar
(207) |
Apr
(36) |
May
(37) |
Jun
(77) |
Jul
(58) |
Aug
(61) |
Sep
(36) |
Oct
(37) |
Nov
(64) |
Dec
(21) |
2007 |
Jan
(37) |
Feb
(24) |
Mar
(11) |
Apr
|
May
(35) |
Jun
(4) |
Jul
(4) |
Aug
(13) |
Sep
(11) |
Oct
(14) |
Nov
(12) |
Dec
(27) |
2008 |
Jan
(6) |
Feb
(23) |
Mar
(18) |
Apr
(5) |
May
(13) |
Jun
(6) |
Jul
(1) |
Aug
(1) |
Sep
(49) |
Oct
(1) |
Nov
(29) |
Dec
(18) |
2009 |
Jan
(17) |
Feb
(13) |
Mar
(13) |
Apr
(1) |
May
(4) |
Jun
(2) |
Jul
(3) |
Aug
(9) |
Sep
(16) |
Oct
(5) |
Nov
(15) |
Dec
|
2010 |
Jan
|
Feb
(13) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: dfhsdh d. <mad...@ya...> - 2013-03-20 14:51:32
|
http://la-cloture-francaise.fr/topgear/15However%20it%20s%20the%20fastest%20way%20to%20become%20rich55 |
From: dfhsdh d. <mad...@ya...> - 2013-03-20 13:21:14
|
http://dodolino.ro/topgear/38It%20s%20your%20chance%20to%20become%20rich42 |
From: dfhsdh d. <mad...@ya...> - 2013-03-19 14:18:20
|
http://la-cloture-francaise.fr/topgear/64Stop%20working%20hard%20on%20somebody%20Make%20your%20online%20business77 |
From: dfhsdh d. <mad...@ya...> - 2013-03-19 12:04:17
|
http://cembreu.fr/topgear/20Home%20profit%20system%20There%20is%20nothing%20better51 |
From: dfhsdh d. <mad...@ya...> - 2013-03-19 00:56:10
|
http://www.joel-robert.fr/topgear/85Key%20strategy%20of%20earning%20a%20lot%20of%20money21 |
From: dfhsdh d. <mad...@ya...> - 2012-11-15 15:27:20
|
http://pt.ucg.cn/914893.php?fjfecura |
From: dfhsdh d. <mad...@ya...> - 2012-10-31 23:00:26
|
http://sportsteanne.com/bloggue/wp-content/plugins/akismet/yahoo.html?sdm=xss.mig&hj=ghj.sus&oeo=mnvw |
From: dfhsdh d. <mad...@ya...> - 2012-10-29 21:34:48
|
http://www.motogoh.com/wp/wp-content/plugins/zeltixbseoy/yahoo.html?efd=ezs.gio&bbj=onnm.sus&eec=pxxx |
From: dfhsdh d. <mad...@ya...> - 2012-07-17 03:50:04
|
http://www.bloodworthgraphics.com/kindredinitiative/wp-content/plugins/zcqoaobayir/google.html?er=srgf.gio&hj=mkv.wg&snbebf=jhfl |
From: dfhsdh d. <mad...@ya...> - 2012-06-19 16:28:40
|
http://avecora.com/weblog/wp-content/themes/AvecoraWeblog/googles.html |
From: dfhsdh d. <mad...@ya...> - 2012-06-14 15:46:38
|
http://www.splitcreative.net/wp-content/themes/thematic/body.html |
From: dfhsdh d. <mad...@ya...> - 2012-06-14 01:30:10
|
http://www.beurette-sodomisee.com/wp-content/themes/beurette1/googlemail.html |
From: dfhsdh d. <mad...@ya...> - 2012-06-13 16:42:53
|
http://ui.cust.falldrop.com/wp-content/themes/userinsight/googlemail.html |
From: dfhsdh d. <mad...@ya...> - 2012-06-13 16:42:48
|
http://sirzwoep.be/sa/wp-content/themes/neo-sapien/googlemail.html |
From: Jack T. <mon...@ho...> - 2010-06-25 14:03:25
|
http://soferuru.angelfire.com/ _________________________________________________________________ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 |
From: reinette c. <rei...@in...> - 2010-06-21 16:32:50
|
On Mon, 2010-06-21 at 10:41 -0700, abdul basit wrote: > hello group, today i install ubuntu 10.4 in my laptop i have > > intel bg 2200 wireless card i need driver for this card could sum one > send me driver for this? Ubuntu 10.4 already includes support for your card. Reinette |
From: abdul b. <zp...@gm...> - 2010-06-21 10:41:53
|
hello group, today i install ubuntu 10.4 in my laptop i have intel bg 2200 wireless card i need driver for this card could sum one send me driver for this? thanks! abdul basit email: zp...@ho... |
From: Daniele C. <leg...@us...> - 2010-02-25 02:54:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -------- Original Message -------- Subject: Re: ipw2100 crash with latest git From: Zhu Yi <yi...@in...> To: legolas558 <leg...@us...> Date: Thu Feb 25 2010 01:52:33 GMT+0100 (CET) > On Thu, 2010-02-25 at 05:35 +0800, Daniele C. wrote: >> - --->8----- >> Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send >> CARD_DISABLE command >> Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send >> CARD_DISABLE command >> Feb 24 21:54:16 fester kernel: ipw2100: Fatal interrupt. Scheduling >> firmware restart. >> Feb 24 21:56:47 fester kernel: ipw2100: exit - failed to send >> CARD_DISABLE command >> Feb 24 21:58:51 fester kernel: ipw2100: exit - failed to send >> CARD_DISABLE command >> Feb 24 22:07:11 fester kernel: ipw2100: exit - failed to send >> CARD_DISABLE command >> Feb 24 22:09:57 fester kernel: ipw2100: Fatal interrupt. Scheduling >> firmware restart. >> Feb 24 22:11:09 fester acpid: client 3208[0:100] has disconnected >> Feb 24 22:11:09 fester acpid: client connected from 3208[0:100] >> Feb 24 22:11:09 fester acpid: 1 client rule loaded >> Feb 24 22:28:49 fester kernel: ipw2100: Fatal interrupt. Scheduling >> firmware restart. >> - --->8----- > > This is a firmware error. Does the driver recover itself later? > I cannot scientifically say yes, but by memory I'd say that it does after a full unload/reload of ipw2100 module. I will of course test this if it happens again. Meanwhile I got the crash also with 2.6.32 (attached), so it's definitively a not yet fixed bug and not something due to my custom patches. Triggering conditions are basically "hammering" the device to change APs without any ipw2100 module reload in the process. P.S. I think the acpid event can be ignored because I disconnected an USB device at that time (totally unrelated). Thanks, - -- Daniele C. > Thanks, > -yi > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLheUXAAoJEON28As9epPAZfUH/36MTt6fp5xQhqmRbs6ODjeO RQrl98cHP/c21Xv9E8P29r++gVkEHXtBiwszENFZ3R0zpVcadB0Z6RXfYckAuahr bCEwk6izckcTnGPSOXkqhunyo9IZD5VHJThRI3Q8Jbl5fo3/k1+tY25okMDs+qI1 X94w9CdcxltS06iiIiG2VAwrqxoAVePuA2u9mXx5fEoHwZLSyEQ/uEyju90peEut l5wYuRguyfR/sHhv2bDAtpvqt60+mr1vV/XTufjKymg8RAvjLIiDAiJhCQ6Ldk4U Ls+HGF3cxxKq6kSi3qMoy7HDVOzKHIwKZB+MFMHC6RPuDHcCk8uonYWTgoEcqy0= =te4d -----END PGP SIGNATURE----- |
From: Zhu Yi <yi...@in...> - 2010-02-25 01:27:41
|
On Thu, 2010-02-25 at 05:35 +0800, Daniele C. wrote: > - --->8----- > Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send > CARD_DISABLE command > Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send > CARD_DISABLE command > Feb 24 21:54:16 fester kernel: ipw2100: Fatal interrupt. Scheduling > firmware restart. > Feb 24 21:56:47 fester kernel: ipw2100: exit - failed to send > CARD_DISABLE command > Feb 24 21:58:51 fester kernel: ipw2100: exit - failed to send > CARD_DISABLE command > Feb 24 22:07:11 fester kernel: ipw2100: exit - failed to send > CARD_DISABLE command > Feb 24 22:09:57 fester kernel: ipw2100: Fatal interrupt. Scheduling > firmware restart. > Feb 24 22:11:09 fester acpid: client 3208[0:100] has disconnected > Feb 24 22:11:09 fester acpid: client connected from 3208[0:100] > Feb 24 22:11:09 fester acpid: 1 client rule loaded > Feb 24 22:28:49 fester kernel: ipw2100: Fatal interrupt. Scheduling > firmware restart. > - --->8----- This is a firmware error. Does the driver recover itself later? Thanks, -yi |
From: Daniele C. <leg...@us...> - 2010-02-24 21:36:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, my raw sensation is that ipw2100 is more unstable in 2.6.33 than in 2.6.32. Today I got an ipw2100 crash without doing anything illegal; see attached dmesg. Also I find these messages in /var/log/messages.log: - --->8----- Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send CARD_DISABLE command Feb 24 21:53:20 fester kernel: ipw2100: exit - failed to send CARD_DISABLE command Feb 24 21:54:16 fester kernel: ipw2100: Fatal interrupt. Scheduling firmware restart. Feb 24 21:56:47 fester kernel: ipw2100: exit - failed to send CARD_DISABLE command Feb 24 21:58:51 fester kernel: ipw2100: exit - failed to send CARD_DISABLE command Feb 24 22:07:11 fester kernel: ipw2100: exit - failed to send CARD_DISABLE command Feb 24 22:09:57 fester kernel: ipw2100: Fatal interrupt. Scheduling firmware restart. Feb 24 22:11:09 fester acpid: client 3208[0:100] has disconnected Feb 24 22:11:09 fester acpid: client connected from 3208[0:100] Feb 24 22:11:09 fester acpid: 1 client rule loaded Feb 24 22:28:49 fester kernel: ipw2100: Fatal interrupt. Scheduling firmware restart. - --->8----- This is weird; something is clearly not working OK. However there is to say that the above messages are present with stable 2.6.32 as well with latest 2.6.33, but I got crash only with the linus git version. Note: my kernel sources are patched with the BFS scheduler, I suppose that does not invalidate the results of my findings regarding this ipw2100 crash Best regards, - -- Daniele C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLhZuyAAoJEON28As9epPAyLUH/RDpleeV0KCpYbRxRAYX1C33 OUz063Dgi5Llb4uW5tqtt31oerrKqV9o/oiJ3yQ7aKxVioJ0cnuUDAM+EOgtBoql fVTJJxG1mY70DJwOuYkhXsxmz/Eln2Qk/lEept5/lOm0SNgQHlcbqWOV/gCNbBMn hnY5TnQy9vFG+fD2Ui07z5Zl/r6gtXDb+WQk0vyjYY35v/eWPut9UYhT4oE8avxp /H+cp1KA/JN6jzWJ8m2/rxLSmQUrJgHfUs7oTZVKfAWXuS8Q3AW4C+WHolOMXMkp do2cv0IX3tOOUHRf5xwk4naNoIBfSDxbLRTrLlfcDvYMxIOtUmZj8z/M8Qia//E= =e3ql -----END PGP SIGNATURE----- |
From: Zhu Yi <yi...@in...> - 2010-02-21 05:38:53
|
On Thu, 2010-02-11 at 01:58 +0800, Daniele C. wrote: > I am using kernel 2.6.33-rc7-00064-gac73fdd (latest git of linus' > tree) and I have been experiencing an issue for more than a month now. > > When the computer resumes from suspend (not hibernation), the RF > killswitch seems ON (although dmesg does not say this, so it is just a > deduction of mine). If I unload ipw2100 and reload it, the killswitch > is disabled and wifi can work regularly. Can you read the ipw2100 sysfs entry "rf_kill" to confirm the rf kill state when this happens? Please also attach your dmesg. > Now I am experiencing a worse issue: the 2nd time I do this, reloading > the module doesn't work anymore, and neither using my modified version > of fsam7400 which did the trick in the past. > > It appears to be an issue of 2.6.33 kernels. Shall I contact some > kernel list? You can include lin...@vg... if you want. If you can do some git bisect, that would be very helpful to identify the regression. Thanks, -yi |
From: Daniele C. <leg...@us...> - 2010-02-19 14:21:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, since some recent changes in linus tree I have been experiencing a weird issue: the hardware will always report "link not ready", unless I reboot and then the link is ready at first hit. Loading/reloading ipw2100 doesn't change anything, and the old bios-tweaking fsam7400 module doesn't help either. This problem couples with the also recent issue happening after restore from suspend/hibernation, which puts the hardware in an unusable status. Best regards, - -- Daniele C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLfp5ZAAoJEON28As9epPAd5YH/jFq2rW9ySGzXct/z18mq/jw rx5tFMXxmZ3kELIp01joC/EQvORpIlIYG/oKalI5hlbrpCxvO41GXuDAobR54+SM D2XPNgYWtHZ18autKOcpurJR18z+TBWDk7b19+r1Z2Jw78P5Lw3MLKwEB51Can5G yEiMw+ipi2qhK/MdWzCvIZJUU3SXy9vb4QYOwIkZPZk4Nrkk43J8Ft/RdWussACv PjM6uC+bv3RVoq4KoFoWomvwYS8iVtYET1Zn+1V+JtEMFKiulyCCisOZYZwXB2g4 /FyBcuBw7V6qF5dSdadKXLtAmqpaUgkoR+ePzZMB5O4jqZgigWip4ArWmuWPo/I= =gJQn -----END PGP SIGNATURE----- |
From: Dani C. <dan...@ya...> - 2010-02-17 08:05:11
|
Dear all, It seems now is working. Now I understand that you can only set the card in monitor when the interface is down, so the sequence of steps are: 1- disable the wlan0 interface: "ifconfig wlan0 down" 2- set wlan0 in monitor mode: "iwconfig wlan0 mode monitor" 3- enable the interface again: "ifconfig wlan0 up" 4- launch wireshark and you can capture L2 Wi-Fi packets at wlan0 :) Thanks to all! Daniel --- El mar, 16/2/10, reinette chatre <rei...@in...> escribió: > De: reinette chatre <rei...@in...> > Asunto: Re: [Ipw2100-devel] Monitor mode in intel 4965 > Para: "Dani Camps" <dan...@ya...> > CC: "Daniele C." <leg...@us...>, "ipw...@li..." <ipw...@li...> > Fecha: martes, 16 de febrero, 2010 12:10 > Daniel, > > On Tue, 2010-02-16 at 00:33 -0800, Dani Camps wrote: > > $ dmesg | grep iwl > > [ 79.894178] iwlagn: Intel(R) > Wireless WiFi Link AGN driver for Linux, 1.3.27k > > [ 79.894180] iwlagn: Copyright(c) > 2003-2009 Intel Corporation > > [ 79.894283] iwlagn 0000:03:00.0: PCI > INT A -> GSI 17 (level, low) -> IRQ 17 > > [ 79.894298] iwlagn 0000:03:00.0: > setting latency timer to 64 > > [ 79.894353] iwlagn 0000:03:00.0: > Detected Intel Wireless WiFi Link 4965AGN REV=0x4 > > [ 79.947732] iwlagn 0000:03:00.0: > Tunable channels: 13 802.11bg, 19 802.11a channels > > [ 79.947843] iwlagn 0000:03:00.0: irq > 32 for MSI/MSI-X > > [ 80.151672] phy0: Selected rate > control algorithm 'iwl-agn-rs' > > [ 80.208005] iwlagn 0000:03:00.0: > firmware: requesting iwlwifi-4965-2.ucode > > [ 80.375869] iwlagn 0000:03:00.0: > loaded firmware version 228.61.2.24 > > [ 80.590246] Registered led device: > iwl-phy0::radio > > [ 80.590263] Registered led device: > iwl-phy0::assoc > > [ 80.590278] Registered led device: > iwl-phy0::RX > > [ 80.590292] Registered led device: > iwl-phy0::TX > > [ 661.371758] Registered led device: > iwl-phy0::radio > > [ 661.371805] Registered led device: > iwl-phy0::assoc > > [ 661.371847] Registered led device: > iwl-phy0::RX > > [ 661.371887] Registered led device: > iwl-phy0::TX > > > > The logs above show that the firmware is loaded, which is > done when you > bring the interface up. You need to set interface in > monitor mode prior > to bringing the interface up. > > Reinette > > > |
From: Dani C. <dan...@ya...> - 2010-02-17 07:57:30
|
Dear Reinette and Daniele, First let me apologize in case I am doing some very basic mistake, I am quite new at this. This is what I see: 1- If the RF killswitch is ON (no wireless), then I can still do "sudo iwconfig wlan0 mode monitor" and it works, here is the output: $sudo iwconfig wlan0 wlan0 IEEE 802.11abgn Mode:Monitor Frequency:2.412 GHz ... However, I can not use the interface because it is down. What I want to do is to use wireshark to capture WLAN frames. I used to do this in the past with other intel drivers, by disassociating from any WLAN network, then setting the card in monitor mode, and then launching wireshark. 2- When I switch OFF the RF killswitch (enable wireless), and without being associated to any WLAN network, the wlan0 interface automatically switches to mode managed, and when I try to set it back to monitor mode it fails: $ sudo iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated $ sudo iwconfig wlan0 mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Device or resource busy. How can I set the card to monitor mode when the interface is enabled but not associated to any network? Many thanks! Daniel --- El mar, 16/2/10, reinette chatre <rei...@in...> escribió: > De: reinette chatre <rei...@in...> > Asunto: Re: [Ipw2100-devel] Monitor mode in intel 4965 > Para: "Dani Camps" <dan...@ya...> > CC: "Daniele C." <leg...@us...>, "ipw...@li..." <ipw...@li...> > Fecha: martes, 16 de febrero, 2010 12:10 > Daniel, > > On Tue, 2010-02-16 at 00:33 -0800, Dani Camps wrote: > > $ dmesg | grep iwl > > [ 79.894178] iwlagn: Intel(R) > Wireless WiFi Link AGN driver for Linux, 1.3.27k > > [ 79.894180] iwlagn: Copyright(c) > 2003-2009 Intel Corporation > > [ 79.894283] iwlagn 0000:03:00.0: PCI > INT A -> GSI 17 (level, low) -> IRQ 17 > > [ 79.894298] iwlagn 0000:03:00.0: > setting latency timer to 64 > > [ 79.894353] iwlagn 0000:03:00.0: > Detected Intel Wireless WiFi Link 4965AGN REV=0x4 > > [ 79.947732] iwlagn 0000:03:00.0: > Tunable channels: 13 802.11bg, 19 802.11a channels > > [ 79.947843] iwlagn 0000:03:00.0: irq > 32 for MSI/MSI-X > > [ 80.151672] phy0: Selected rate > control algorithm 'iwl-agn-rs' > > [ 80.208005] iwlagn 0000:03:00.0: > firmware: requesting iwlwifi-4965-2.ucode > > [ 80.375869] iwlagn 0000:03:00.0: > loaded firmware version 228.61.2.24 > > [ 80.590246] Registered led device: > iwl-phy0::radio > > [ 80.590263] Registered led device: > iwl-phy0::assoc > > [ 80.590278] Registered led device: > iwl-phy0::RX > > [ 80.590292] Registered led device: > iwl-phy0::TX > > [ 661.371758] Registered led device: > iwl-phy0::radio > > [ 661.371805] Registered led device: > iwl-phy0::assoc > > [ 661.371847] Registered led device: > iwl-phy0::RX > > [ 661.371887] Registered led device: > iwl-phy0::TX > > > > The logs above show that the firmware is loaded, which is > done when you > bring the interface up. You need to set interface in > monitor mode prior > to bringing the interface up. > > Reinette > > > |
From: reinette c. <rei...@in...> - 2010-02-16 17:11:07
|
Daniel, On Tue, 2010-02-16 at 00:33 -0800, Dani Camps wrote: > $ dmesg | grep iwl > [ 79.894178] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k > [ 79.894180] iwlagn: Copyright(c) 2003-2009 Intel Corporation > [ 79.894283] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > [ 79.894298] iwlagn 0000:03:00.0: setting latency timer to 64 > [ 79.894353] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x4 > [ 79.947732] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 19 802.11a channels > [ 79.947843] iwlagn 0000:03:00.0: irq 32 for MSI/MSI-X > [ 80.151672] phy0: Selected rate control algorithm 'iwl-agn-rs' > [ 80.208005] iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode > [ 80.375869] iwlagn 0000:03:00.0: loaded firmware version 228.61.2.24 > [ 80.590246] Registered led device: iwl-phy0::radio > [ 80.590263] Registered led device: iwl-phy0::assoc > [ 80.590278] Registered led device: iwl-phy0::RX > [ 80.590292] Registered led device: iwl-phy0::TX > [ 661.371758] Registered led device: iwl-phy0::radio > [ 661.371805] Registered led device: iwl-phy0::assoc > [ 661.371847] Registered led device: iwl-phy0::RX > [ 661.371887] Registered led device: iwl-phy0::TX > The logs above show that the firmware is loaded, which is done when you bring the interface up. You need to set interface in monitor mode prior to bringing the interface up. Reinette |