Jump to content

Two Brief Questions


portcontrol7
 Share

Recommended Posts

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!

Link to comment
Share on other sites

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).

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...