Airmon-ng goes weird!

[JackBruno]

hey all of you awesome hackers. i just need your help for a bit. i installed airmon-ng package suit... for security reasons e.g exploiting own routers to detect some bugs. but. airmon-ng start to act weird...

Code: [Select]

Interface    Chipset        Driver

eth1        Broadcom    wl - [phy0]mon0: ERROR while getting interface flags: No such device

                (monitor mode enabled on mon0)
weird right? but i tried to reinstall the bcmw-kernel-source... and reinstall aircrack-ng package
nothing happens!

i hacked a lot of wifi using different techniques. but now i can't turn my wireless adapter into monitor mode. my perl programs are useless!

[Kulverstukas]

Do you run it as root?

[JackBruno]

yeah... i always logged in as root... and thanks for fast reply!

[proxx]

hey all of you awesome hackers. i just need your help for a bit. i installed airmon-ng package suit... for security reasons e.g exploiting own routers to detect some bugs. but. airmon-ng start to act weird...

Code: [Select]

Interface    Chipset        Driver

eth1        Broadcom    wl - [phy0]mon0: ERROR while getting interface flags: No such device

                (monitor mode enabled on mon0)
weird right? but i tried to reinstall the bcmw-kernel-source... and reinstall aircrack-ng package
nothing happens!

i hacked a lot of wifi using different techniques. but now i can't turn my wireless adapter into monitor mode. my perl programs are useless!

Funny how you act like you pwn the planet but are incapable of debugging simple shit.

eth1        Broadcom    wl - [phy0]mon0: ERROR while getting interface flags: No such device
^
Does this device even exist?

Post the output of ifconfig -a and iwconfig.

[JackBruno]

Okay as you wish.

Code: [Select]

ifconfig -a
eth0      Link encap:Ethernet  HWaddr e8:11:32:2e:a6:fd 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:18

eth1      Link encap:Ethernet  HWaddr 00:1b:b1:a9:ac:e0 
          inet addr:192.168.1.124  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:b1ff:fea9:ace0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25357 errors:8 dropped:0 overruns:0 frame:34474
          TX packets:29140 errors:34 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17317109 (17.3 MB)  TX bytes:4038775 (4.0 MB)
          Interrupt:16

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:43 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7460 (7.4 KB)  TX bytes:7460 (7.4 KB)
and then...

Code: [Select]

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11abg  ESSID:"KISSHEART" 
          Mode:Managed  Frequency:2.437 GHz  Access Point: C0:C1:C0:2B:E4:89   
          Bit Rate=5.5 Mb/s   Tx-Power=200 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=26/70  Signal level=-84 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


[proxx]

Its curious that its named eth1..
This is not at all expected behaviour.

Try throwing the interface down;  ifconfig eth1 down
Then try recreating the mon interface.

[JackBruno]

lol.. that is the first thing that i do! when i got this error...

[proxx]

Run : airmon-ng check eth1
If anything shows up in dmesg post that aswel.

[JackBruno]

okay... i already did this but. here it is

Code: [Select]

airmon-ng check eth1

PID Name
1019 avahi-daemon
1020 avahi-daemon
3464 wpa_supplicant
3487 dhclient
Process with PID 3464 (wpa_supplicant) is running on interface eth1
Process with PID 3487 (dhclient) is running on interface eth1
and what do you mean about dmesg command? do i need to copy that crap and paste it here? thats kinda
longer

[techb]

...
and what do you mean about dmesg command? do i need to copy that crap and paste it here? thats kinda
longer

grep with "eth" or something.

[JackBruno]

Okay i run ...

Code: [Select]

dmesg | grep eth1

[   19.894588] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.20.155.1 (r326264)
[  233.870793] ERROR @wl_notify_scan_status : eth1 Scan_results error (-22)
i tried to remove my interface from wicd and run it... same!

[techb]

Do you have the right drivers? Broadcom is a bitch btw.

[proxx]

Looks like your network manager is locking the device.
Make sure you kill the WICD (daemon).

Those PID's are locking the interface.
That  error from DMESG is also an idication for this behaviour.

[JackBruno]

Code: [Select]

airmon-ng check kill
...
...
...
killing all those process
...

Code: [Select]

dmesg | grep eth1
....
[same as above]