Jump to content

epretorious

Members
  • Posts

    115
  • Joined

  • Last visited

Posts posted by epretorious

  1. 1. airfart has to be started using the 'run' action (of the Start Menu) - There is no icon for airfart in the Start Menu.

    2. Once started it does nothing - even after setting the only configurable setting: the device.

    I stand corrected: There is an item in the Internet -> Other sub-menu. However, it does not function correctly. :wall:

     

    The command associated with the Internet -> Other -> airfart menu-item (`gksu airfart`) bombs when executed from the Konsole (as a non-root user):

    [eric@zippy doc]$ gksu airfart
    Starting Airfart...
    Launching sniffer thread...
    start_sniffing_thread() Called!
    Sniffing thread spawned successfully!
    sh: line 1: wlanctl-ng: command not found
    Could not put the card in monitor mode!
     The device is not present or 'wlanctl-ng' is not in your path or the device refused.
    sniffing loop bombed out!

    The only time that airfart runs correctly is when it's started as root (from the Konsole). That's because wlanctl-ng is in /sbin/wlanctl-ng and /sbin is in root's path. Ergo, gksu isn't updating $HOME. :wall:

  2. AFter removing orinoco_cs from /etc/modprobe.preload in adding prism2_cs instead, Airfart has begun working. (Airfart installs the wlan-ng package which includes the prism2 wireless kernel modules.)

     

    Though it does begin detecting networks airfart complains in the konsole window from which I started it:

    [root@zippy root]# airfart
    Starting Airfart...
    Launching sniffer thread...
    start_sniffing_thread() Called!
    Sniffing thread spawned successfully!
    message=lnxreq_wlansniff
     enable=true
     channel=6
     prismheader=no_value
     wlanheader=true
     keepwepflags=no_value
     stripfcs=no_value
     packet_trunc=no_value
     resultcode=success
    Warning: Dropped a frame.
     Frame Contents:
    ff ff ff ff ff ff aa aa  03 00 00 00 08 00 45 00   ÿÿÿÿÿÿªª ......E.
    00 8c 00 28 40 00 40 11  b7 83 c0 a8 00 66 c0 a8   ...(@.@. ·.À¨.fÀ¨
    00 ff 02 77 02 77 00 78  2c 03 33 30 35 36 20 33   .ÿ.w.w.x ,.3056 3
    20 69 70 70 3a 2f 2f 31  39 32 2e 31 36 38 2e 30    ipp://1 92.168.0
    2e 31 30 32 2f 70 72 69  6e 74 65 72 73 2f 46 72   .102/pri nters/Fr
    65 6d 6f 6e 74 5f 4e 4f  43 20 22 46 72 65 6d 6f   emont_NO C "Fremo
    6e 74 5f 4e 4f 43 22 20  22 48 50 20 4c 61 73 65   nt_NOC"  "HP Lase
    72 4a 65 74 20 34 30 35  30 22 20 22 48 50 20 4c   rJet 405 0" "HP L
    61 73 65 72 4a 65 74 20  53 65 72 69 65 73 20 43   aserJet  Series C
    55 50 53 20 76 31 2e 31  22 0a                     UPS v1.1 ".

    Airfart complains about the same dropped frame over and over. (The frame appears to be some sort of beacon sent from my laptop to the printer in my office.) Any ideas what's causing this? :unsure:

  3. Hello, All:

     

    I've just installed airfart (airfart-0.2.1-2mdk) and discovered that - along with most of Mandrake 10.0's wireless networking tools - it doesn't work. (Read about my other experiences with M10's wireless tools.) :wall:

     

    1. airfart has to be started using the 'run' action (of the Start Menu) - There is no icon for airfart in the Start Menu.

    2. Once started it does nothing - even after setting the only configurable setting: the device.

     

    Any ideas?

  4. I haven't made any progress finding a solution to this but I have noticed that sometimes there's just a lag between issuing the command and the card associating with the AP. But then again, sometimes it just bombs. :wall:

     

    Any ideas?

  5. Well, after reading a bit more, I learned how to test the orinoco_cs module to see if monitor mode is available:

    [root@zippy root]# iwpriv eth0
    eth0      Available private ioctl :
             force_reset      (8BE0) : set   0       & get   0
             card_reset       (8BE1) : set   0       & get   0
             set_port3        (8BE2) : set   1 int   & get   0
             get_port3        (8BE3) : set   0       & get   1 int
             set_preamble     (8BE4) : set   1 int   & get   0
             get_preamble     (8BE5) : set   0       & get   1 int
             set_ibssport     (8BE6) : set   1 int   & get   0
             get_ibssport     (8BE7) : set   0       & get   1 int
             dump_recs        (8BFF) : set   0       & get   0

    So the short answer is that Mandrake's installation of orinoco_cs does not support monitor mode. :wall:

  6. Hello, All:

     

    I've configured kismet (kismet-3.1.020401-2mdk) but when I attempt to use kismet (with either my Wavelan/IEEE card or my Prism2 card*) it complains and then dies...

     

    [root@zippy root]# kismet
    Server options:  none
    Client options:  none
    Starting server...
    Will drop privs to eric (500) gid 500
    No specific sources given to be enabled, all will be enabled.
    Enabling channel hopping.
    Enabling channel splitting.
    Source 0 (orinocosource): Enabling monitor mode for orinoco source interface eth1 channel 6...
    Waiting for server to start before startuing UI...
    FATAL: Could not find 'monitor' private ioctl.  This typically means that the drivers have not been patched or the patched drivers are being loaded.  See the troubleshooting section of the README for more information.

    * Kismet works with both of these cards in Gentoo

     

    The kismet README (/usr/share/doc/kismet-3.1.020401/README) addresses this...

    PROBLEM: Fatal error enabling monitor mode, 'monitor' ioctl not available

          Some capture sources use a private ioctl, 'monitor', to enable rfmon.

          If Kismet is unable to find this ioctl, it means that the wrong

          interface was specified, the wrong capture type is being used, or

          most commonly, the drivers you are using have not been patched or the

          patched drivers are not being loaded.

          Be sure to download any patches needed for the drivers you are using,

          and make sure that no other copies of those drivers exist in your

          /lib/modules/kern-version/ directory.  You may need to restart pcmcia-cs

          if your wireless card was already running when you installed the patched

          drivers.

    FIX: Provide the correct interface and ensure that the patched drivers are

          loaded.

    So I verified that the interface is specified correctly in /etc/kismet.conf...
    source=orinoco,eth1,orinocosource

    and verified that the card is bound to eth1...

     

    [root@zippy root]# iwconfig eth1
    eth1      IEEE 802.11-DS  ESSID:"linksys"  Nickname:"HERMES I"
             Mode:Managed  Frequency:2.437GHz  Access Point: 00:0C:41:18:4D:FA
             Bit Rate:5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
             Retry limit:4   RTS thr:off   Fragment thr:off
             Encryption key:off
             Power Management:off
             Link Quality:21/92  Signal level:-75 dBm  Noise level:-95 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
             Tx excessive retries:5  Invalid misc:0   Missed beacon:0

    orinoco_cs is loaded along with all the others...

     

    ds                     15364  6 pcnet_cs,orinoco_cs
    orinoco                39532  1 orinoco_cs
    hermes                  8736  2 orinoco_cs,orinoco
    yenta_socket           16352  2
    pcmcia_core            68768  4 pcnet_cs,orinoco_cs,ds,yenta_socket

    But there's still no love goin' on so that means that "the drivers [i am] using have not been patched." How can I narrow this down to the specific driver that needs to be patched?

  7. Hello, All:

     

    I'm attempting to configure my wireless interface using iwconfig (wireless-tools-26-3mdk) and am not able to modify any settings using any of my cards. (Orinoco Classic Gold, Netgear MA401, or D-Link DWL-650 verion 1.02 -The first is a Wavelan/IEEE card and the other two are Prism2 cards.)

     

    pcmcia-cs/orinoco_cs (pcmcia-cs-3.2.5-3mdk) automatically connects to the strongest open AP and configures my wireless cards without flaw:

     

    [eric@zippy eric]$ sudo /sbin/iwconfig eth0
    eth0      IEEE 802.11-DS  ESSID:"wireless"  Nickname:"zippy"
             Mode:Managed  Frequency:2.437GHz  Access Point: 00:06:F4:04:DB:91
             Bit Rate:5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
             Retry limit:4   RTS thr:off   Fragment thr:off
             Encryption key:off
             Power Management:off
             Link Quality:28/92  Signal level:-70 dBm  Noise level:-98 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:6
             Tx excessive retries:22  Invalid misc:0   Missed beacon:0

    However, when I attempt to manually associate with a different AP...

     

    [eric@zippy eric]$ sudo /sbin/iwconfig eth0 essid 'linksys'
    [eric@zippy eric]$ sudo /sbin/iwconfig eth0
    eth0      IEEE 802.11-DS  ESSID:"linksys"  Nickname:"zippy"
             Mode:Managed  Frequency:2.437GHz  Access Point: 00:06:F4:04:DB:91
             Bit Rate:5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
             Retry limit:4   RTS thr:off   Fragment thr:off
             Encryption key:off
             Power Management:off
             Link Quality:29/92  Signal level:-70 dBm  Noise level:-99 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:6
             Tx excessive retries:22  Invalid misc:0   Missed beacon:0

    ...the operation fails. (Notice that the AP's MAC address has NOT changed.)

     

    Or if I try to change the channel...

     

    [eric@zippy eric]$ sudo /sbin/iwconfig eth0 channel 10
    Error for wireless request "Set Frequency" (8B04) :
       SET failed on device eth0; Operation not supported.
    [eric@zippy eric]$ sudo /sbin/iwconfig eth0
    eth0      IEEE 802.11-DS  ESSID:"linksys"  Nickname:"zippy"
             Mode:Managed  Frequency:2.437GHz  Access Point: 00:06:F4:04:DB:91
             Bit Rate:5.5Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
             Retry limit:4   RTS thr:off   Fragment thr:off
             Encryption key:off
             Power Management:off
             Link Quality:35/92  Signal level:-63 dBm  Noise level:-99 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:85
             Tx excessive retries:143  Invalid misc:0   Missed beacon:0

    ...the operation fails. (Notice that the frequency has NOT changed.)

     

    Any ideas what's causing this? I believe that the orinoco_cs driver is supposed to provide complete supoprt for the Wavelan/IEEE chipset and nearly-complete support for the Prism2 chipset.

  8. Hello, All:

     

    When I execute apradar (apradar-0.50-1mdk) with my Orinoco Classic Gold (Wavelan/IEEE) or my Netgear MA401 (Prism2)...

     

    [root@zippy root]# apradar

    apradar dumps a core and complains...

     

    AP Radar 0.5
    Resource directory is set to /usr/share/apradar
    Loading options from /root/.apradar/options
    Aborted (core dumped)
    [root@zippy root]# Mutex destroy failure: Device or resource busy
    ICE default IO error handler doing an exit(), pid = 4509, errno = 2

    Any ideas what might be causing this?

  9. Hello, All:

     

    I've been using my wireless PCMCIA cards (Orinoco Gold Classic, Netgear MA401, & D-Link DWL-650 version 1.02) under Mandrake 10.0 for a while now. The cards automatically connect to the strongest open AP and negotiate a connection without any interaction on my part. :D

     

    I'd like to begin using WPA, however, to encrypt my data. Is there a WPA supplicat for Mandrake 10 yet?

  10. Hello, All:

     

    I've been really impressed with MandrakeLinux's wireless implimentation: I insert my D-Link DWL-650 (version 1.02) into the PCMCIA slot and it automatically connects to my AP (i.e., the AP with the strongest signal) and configures networking. :P

     

    However, there are times when I don't want to automatically connect to the strongest AP by default but would rather use another weaker AP - My neighbor's AP, for example - but when I used iwconfig to connect to the AP, iwconfig complains...

    [root@zippy root]# iwconfig eth0 ap 00:OF:66:00:CC:69
    Invalid hardware address 00:OF:66:00:CC:69
    Error for wireless request "Set AP Address" (8B14) :
       invalid argument "00:OF:66:00:CC:69".

    Because my neighbors and I all have Linksys AP's and none of us has changed the BSSID of the AP, our AP's are all identified as 'linksys' so using `iwconfig eth0 essid "MyAP"` isn't an option. (I'm sure that the MAC address is correct - I captured it using kismet.)

     

    What's wrong with iwconfig?

  11. The root-cause of this problem appears to be operator error: I completely forgot that tar'ing my old directory (in order to copy it to the new machine) will omit hidden directories. e.g., ~/.kde.

     

    Once I realized this, I was able to complete the migration by creating an invoice file for tar...

    .kde/share/apps/korganizer
    .kde/share/apps/kabc
    .kde/share/apps/konqueror

    ...and then moving the .tar file to the new workstation and un-tar'ing them.

     

    Caveat: One minor modification was required: I had to rename ~/.kde/share/apps/korganizer/eric.ics -> std.ics. in order for korganizer to load my old calendar.

  12. Hello, All:

     

    I am in the process of upgrading from Mandrake 9.1 / KDE 3.1 to Mandrake 10.0 / KDE 3.2 and have run into a few snags:

    • Kontact won't read my KAddressManager contact information..
    • Kontact won't read my KOrganizer calendar/todo list.
    • Kontact won't read my Konqueror bookmarks.

    KMail is able to read my old .Mail direcotory, though (i.e., folders and messages). :blink:

     

    Is there some sort of upgrade scripts that I need to run these files through in order to upgrade/import them into Kontact?

  13. The board is now running an RC version which is stable. As for the "view my posts" link, that was a hack i added on myself. If i get time i will put it back on this version. In the meantime a click on your name will bring up your profile and from that page you can view all the posts you ever made.
    Cool - Thanks! :o
    Search feature? what can't you find?
    e.g., Searching for the phrase "5 button mouse", "5 mouse button", and "memorex" all failed to find this post. The search feature may work but it's horrendously inflexible. icon8.gif
×
×
  • Create New...