airbase-ng showing 2 essids since Kali update/upgrade

[SAH1376]

Hi all,

Ive been playing with airbase-ng creating APs with 0 issues for a little while.
Yesterday I performed

apt-get update
apt-get upgrade

Since then airbase has been playing up.
It appears to be struggling to apply the essid name.

Viewing on a client i will see the AP "wifi" which I assigned and also "default" AP
airodump-ng shows the essid switching between "wifi" and "default"

These are the commands Im using

root@kali:~# airmon-ng check kill

root@kali:~# airmon-ng start wlan0


PHY	Interface	Driver		Chipset

phy0	wlan0		brcmsmac	Broadcom on bcma bus, information limited

		(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
		(mac80211 station mode vif disabled for [phy0]wlan0)

Check monitor mode

root@kali:~# iwconfig
wlan0mon  IEEE 802.11bgn  Mode:Monitor  Frequency:2.457 GHz  Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          
lo        no wireless extensions.

eth0      no wireless extensions.

Start airbase-ng

airbase-ng -e wifi -c 2  wlan0mon

Now seeing 2 essids on my clients "wifi" and "default"

airodump-ng output:

root@kali:~# airodump-ng wlan0mon -c 2

 CH  2 ][ Elapsed: 1 min ][ 2015-12-08 09:58                                         
                                                                                                  
 BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID
                                                                                                  
 XX:XX:XX:XX:XX:XX    0 100     1434        0    0   2  54   OPN              default

The essid in the above output flicks between the 2 stated above, one given in the airbase-ng line and the other is the default.


Im now baffled as to what to try next. Everything has been working as it should up until yesterday. Does it look like a driver issue?

Any and all suggestions welcome.



Some support info;

root@kali:~# ifconfig
eth0      Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX  
          inet addr:XX.XX.XX.XX  Bcast:XX.XX.XX.XX  Mask:255.255.255.0
          inet6 addr: XXX.XXX.XXX.XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8481 (8.2 KiB)  TX bytes:9380 (9.1 KiB)
          Interrupt:18 

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:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1200 (1.1 KiB)  TX bytes:1200 (1.1 KiB)

wlan0     Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX  
          inet addr:XX.XX.XX.XX  Bcast:XX.XX.XX.XX  Mask:255.255.255.0
          inet6 addr: XXX.XXX.XXX.XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:97 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:22625 (22.0 KiB)  TX bytes:9337 (9.1 KiB)

root@kali:~# iwconfig
wlan0     IEEE 802.11bgn  ESSID:"XXXXXX"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: XX:XX:XX:XX:XX:XX   
          Bit Rate=1 Mb/s   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:49   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

root@kali:~# lspci -vnn |grep Network
04:00.0 Network controller [0280]: Broadcom Corporation BCM43225 802.11b/g/n [14e4:4357] (rev 01)

[grid]

That's odd, I'm running the newest version of the aircrack-ng suite, with an Alfa AWUS036H, and don't see that behavior.

A long shot, but have you tried naming the access point something else, like test? Maybe wifi is some sort of reserved word in airbase-ng, and it's causing a conflict?

[SAH1376]

Just tried a few different essids, all produce the same results.

[grid]

Hmm, in that case, I'd remove and reinstall the aircrack-ng suite. Maybe something got messed up

[Rickybobbyact]

SAH1376,
I am getting the exact same problem.
I have two wifi dongles and same fault occurs for both.
Have you had any progress with this?
Updates, upgrades not fixing.
Cheers.

[SAH1376]

No progress here. Fully removed and re installed, no change.

Was beginning to think it was just me.

[mmusket33]

Try putting the -P respond to all probes in the command line and see what occurs. Then take it out and see what happens. Also technically from the help files there is no -e command only --essid. So try using --essid and make sure there is no space in the essid name for your test. If that does not work try writing a text file with the essid name on the first line. Next use --essids /root/filename.txt or --essids root/filename.txt or --essids filename. One of these three will work if your text file is in root If you are running airbase-ng in a xterm window write us and we will provide more info.

See airbase-ng --help for expansions.

[SAH1376]

Hi, thanks for helping!

I too noticed that the help says --essid rather than -e so my last tests were using that instead.

I have now tried with and without -P, same results.

Also tried --essids filename.txt, also with and without -P, all with no change.

Correct essid and default both still showing on clients and airodump.

[mmusket33]

The simple solution can be found here.

https://forums.kali.org/showthread.p...3946#post53946


Thanks for the headsup

MTeams