Results 1 to 9 of 9

Thread: aircrack-ptw cannot open file

  1. #1
    Just burned his ISO
    Join Date
    Mar 2006
    Posts
    17

    Default aircrack-ptw cannot open file

    So I captured around 30,000 ivs from a AP that i know uses 64bit wep. When i run aircrak-ptw cap-01.ivs, the first 2 lines are the standard aircrack-ptw info and the visit our site line, but then i get an error, cannot open file. Anyone know why this is.

  2. #2
    Member
    Join Date
    Mar 2007
    Posts
    121

    Default

    aircrack-ptw wont read *.ivs files only *.cap files

  3. #3
    Just burned his ISO
    Join Date
    Mar 2006
    Posts
    17

    Default

    how to i make airodump-ng save as .cap? do i have to do
    > airodump-ng -w cap.cap ath1?

    because i think that when i was capping packets last time i just did cap and left out the .cap part

    thanks for the info

  4. #4
    Member
    Join Date
    Mar 2007
    Posts
    121

    Default

    dont need to put any thing as *.cap is it's default

  5. #5
    Member
    Join Date
    Mar 2007
    Posts
    121

    Default

    hey there again, here is what i use for airodump:

    airodump-ng -w abc -c 001 wlan0

    so that gives me a abc-01.cap file ect

  6. #6
    Just burned his ISO
    Join Date
    Mar 2006
    Posts
    17

    Default

    cool thanks. i wonder why mine saved as .ivs last time i used airodump :S

  7. #7
    Moderator theprez98's Avatar
    Join Date
    Jan 2010
    Location
    Maryland
    Posts
    2,533

    Default

    Quote Originally Posted by hyperlitemofo View Post
    cool thanks. i wonder why mine saved as .ivs last time i used airodump :S
    You probably used the -i (--ivs) flag, which saves only captured IVs as opposed to everything else.
    "\x74\x68\x65\x70\x72\x65\x7a\x39\x38";

  8. #8
    Just burned his ISO
    Join Date
    Mar 2006
    Posts
    17

    Default

    now that i think of it. I probably did

    airodump-ng -w cap -i ath0

    because i forgot that airodump doesnt use -i to identify the interface :P

  9. #9
    Moderator theprez98's Avatar
    Join Date
    Jan 2010
    Location
    Maryland
    Posts
    2,533

    Default

    Quote Originally Posted by hyperlitemofo View Post
    now that i think of it. I probably did

    airodump-ng -w cap -i ath0

    because i forgot that airodump doesnt use -i to identify the interface :P
    There you go.
    "\x74\x68\x65\x70\x72\x65\x7a\x39\x38";

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •