OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Steve Stearns (sternobigbrother.net)
Date: Fri Feb 23 2001 - 00:56:19 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Okay, I've been bludgeoning my skull with the walls of my apartment for
    the past couple of days and I've made some progress but now I'm stumped.
    I've got an SMC2632W on my Laptop which is using RedHat 6.1 with a
    custome compiled kernel (2.4.1). I've finally got it so that it appears
    that the card is talking to my DLink but for some reason I cannot access
    the network.

    Now, to test that I was actually connecting to the access point, I tried
    blocking out my card's mac address using the settins on the access
    point. Sure enough, when I activate the blocking the light on the card
    started blinking and I got transmission errors. When I de-activated the
    blocking everything was back to normal with a steady light. So, my
    impression is that the card is talking to the base station.

    So, at this point it APPEARS that everything's talking but yet I cannot
    access the network for some reason.

    When I insert the card, here's what I see:

    Feb 23 00:42:52 localhost cardmgr[4061]: initializing socket 0
    Feb 23 00:42:52 localhost cardmgr[4061]: socket 0: Intersil PRISM2
    Reference Design 11Mb/s WLAN Card
    Feb 23 00:42:52 localhost cardmgr[4061]: executing: 'modprobe prism2_cs'
    Feb 23 00:42:52 localhost cardmgr[4061]: + modprobe: Can't locate module
    prism2_cs
    Feb 23 00:42:52 localhost cardmgr[4061]: modprobe exited with status 255
    Feb 23 00:42:52 localhost cardmgr[4061]: executing: 'insmod
    /lib/modules/2.4.1/pcmcia/prism2_cs.o'
    Feb 23 00:42:53 localhost kernel: init_module: prism2_cs.o: 0.1.7 Loaded
    Feb 23 00:42:53 localhost kernel: init_module: dev_info is: prism2_cs
    Feb 23 00:42:53 localhost kernel: prism2_cs: index 0x01: Vcc 5.0, irq 3,
    io 0x0140-0x017f
    Feb 23 00:42:53 localhost cardmgr[4061]: executing: './wlan-ng start wlan0'
    Feb 23 00:42:53 localhost kernel: ident: nic h/w: id=0x8002 1.0.0
    Feb 23 00:42:53 localhost kernel: ident: pri f/w: id=0x15 0.3.0
    Feb 23 00:42:53 localhost kernel: ident: sta f/w: id=0x1f 0.7.6
    Feb 23 00:42:53 localhost kernel:
    MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
    Feb 23 00:42:53 localhost kernel:
    CFI:SUP:role=0x00:id=0x02:var=0x01:b/t=1/1
    Feb 23 00:42:53 localhost kernel:
    PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/2
    Feb 23 00:42:53 localhost kernel:
    STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/4
    Feb 23 00:42:53 localhost kernel:
    PRI-CFI:ACT:role=0x01:id=0x02:var=0x01:b/t=1/1
    Feb 23 00:42:53 localhost kernel:
    STA-CFI:ACT:role=0x01:id=0x02:var=0x01:b/t=1/1
    Feb 23 00:42:53 localhost kernel:
    STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
    Feb 23 00:42:53 localhost kernel: Prism2 card SN: 39 39 53 41 30 31 30
    30 30 30 30 30
    Feb 23 00:42:53 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:53 localhost cardmgr[4061]: +
    mibattribute=dot11WEPDefaultKeyID=1Feb 23 00:42:53 localhost
    cardmgr[4061]: + resultcode=success
    Feb 23 00:42:53 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:53 localhost cardmgr[4061]: +
    mibattribute=dot11ExcludeUnencrypted=false
    Feb 23 00:42:53 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:53 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:53 localhost cardmgr[4061]: +
    mibattribute=dot11PrivacyInvoked=true
    Feb 23 00:42:53 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    mibattribute=dot11WEPDefaultKey0=e2:35:48:55:11
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    mibattribute=dot11WEPDefaultKey1=29:2b:b5:1b:cc
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    mibattribute=dot11WEPDefaultKey2=3d:cd:22:0b:c8
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    mibattribute=dot11WEPDefaultKey3=97:c7:4d:a6:50
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_mibset
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    mibattribute=dot11DesiredSSID=pinochio
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:54 localhost cardmgr[4061]: + message=dot11req_associate
    Feb 23 00:42:54 localhost cardmgr[4061]: + peerstaaddress=no_value
    Feb 23 00:42:54 localhost cardmgr[4061]: +
    associatefailuretimeout=no_value
    Feb 23 00:42:54 localhost cardmgr[4061]: + cfpollable=no_value
    Feb 23 00:42:54 localhost cardmgr[4061]: + cfpollreq=no_value
    Feb 23 00:42:54 localhost cardmgr[4061]: + privacy=no_value
    Feb 23 00:42:54 localhost cardmgr[4061]: + listeninterval=0
    Feb 23 00:42:54 localhost cardmgr[4061]: + resultcode=success
    Feb 23 00:42:55 localhost cardmgr[4061]: + usage: /sbin/ifport interface
    [auto|10baseT|10base2|aui|100baseT|##]

    Okay, so after getting that if I run ifconfig I see:

    wlan0 Link encap:Ethernet HWaddr 00:E0:29:9E:73:97
             inet addr:10.0.0.10 Bcast:10.0.0.255 Mask:255.255.255.0
             UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
             RX packets:61 errors:0 dropped:0 overruns:0 frame:0
             TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0

    Now, that's if I hard code the IP address. If I put in DHCP mode it
    will try to look up an IP but fail. Now, I checked the DLink and sure
    enough it is connecting to the network. My DHCP server is serving up an
    IP address to it and I can ping it without a problem (if it matters, in
    this case the DLink is running on IP 10.0.0.9).

    So, I'm stumped. Does anybody out there have suggestions as to what
    would cause this problem and how I might go about fixing it?

    Thanks!

    ---Steve

     <mailto:sternobigbrother.net>

    -----------------------------------------------
    The Linux WLAN User's Mailing List
    For more information about this list see:
    http://www.absoval.com/linux-wlan/lists.html