Results 1 to 5 of 5

Thread: airdrop-ng and pylorcon

Hybrid View

  1. #1
    My life is this forum Snayler's Avatar
    Join Date
    Jan 2010
    Posts
    1,418

    Default airdrop-ng and pylorcon FIX

    airdrop-ng is unable to function because pylorcon is missing.
    Code:
    root@bt:/pentest/wireless/aircrack-ng/scripts/airdrop-ng# ./airdrop-ng -i wlan0 -t /root/testap.csv -r /root/rules
    
    #################################################
    #             Welcome to AirDrop-ng             #
    #################################################
    
    
    Pylorcon error, do you have it installed?
    
    Airdrop-ng will now exit
    Sent 0 Packets
    
    Exiting Program, Please take your card wlan0 out of monitor mode
    Trying to install it results in a series of errors, as follows:
    Code:
    Would you like to install pylorcon? (y/n): y
    tar: Record size = 8 blocks
    pylorcon/
    pylorcon/tx.py
    pylorcon/setup.py
    pylorcon/README
    pylorcon/pylorcon.c
    pylorcon/LICENSE
    running install
    running build
    running build_ext
    building 'pylorcon' extension
    gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.6 -c pylorcon.c -o build/temp.linux-i686-2.6/pylorcon.o
    pylorcon.c:8:20: error: Python.h: No such file or directory
    pylorcon.c:9:26: error: structmember.h: No such file or directory
    pylorcon.c:13: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:16: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:74: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:81: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:118: error: expected specifier-qualifier-list before ‘PyObject_HEAD’
    pylorcon.c: In function ‘Lorcon_dealloc’:
    pylorcon.c:128: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:129: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:131: error: ‘Lorcon’ has no member named ‘ob_type’
    pylorcon.c:131: error: ‘PyObject’ undeclared (first use in this function)
    pylorcon.c:131: error: (Each undeclared identifier is reported only once
    pylorcon.c:131: error: for each function it appears in.)
    pylorcon.c:131: error: expected expression before ‘)’ token
    pylorcon.c: At top level:
    pylorcon.c:136: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:151: error: expected declaration specifiers or ‘...’ before ‘PyObject’
    pylorcon.c:151: error: expected declaration specifiers or ‘...’ before ‘PyObject’
    pylorcon.c: In function ‘Lorcon_init’:
    pylorcon.c:152: error: ‘PyObject’ undeclared (first use in this function)
    pylorcon.c:152: error: ‘iface’ undeclared (first use in this function)
    pylorcon.c:152: error: ‘driver’ undeclared (first use in this function)
    pylorcon.c:152: warning: left-hand operand of comma expression has no effect
    pylorcon.c:155: warning: implicit declaration of function ‘PyArg_ParseTupleAndKeywords’
    pylorcon.c:155: error: ‘args’ undeclared (first use in this function)
    pylorcon.c:155: error: ‘kwds’ undeclared (first use in this function)
    pylorcon.c:161: warning: implicit declaration of function ‘Py_INCREF’
    pylorcon.c:162: error: ‘Lorcon’ has no member named ‘iface’
    pylorcon.c:164: error: ‘Lorcon’ has no member named ‘driver’
    pylorcon.c:166: error: ‘Lorcon’ has no member named ‘drivertype’
    pylorcon.c:166: warning: implicit declaration of function ‘PyString_AsString’
    pylorcon.c:166: error: ‘Lorcon’ has no member named ‘driver’
    pylorcon.c:168: error: ‘Lorcon’ has no member named ‘drivertype’
    pylorcon.c:169: warning: implicit declaration of function ‘PyErr_SetString’
    pylorcon.c:169: error: ‘LorconError’ undeclared (first use in this function)
    pylorcon.c:173: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:173: error: ‘Lorcon’ has no member named ‘iface’
    pylorcon.c:174: error: ‘Lorcon’ has no member named ‘drivertype’
    pylorcon.c:175: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:179: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:180: error: ‘Lorcon’ has no member named ‘in_tx’
    pylorcon.c:183: error: ‘Lorcon’ has no member named ‘in_packet’
    pylorcon.c: At top level:
    pylorcon.c:191: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:201: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:238: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:269: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:297: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:310: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:327: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:372: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:422: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:455: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:496: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:502: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
    pylorcon.c:523: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘Lorcon_members’
    pylorcon.c:527: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘Lorcon_methods’
    pylorcon.c:562: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘LorconType’
    pylorcon.c:604: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pylorcon_methods’
    pylorcon.c: In function ‘initpylorcon’:
    pylorcon.c:617: error: ‘PyObject’ undeclared (first use in this function)
    pylorcon.c:617: error: ‘m’ undeclared (first use in this function)
    pylorcon.c:619: warning: implicit declaration of function ‘PyType_Ready’
    pylorcon.c:619: error: ‘LorconType’ undeclared (first use in this function)
    pylorcon.c:622: warning: implicit declaration of function ‘Py_InitModule3’
    pylorcon.c:622: error: ‘pylorcon_methods’ undeclared (first use in this function)
    pylorcon.c:628: error: ‘LorconError’ undeclared (first use in this function)
    pylorcon.c:628: warning: implicit declaration of function ‘PyErr_NewException’
    pylorcon.c:630: warning: implicit declaration of function ‘PyModule_AddObject’
    pylorcon.c:633: error: expected expression before ‘)’ token
    error: command 'gcc' failed with exit status 1
    ________________________________

    EDIT: Found the solution:
    Code:
    apt-get install python-dev
    Last edited by Snayler; 11-07-2011 at 04:50 PM. Reason: Solution Found

  2. #2
    Just burned his ISO
    Join Date
    Sep 2010
    Posts
    1

    Thumbs up Re: airdrop-ng and pylorcon

    It worked for me in BT5. Problem resolved

  3. #3
    Just burned his ISO
    Join Date
    Jan 2011
    Posts
    5

    Default Re: airdrop-ng and pylorcon

    We use airdrop-ng extensively thru Backtrack 4(BT4) in conjunction with the weaknet WPA phishing attack to socially engineer WPA keys.

    Getting BT5 to run though is not so straight forward. There are about four downloads required to get the program to run and even then it crashes the computer within three minutes beginning the rule based attack. As the program runs fine with BT4 we could use it instead but be would like to solve the BT5 crash problem.

    Any info would be appreciated

  4. #4
    Just burned his ISO
    Join Date
    Jan 2011
    Posts
    5

    Default Re: airdrop-ng and pylorcon

    We attempted to install airdrop-ng to Backtrack 5 R3. First the install.py no longer exists. When we finnally got it installed we got a lorcon2 not installed error message. When you go to the read files it tells you to install lorcan 2 from a site BUT when you try and find the files we were unable to find a tarball for lorcon2. Just a load of script files which just left us wondering how long and which files. We can always use mdk3 in some ways it is easier then airdrop-ng however we would like to get the program up and running but the effort doesnot seem warrant the time as we do have the mdk3 alternative.

    If you run airdrop-ng from BT5R1 and it crashes set the tranmit time to one(1) second or greater and the program runs just fine. These is especially true if you are running BT5R1 from a pen drive

  5. #5
    Member stepking2's Avatar
    Join Date
    May 2012
    Posts
    83

    Default Re: airdrop-ng and pylorcon

    To lorcon, use the SVN link in the README file for Airdrop-ng.

Similar Threads

  1. Problem with Airdrop
    By PJK33NAN in forum Beginners Forum
    Replies: 2
    Last Post: 09-05-2010, 11:00 PM
  2. Airdrop-ng possible problem help.
    By pilotguy in forum Beginners Forum
    Replies: 3
    Last Post: 05-29-2010, 07:37 PM
  3. Instalar o Airdrop-ng
    By firebits in forum Tutoriais e Howtos
    Replies: 0
    Last Post: 04-16-2010, 12:19 PM
  4. Airdrop-ng When Released
    By Mr-Protocol in forum Tool Requests
    Replies: 10
    Last Post: 02-18-2010, 02:49 PM

Posting Permissions

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