usr/local/bin/start-kismet-ng Bug Fixed!!

[drpepperONE]

Hy guyz !!

I fixed the bugged /usr/local/bin/start-kismet-ng script that it could be start kismet.

The probelm was that the script uses a wrong order of capturesource variable for kismet.
I changed the order and the right sintax with coma.

I also changed a bug name about ksmet driver supported for rt8180 because the script uses the wrong name r8180.

I tested the new fixed script with atheros, ralink, realtek chipset wifi-cards and it works.

So what todo??

U must add the following code at the end of the script:

find lines :

eval "/usr/local/sbin/airmon-ng start $iface"
sleep 2

and add following code:

if [ $DEVCOUNT -gt 1 ]
then

DRP_DEVICE_NAME=`echo ${A_ASKINTERFACE}|cut -d, -f1`

DRP_DRIVER_NAME=`echo ${A_ASKINTERFACE} | cut -d , -f2| awk -F' ' '{print $1}'`

        if [ $DRP_DRIVER_NAME = "r8180" ]

                then

                        DRP_DRIVER_NAME=rt8180

                fi
        konsole -e kismet -c $DRP_DRIVER_NAME,$DRP_DEVICE_NAME,$DRP_DRIVER_NAME

else
DRP_DEVICE_NAME=`echo ${A_WLAN_MENU}|cut -d, -f1`

DRP_DRIVER_NAME=`echo ${A_WLAN_MENU} | cut -d , -f2| awk -F' ' '{print $1}'`

if [ $DRP_DRIVER_NAME = "r8180" ]

        then
                #
                #
                DRP_DRIVER_NAME=rt8180

        fi

konsole -e kismet -c $DRP_DRIVER_NAME,$DRP_DEVICE_NAME,$DRP_DRIVER_NAME
fi

Remove the "konsole -e kismet" final line in the original script.

I wish that it could be help someone.!!

Byezzzzzz by drpepperONE.

[PrairieFire]

Tested and could be considered a partial fix. Failure to append correct source=driver,interface,name to /usr/local/etc/kismet.conf still exists though.

[drpepperONE]

Tested and could be considered a partial fix. Failure to append correct source=driver,interface,name to /usr/local/etc/kismet.conf still exists though.

Hi...the goal of the start-kismet-ng script is to launch kismet without configure kismet.conf.
Infact I changed for this reason.
So I had share my work with your wonderful community!!

Your are THE BEST!!!!!!

[purehate]

Although I appreciate the input to bt3 and by no means want to discourage you I don't consider this a fix. In my opinion the correct protocol for kismet is to edit the .conf file with your interface and then start kismet from the command line like this.
bt~#kismet
and it will start right up. I personally edit my kde menu to reflect that and not the script however if this helps some people I'm glad.

[drpepperONE]

Although I appreciate the input to bt3 and by no means want to discourage you I don't consider this a fix. In my opinion the correct protocol for kismet is to edit the .conf file with your interface and then start kismet from the command line like this.
bt~#kismet
and it will start right up. I personally edit my kde menu to reflect that and not the script however if this helps some people I'm glad.

Hi pureh@te, I changed and fixed the start-kismet-ng script because it's the default script item that its' launched by BT3 beta official default menu.

The aim of the start-kismet-ng script is to auto-configure kismet for the most popular wirless chipset cards.

I agree with u, that for some special and particural wireless cards, we must configure the kismet.conf.


In the previus BT2 final i used always the default menu used to start kismet that have the same script (start-kismet-ng) and it always worked fine with differets cards.


So I think that what I did it's only a little workaround

[PrairieFire]

Noted as possible fix rt8180, start-kismet-ng still fails on madwifi, hostap, iwlwifi, ipwraw,......

[iicocuk]

thank you. it works

[Re@lity]

Nice one - I'll give it a try too.....

I always liked the auto-config feature - saves a lot of time/hassle when changing cards alot

EDIT:

Works with eeepc built-in Atheros and Alfa AWUS036H RTL 8187

When I put the revised script onto a "normal" laptop (pc-card slot) in a while, I'll test with most other chipsets too

Nice one drpepperONE

[drpepperONE]

Nice one - I'll give it a try too.....

I always liked the auto-config feature - saves a lot of time/hassle when changing cards alot

EDIT:

Works with eeepc built-in Atheros and Alfa AWUS036H RTL 8187

When I put the revised script onto a "normal" laptop (pc-card slot) in a while, I'll test with most other chipsets too

Nice one drpepperONE

Thank you Re@lity. If there is some chipset that does not work tell me that I will fix.

Thank you.

[imported_ecsployt]

"Sorry I could not identify any wlan interfaced I will exit now"

Doesn't work for me.
I have rt8187 card. Using BT3 via VMware install.