Thanks for the advice guys. yup, tried monitoring despite (monitor mode) not by the device, was hoping might be a little bug or what not but nope, no dice. this is what i got.
morbid@crypt:~$ sudo wash -i mon0
Wash v1.4 WiFi Protected Setup Scan Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <
cheffner@tacnetsol.com>
[X] ERROR: Failed to open 'mon0' for capturing
morbid@crypt:~$ sudo wash -i wlan1
Wash v1.4 WiFi Protected Setup Scan Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <
cheffner@tacnetsol.com>
[X] ERROR: Failed to compile packet filter
morbid@crypt:~$
[note: above im using a external wireless card explaing the -i wlan1]
the Distro that im using is backbox (gave up kali / BT once trying it) i tried the kill -9 approach and no luck, the processes respawned. here is the output
morbid@crypt:~$ sudo airmon-ng
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ sudo airmon-ng start -i wlan1
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
828 NetworkManager
5025 avahi-daemon
5026 avahi-daemon
5045 wpa_supplicant
5073 dhclient
Process with PID 5073 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ sudo kill -9 828
morbid@crypt:~$ sudo kill -9 5025
morbid@crypt:~$ sudo kill -9 5026
morbid@crypt:~$ sudo kill -9 5045
morbid@crypt:~$ sudo kill -9 5073
morbid@crypt:~$ sudo airmon-ng start -i wlan1
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
6259 NetworkManager
6344 avahi-daemon
6345 avahi-daemon
6356 wpa_supplicant
6390 dhclient
Process with PID 6390 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ clear
morbid@crypt:~$ sudo airmon-ng
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ sudo airmon-ng start -i wlan1
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
6259 NetworkManager
6344 avahi-daemon
6345 avahi-daemon
6356 wpa_supplicant
6390 dhclient
Process with PID 6390 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ sudo kill 6259
morbid@crypt:~$ sudo kill 6344
morbid@crypt:~$ sudo kill 6345
morbid@crypt:~$ sudo kill 6356
morbid@crypt:~$ sudo kill 6390
morbid@crypt:~$ sudo airmon-ng start -i wlan1
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
7609 NetworkManager
7625 avahi-daemon
7626 avahi-daemon
7731 wpa_supplicant
7758 dhclient
Process with PID 7758 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
morbid@crypt:~$ sudo kill 7609
morbid@crypt:~$ sudo kill 7731
morbid@crypt:~$ sudo kill 7758
morbid@crypt:~$ sudo kill -9 7625
morbid@crypt:~$ sudo kill -9 7731
morbid@crypt:~$ sudo airmon-ng start -i wlan1
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
8291 NetworkManager
8306 wpa_supplicant
8309 dhclient
8414 avahi-daemon
8415 avahi-daemon
Process with PID 8309 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan1 Atheros AR9271 ath9k - [phy1]
wlan0 Intel 5300AGN iwlwifi - [phy0]
i'll admit im not familiar enough to disable at run levels. I'm going to try the link ph0bYx suggested and see what happens.
----------- minutes later ------------------
so tried to disable with the gedit approach. here is my daemon, with the value set as zero , does the same as the zero set as 1
# 1 = Try to detect unicast dns servers that serve .local and disable avahi in
# that case, 0 = Don't try to detect .local unicast dns servers, can cause
# troubles on misconfigured networks
AVAHI_DAEMON_DETECT_LOCAL=0