Two Brief Questions

[portcontrol7]

Hi,

While following along with Darren on a couple episodes I ran into some issues:

#1:

root@bt:~#!/usr/bin/expect

bash:!/usr/bin/expect: event not found

root@bt:~# expect

expect1.1>

Expect is there, but when I start off with !/ it don't work.

2#

I have recently installed airdrop-ng on my Backtrack Linux. I have an Alfa AWUSO36H card, and everything works fine it seems except airdrop. When I run airdrop-ng it promptly tells me that "Interface mon0 does not exist", even though I'm successfully using mon0 with airodump-ng at the same time.

Much obliged for any help!

[Pwnd2Pwnr]

Unfortunately, you may have to revert to Google university... it would probably be quicker to find the fix through the airmon-ng tutorials...

Best of luck (I personally hate airmon... it seems to crash on my system a lot).

[Infiltrator]

I have recently installed airdrop-ng on my Backtrack Linux. I have an Alfa AWUSO36H card, and everything works fine it seems except airdrop. When I run airdrop-ng it promptly tells me that "Interface mon0 does not exist", even though I'm successfully using mon0 with airodump-ng at the same time.

Much obliged for any help!

Have you tried, running those tools individually and at different times. Rather than running both at the same time?

[portcontrol7]

From my understanding you must have the mon0 interface in monitor mode, and the only way I know how to do this is with airmen-ng on wlan0, which creates the mon0 interface. I am going to upgrade to backtrack 5 R3 and see if that helps.

[Sitwon]

Regarding your first question, I think you may have misunderstood something.

If you're writing a script you start the script with "#!/usr/bin/expect" on the first line so that the shell knows to run the commands inside the script through the expect interpreter. However on the command-line you should not try to invoke !/usr/bin/expect, because in the shell any command that starts with ! is a history command. You basically told it to search the history for a matching command, but since none exists it gave you an error. You probably meant to execute /usr/bin/expect (no !), but there's no reason to do that, since as you demonstrated it's already in your $PATH so you can call it without using the full path.