Results 1 to 4 of 4

Thread: Airpwn

  1. #1
    Just burned his ISO
    Join Date
    Dec 2007
    Posts
    9

    Default Airpwn

    I did what was said to "fix Airpwn" located here:
    http|//forums.remote-exploit.org/showthread.php?t=11475&highlight=airpwn
    and i get the following error:
    Code:
    bt lorcon # ./configure && make && make install
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking for gcc... gcc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ANSI C... none needed
    checking for a sed that does not truncate output... /usr/bin/sed
    checking for egrep... grep -E
    checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
    checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
    checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependent libraries... pass_all
    checking how to run the C preprocessor... gcc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking how to run the C++ preprocessor... g++ -E
    checking for g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for epcf90... no
    checking for f95... no
    checking for fort... no
    checking for xlf95... no
    checking for ifc... no
    checking for efc... no
    checking for pgf95... no
    checking for lf95... no
    checking for gfortran... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether  accepts -g... no
    checking the maximum length of command line arguments... 32768
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if gcc static flag  works... yes
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking for platform-specific compiler flags... none needed
    checking whether byte ordering is bigendian... no
    checking for ANSI C header files... (cached) yes
    checking for sys/wait.h that is POSIX.1 compatible... yes
    checking fcntl.h usability... yes
    checking fcntl.h presence... yes
    checking for fcntl.h... yes
    checking sys/ioctl.h usability... yes
    checking sys/ioctl.h presence... yes
    checking for sys/ioctl.h... yes
    checking sys/time.h usability... yes
    checking sys/time.h presence... yes
    checking for sys/time.h... yes
    checking for unistd.h... (cached) yes
    checking net/if_arp.h usability... yes
    checking net/if_arp.h presence... yes
    checking for net/if_arp.h... yes
    checking sys/socket.h usability... yes
    checking sys/socket.h presence... yes
    checking for sys/socket.h... yes
    checking that linux/wireless.h is what we expect... no
    configure: error: *** Missing working Linux wireless kernel extensions ***
    how do I fix this

  2. #2
    Just burned his ISO
    Join Date
    Dec 2007
    Posts
    9

    Default

    I know i am "*** Missing working Linux wireless kernel extensions ***" , but I installed kernel.lzm, and I dont know what else to do

  3. #3
    Just burned his ISO
    Join Date
    Dec 2007
    Posts
    9

    Default

    or maybe something to do with iwconfig,ifconfig,wlanconfig ??????

  4. #4
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    3

    Default

    I got the same problem some minutes ago.

    Fix;

    go to 802.11ninja.net and download the trunk as zip.

    unzip it, chmod +x the configure file and run ./configure

    this should do it.

    after that;

    cp /usr/local/lib/liborcon-1.0.0.so /usr/lib

    thats it.

Posting Permissions

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