Results 1 to 6 of 6

Thread: Alfa - Mac80211 to IEEE80211: problems

  1. #1
    Junior Member
    Join Date
    Jan 2010
    Posts
    81

    Default Alfa - Mac80211 to IEEE80211: problems

    Quote Originally Posted by #mfBaranian#
    The ieee80211 (r8187) driver is available in the repo's (for BT4PF) and you can get it through apt-get (apt-get install r8187-drivers)
    1. I tried getting the drivers through the repo's but was unsuccessful.
    2. Used the tutorial from aircrack
    Code:
    http://aircrack-ng.org/doku.php?id=r8187
    But, yet again no luck.

    3. Last, I went to the ubuntu forums to see what they thought:
    Code:
    http://ubuntuforums.org/showthread.php?t=945814
    and followed a modified tutorial:
    Quote Originally Posted by rattking
    ifconfig wlan0 down
    rmmod r8187 rtl8187 2>/dev/null
    wget http://dl.aircrack-ng.org/drivers/rt...ux_26.1010.zip
    unzip rtl8187_linux_26.1010.zip
    cd rtl8187_linux_26.1010.0622.2006/
    wget http://patches.aircrack-ng.org/rtl8187_2.6.27.patch
    tar xzf drv.tar.gz
    tar xzf stack.tar.gz
    patch -Np1 -i rtl8187_2.6.27.patch

    then I had to edit the file
    beta-8187/r8187.h
    and change
    #include <asm/semaphore.h>
    to
    #include <linux/semaphore.h>

    make
    make install
    Again no success.

    When make'ing either tutorial i got errors that may lead to a solution:
    Code:
    root@laptop:~/rtl8187_linux_26.1010.0622.2006# make
    rm -f ieee80211/Module.symvers 2>/dev/null
    rm -f ieee80211/Modules.symvers 2>/dev/null
    make -C ieee80211 all
    make[1]: Entering directory `/root/rtl8187_linux_26.1010.0622.2006/ieee80211'
    make -C /lib/modules/2.6.29.4/build M=/root/rtl8187_linux_26.1010.0622.2006/ieee80211 modules
    make[2]: Entering directory `/usr/src/linux-source-2.6.29.4'
    
      WARNING: Symbol version dump /usr/src/linux-source-2.6.29.4/Module.symvers
               is missing; modules will have no dependencies and modversions.
    
      CC [M]  /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_softmac.o
    In file included from /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_softmac.c:17:
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h: In function 'ieee80211_priv_rtl7':
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h:1181: warning: 'netdev_priv' is static but used in inline function 'ieee80211_priv_rtl7' which is not static
      CC [M]  /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_rx.o
    In file included from /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_rx.c:52:
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h: In function 'ieee80211_priv_rtl7':
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h:1181: warning: 'netdev_priv' is static but used in inline function 'ieee80211_priv_rtl7' which is not static
      CC [M]  /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_tx.o
    In file included from /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_tx.c:60:
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h: In function 'ieee80211_priv_rtl7':
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h:1181: warning: 'netdev_priv' is static but used in inline function 'ieee80211_priv_rtl7' which is not static
      CC [M]  /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.o
    In file included from /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:37:
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h: In function 'ieee80211_priv_rtl7':
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211.h:1181: warning: 'netdev_priv' is static but used in inline function 'ieee80211_priv_rtl7' which is not static
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c: In function 'ipw2100_translate_scan_rtl7':
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:57: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:57: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:57: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:57: error: too few arguments to function 'iwe_stream_add_event'
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:66: warning: passing argument 1 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:66: warning: passing argument 3 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:66: warning: passing argument 4 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:66: error: too few arguments to function 'iwe_stream_add_point'
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:69: warning: passing argument 1 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:69: warning: passing argument 3 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:69: warning: passing argument 4 of 'iwe_stream_add_point' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:69: error: too few arguments to function 'iwe_stream_add_point'
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:75: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:75: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:75: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:75: error: too few arguments to function 'iwe_stream_add_event'
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:87: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:87: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:87: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:87: error: too few arguments to function 'iwe_stream_add_event'
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:97: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:97: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
    /root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.c:97: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
    make[3]: *** [/root/rtl8187_linux_26.1010.0622.2006/ieee80211/ieee80211_wx.o] Error 1
    make[2]: *** [_module_/root/rtl8187_linux_26.1010.0622.2006/ieee80211] Error 2
    make[2]: Leaving directory `/usr/src/linux-source-2.6.29.4'
    make[1]: *** [modules] Error 2
    make[1]: Leaving directory `/root/rtl8187_linux_26.1010.0622.2006/ieee80211'
    make: *** [all] Error 2
    make install:
    Code:
    root@laptop:~/rtl8187_linux_26.1010.0622.2006# make install
    install -d /lib/modules/2.6.29.4/kernel/drivers/net/wireless/rtl_ieee80211
    install -d /lib/modules/2.6.29.4/kernel/drivers/net/wireless/rtl8187
    install -m 644 ./ieee80211/*.ko /lib/modules/2.6.29.4/kernel/drivers/net/wireless/rtl_ieee80211
    install: cannot stat `./ieee80211/*.ko': No such file or directory
    make: *** [install] Error 1
    Any suggestions will be greatly appreciated.

    Thanks,
    red

  2. #2
    Senior Member
    Join Date
    Aug 2007
    Posts
    916

    Default

    Exactly why were you unsuccessful using the drivers from the repository? You do not need to manually compile and install r8187 driver by hand as it is not the easiest thing for beginners. I have written up a guide on my blog which sort of used to work prior to me contacting muts in regards to having the driver to be packaged and placed into the repository.

    First things first, once you have installed r8187-drivers, you need to unplug the device (after ifconfig it down of course), blacklist rtl8187 and then make sure there's no traces of rtl8187 and its deps are in the lsmod (provided that you have only one wireless device) and then you plug the device back in.

    My personal blog is here but I highly recommend you to not follow the guide on my blog as it is not easy for beginners.

  3. #3
    Junior Member
    Join Date
    Jan 2010
    Posts
    81

    Default

    Quote Originally Posted by hatake_kakashi View Post
    Exactly why were you unsuccessful using the drivers from the repository? You do not need to manually compile and install r8187 driver by hand as it is not the easiest thing for beginners. I have written up a guide on my blog which sort of used to work prior to me contacting muts in regards to having the driver to be packaged and placed into the repository.

    First things first, once you have installed r8187-drivers, you need to unplug the device (after ifconfig it down of course), blacklist rtl8187 and then make sure there's no traces of rtl8187 and its deps are in the lsmod (provided that you have only one wireless device) and then you plug the device back in.

    My personal blog is here but I highly recommend you to not follow the guide on my blog as it is not easy for beginners.
    Because when I use the command given, it does not work. I have gone through synaptic as well but have found nothing. I will look at your blog.

    Thanks,
    red

    Edit:
    A tutorial is a tutorial, if all commands are listed correctly, anyone can follow. Yours is very similar to the post on aircrack making it a piece of cake. Thank you for giving me the link and making the tutorial. I will report if there are any errors.

    Edit2:
    Worked beautifully, thank you very much. I also bookmarked your blog. =) Last but not least, when I use airmon-ng, it does not create vap's like the previous driver did, such as mon0, mon1, and etc. Now, it goes into monitoring mode, but does not create them.

  4. #4
    Member
    Join Date
    Jan 2010
    Posts
    332

    Default

    Well I can see that you have done it already. I think that you just needed to apt-get update and then it would work. But hey, you can try it again since the new kernel is out .....
    Last but not least, when I use airmon-ng, it does not create vap's like the previous driver did, such as mon0, mon1, and etc. Now, it goes into monitoring mode, but does not create them.
    Yes, that's one of the main differences between the mac and ieee drivers.
    SecurityTube has two new sections. Questions & News

  5. #5
    Senior Member
    Join Date
    Aug 2007
    Posts
    916

    Default

    Quote Originally Posted by #mfBaranian# View Post
    Quote Originally Posted by redhotfire
    Last but not least, when I use airmon-ng, it does not create vap's like the previous driver did, such as mon0, mon1, and etc. Now, it goes into monitoring mode, but does not create them.
    Yes, that's one of the main differences between the mac and ieee drivers.
    That's not the main difference between mac80211 and ieee80211 drivers, that's just an extra interface created specifically for monitoring and what not. It is not a mandatory option to use airmon-ng as I believe it can confuse the living hell out of most people. I still would recommend the usage of iwconfig <dev> mode monitor

    Moreover, the real difference between mac80211 and ieee80211 drivers are the lack of needing to use extra tools. Users of atheros, aironet, prism2_usb would know what I mean.

    VAP was an unique thing for atheros owners (using madwifi-ng) but at the same time it confused many people, such as the fact you cannot simply do iwconfig ath0 mode monitor, you need to destroy the VAP (well preferrably) and create a new one specifically for monitoring. That wasn't a real drawback considering it was in theory possible to setup an AP and monitor on the same channel.

  6. #6
    Member
    Join Date
    Jan 2010
    Posts
    332

    Default

    I stand corrected.
    Although I was thinking of differences in terms of usage.
    SecurityTube has two new sections. Questions & News

Posting Permissions

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