View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001110Kali LinuxGeneral Bugpublic2014-03-25 19:172018-01-29 11:17
Reportertabbek Assigned Tomuts  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionsuspended 
Summary0001110: airbase-ng, airodump-ng, and other *-ng suit tools channel -1
Description

While trying to use *-ng tools, specifically airbase-ng and airodump-ng, I get channel -1 errors.

I reviewed https://bugs.kali.org/view.php?id=1000 and I have used "airmon-ng check kill" prior to creating monitor interfaces on a channel as suggested in that closed bug, but I still encounter the -1 error.

Steps To Reproduce

root@toadstool:~# ifconfig wlan3
wlan3 Link encap:Ethernet HWaddr 00:0f:54:18:10:2d
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)

root@toadstool:~# airmon-ng check
root@toadstool:~# airmon-ng check kill
root@toadstool:~# airmon-ng start wlan3 6

Interface Chipset Driver

wlan3 Ralink RT2870/3070 rt2800usb - [phy1]
(monitor mode enabled on mon0)
wlan0 Atheros AR9285 ath9k - [phy0]

root@toadstool:~# ifconfig mon0
mon0 Link encap:UNSPEC HWaddr 00-0F-54-18-10-2C-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17180 errors:0 dropped:17180 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1241264 (1.1 MiB) TX bytes:0 (0.0 B)

root@toadstool:~# ifconfig mon0 up
root@toadstool:~# airbase-ng -c 6 -e testnet mon0
12:21:55 Created tap interface at0
12:21:55 Trying to set MTU on at0 to 1500
12:21:55 Trying to set MTU on mon0 to 1800
12:21:55 Access Point with BSSID 00:0F:54:18:10:2C started.
Error: Got channel -1, expected a value > 0.
^C

Additional Information

root@toadstool:~# uname -a
Linux toadstool 3.12-kali1-686-pae 0000001 SMP Debian 3.12.6-2kali1 (2014-01-06) i686 GNU/Linux

root@toadstool:~# iwconfig
wlan3 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on

wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

lo no wireless extensions.

mon0 IEEE 802.11bgn Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on

eth0 no wireless extensions.

Activities

muts

muts

2014-04-02 19:04

reporter   ~0001654

Unable to reproduce.
tabbek

tabbek

2014-04-03 16:20

reporter   ~0001662

What data would you like for investigation? I can reproduce at will.
muts

muts

2014-04-03 17:13

reporter   ~0001663

Last edited: 2014-04-03 17:14

This is how i tried to reproduce the steps:

http://pastebin.com/ua3HyRSd

The last airodump-ng command settles on channel 6, and not -1.
tabbek

tabbek

2014-04-03 23:07

reporter   ~0001664

One difference I noted, but I dont't think is the issue:
amd64 vs 686-pae
Don't have access to another box or VM host at the moment to test this specifically, but could be arranged.

I also saw that the monitoring interface setup was being done differently:
root@toadstool:~# airmon-ng start wlan3 6
vs
root@kali~# airmon-ng start wlan0

When following the sequence followed by muts, I had success once and only once on a fresh boot, fresh usb-plug-in. I killed airbase-ng with ctrl-c, and stopped mon0 with airmon-ng stop mon0. Subsequent attempts would result in the -1 channel issue.

http://pastebin.com/AFbrW6TM
g0tmi1k

g0tmi1k

2018-01-29 11:17

administrator   ~0007963

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2014-03-25 19:17 tabbek New Issue
2014-04-02 19:04 muts Note Added: 0001654
2014-04-02 19:04 muts Status new => closed
2014-04-02 19:04 muts Assigned To => muts
2014-04-02 19:04 muts Resolution open => unable to reproduce
2014-04-03 16:20 tabbek Note Added: 0001662
2014-04-03 16:20 tabbek Status closed => feedback
2014-04-03 16:20 tabbek Resolution unable to reproduce => reopened
2014-04-03 17:13 muts Note Added: 0001663
2014-04-03 17:14 muts Note Edited: 0001663
2014-04-03 23:07 tabbek Note Added: 0001664
2014-04-03 23:07 tabbek Status feedback => assigned
2014-05-12 17:16 xploitx Issue cloned: 0001228
2018-01-29 11:17 g0tmi1k Status assigned => closed
2018-01-29 11:17 g0tmi1k Resolution reopened => suspended
2018-01-29 11:17 g0tmi1k Note Added: 0007963