Author Topic: Wellenreiter 1.0.2.1 : No Wireless Extensions.  (Read 3271 times)

ElZauruso

  • Newbie
  • *
  • Posts: 6
    • View Profile
Wellenreiter 1.0.2.1 : No Wireless Extensions.
« on: November 22, 2004, 04:53:14 pm »
Hello,

I am trying get Wellenreiter II (1.0.2.1)  to work on my SL5500 with CackoROM.

And here I am now:

Wellenreiter starts (only from Console, not via the Icon... but thats another Problem)
and when trying to configure my WLAN-Card (ASUS-WL110 SpaceLink), I cannot choose my Interface ("Name") - For every Driver I try.

After searching around this and other Forums, I think, it has something to do with the Wireless Extensions (iwconfig). My device (eth0) is listed, but with "No wireless.... available".... which is not so fine ;-)

What Steps I have to do to get  wireless extensions?
After reading around for 2 Days I am really confused....

BTW: Kismet runs fine on the same SL5500...

Can anyone please point me to the right direction?

Thanx...

loji

  • Full Member
  • ***
  • Posts: 130
    • View Profile
    • http://
Wellenreiter 1.0.2.1 : No Wireless Extensions.
« Reply #1 on: December 04, 2004, 08:56:46 pm »
I have a linksys card on a 5600 and to get wellenreiter to reconize it I needed to use the hostap drivers.

Still doesn't actually sniff anythign :/  but it reocnizes the card : so it's a step in the right direction.

have you been here?
http://rcm.amazon.com/e/cm?t=zaurususergro...lt1=&bg1=&f=ifr
-> pdaXrom beta 3 fixes & feeds
C-1000 + pdaXrom beta3
linksys wifi + expansions

ElZauruso

  • Newbie
  • *
  • Posts: 6
    • View Profile
Wellenreiter 1.0.2.1 : No Wireless Extensions.
« Reply #2 on: December 06, 2004, 03:52:41 pm »
It works now....

The Problem was the Prism2-Drivers shipped and used by default for my Asus Spacelink WL-110.

From the wlan.conf-File (in /etc/pcmcia), I took the Paragraph

card "Asus...."
   version "ASUS......"
    bind "prism2_cs"

copied this and pasted it into the "spectrum.conf"
Now I changed the "prism2_cs" to "orinoco_cs"

then you have to move or delete the wlan.conf File
(I moved it for switching back to it later...)

then restarted the pcmcia-services...

Reset the Card, then resume it...

cardctl reset
cardctl scheme CardResume

...and that was it....

eth0 should be up now (ifconfig) and also should
give you wireless extensions (iwconfig)

Wellenreiter then uses eth0 with Orinoco-Drivers.

and ofcourse scans....

If you want back to wlan.conf, move that file again to etc/pcmcia
and restart pcmcia-services....

After this, eth0 should have no wireless extensions... and you are
using the standard drivers again....

Again my Configuration

SL5500 - Spacelink WL110 - CackoROM (64-0)

Sin

  • Newbie
  • *
  • Posts: 3
    • View Profile
Wellenreiter 1.0.2.1 : No Wireless Extensions.
« Reply #3 on: April 15, 2005, 06:50:22 pm »
Quote
It works now....

The Problem was the Prism2-Drivers shipped and used by default for my Asus Spacelink WL-110.

From the wlan.conf-File (in /etc/pcmcia), I took the Paragraph

card "Asus...."
   version "ASUS......"
    bind "prism2_cs"

copied this and pasted it into the "spectrum.conf"
Now I changed the "prism2_cs" to "orinoco_cs"

then you have to move or delete the wlan.conf File
(I moved it for switching back to it later...)

then restarted the pcmcia-services...

Reset the Card, then resume it...

cardctl reset
cardctl scheme CardResume

...and that was it....

eth0 should be up now (ifconfig) and also should
give you wireless extensions (iwconfig)

Wellenreiter then uses eth0 with Orinoco-Drivers.

and ofcourse scans....

If you want back to wlan.conf, move that file again to etc/pcmcia
and restart pcmcia-services....

After this, eth0 should have no wireless extensions... and you are
using the standard drivers again....

Again my Configuration

SL5500 - Spacelink WL110 - CackoROM (64-0)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=55353\"][{POST_SNAPBACK}][/a][/div]

Would this work with Linksys WCF12?

Sin

  • Newbie
  • *
  • Posts: 3
    • View Profile
Wellenreiter 1.0.2.1 : No Wireless Extensions.
« Reply #4 on: April 16, 2005, 02:00:58 am »
Yeah, I've been digging around all night can't get past this error.