Hi,
I have the ndiswrapper working but I want to have all the abilities to capture wireless packets in monitor mode which doesn't work under the ndiswrapper. I have the
----------
lspci
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)
-----------
wireless card and I hear that the Lucent Orinoco and Prism II-based PCMCIA wireless chipset s work. I actually know they do because when I was using SuSE on my laptop it worked. I am running kernel 2.6.11-1.14_FC3. When I do a service pcmcia restart I get this response in the log

Apr 24 11:47:58 localhost kernel: cs: IO port probe 0xc00-0xcff: clean.
Apr 24 11:47:58 localhost kernel: cs: IO port probe 0x100-0x4ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38
Apr 24 11:47:58 localhost kernel: cs: IO port probe 0xa00-0xaff: clean.

root@localhost log]# service pcmcia status
cardmgr (pid 14208) is running...



The orinoco modules arent loaded, but I can do that, however I dont know how much it would do for me if I had the modules loaded without knowing the results from cardctl ident.

Also looking at this site
http://lisonbee.freeshell.org/linux/...ario_2100.html
Somebody with the same laptop and FC1 got it to work from the GUI but no Lucent Orinoco chipsets show up for me.

Before you do cardctl ident you must be sure you have inserted the card with cardctl, insert the card by doing "cardctl insert", the card should start to blink or so and then you can try to ident the card.

If this does not work you should recompile your kernel and make sure you compile it with wireless extensions. You should have wireless tools installed. Then you can do this:

That is what I get. I do not use ndiswrapper since when I last used it I could not get my card into monitor mode. I have also heard that there has been problems with the orinoco card, getting it into monitor mode. I am not sure about this though, since I have never used it by myself. But I have also heard that the orinoco card should be perfect for wardriving.

Regards

I am using Fedora Core 3 and am pretty sure I do have the wireless tools installed in the kernel since I have been using iwconfig for a while now. Is this what you where talking about when you said compile the kernel with wireless support? I will do a iwconfig -v and post it on here when I get home today.

Since this is a laptop with an integrated wireless card and not one that I put in the pcmcia slot, Do I still need to do a cardctl insert?

In fact after you posted a reply I realized that I use lspci to get info on the card.
Therefore it is not a pcmcia card, it is a pci card.
So cardctl doesnt help.
I will try a cardctl -v to see if I get the correct addresses I need to the config file when I get off of work.

Is this thought proccess correct? If I remember correctly there are some addresses that I need so that I can insert them into a config file that I edit when I modprobe orinoco. Hopefully lspci -v will give me those addresses.

Sorry I forgot to thank you for your response and I added this box not realizing that I could have just changed my last response.

Thanks a lot for your response I will post back here if I get my card to work or not.

You should have both wireless tools and wireless extensions. The latter goes into the kernel and the other one is what gives you commands like iwconfig.

I have a pcmcia card and here is my information from lspci:
When you modprobe orinoco check what dmesg tells you about it. Maybe you will find something usefull there. Check with ifconfig -a if your interface exists. Report back if it doesn't and also tell me the result of iwconfig -v

lspci -vv

00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device 00e7
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d0004000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
iwconfig -v
iwconfig Wireless-Tools version 27
Compatible with Wireless Extension v11 to v17.

Kernel Currently compiled with Wireless Extension v17.

wlan0 Recommend Wireless Extension v0 or later,
Currently compiled with Wireless Extension v17.

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0D:9D:81:FC:72
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:90:4B:47:93:0A
inet addr:138.236.231.149 Bcast:138.236.255.255 Mask:255.255.224.0
inet6 addr: fe80::290:4bff:fe47:930a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:151314 errors:0 dropped:0 overruns:0 frame:0
TX packets:5472 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37958704 (36.2 MiB) TX bytes:519501 (507.3 KiB)
Memory:d0004000-d0005fff


modprobe orinoco_cs orinoco hermes
# lsmod | grep orinoco
orinoco_cs 10057 0
orinoco 53837 1 orinoco_cs
hermes 8513 2 orinoco_cs,orinoco
pcmcia 26465 3 orinoco_cs
pcmcia_core 47993 4 orinoco_cs,pcmcia,yenta_socket,rsrc_nonstatic

#dmesg
orinoco 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
orinoco_cs: Unknown parameter `orinoco'
orinoco_cs 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)

Now what I need to do is make my hermes.conf file or so I think.
I was told it should look something like this from a website


device "orinoco_cs"
class "network"
module "hermes", "orinoco", "orinoco_cs"
# LinkSys WPC11
card "Instant Wireless Network PC Card"
manfid 0x0156,0x0002 #Substitute your addresses here
bind "orinoco_cs"

So what I thought I would get from cardctl was the manfid address, but I am not sure anymore.

It seems to me that you have an interface called wlan0, trie to search for APs by issueing iwlist wlan0 scan. If your card supports it this should give you a list of all APs around. Check out the man for iwconfig on how to connect your card to an AP. If you router uses dhcp then just do dhcpcd wlan0 and you should get an IP.

yes I do have an interface wlan0 that works just fine with the ndiswrapper but I am trying to use the actual drivers for the card which the hermes chipset orinoco prism II based drivers work for. The problem is that I cant find those drivers under fedoras's config program. So I am trying to do it manually. In order to do it manually I was reading that I neaded to modprobe orinoc_cs, orinoco, and hermes. This I beleive works but then I have to insert the hardware address or something into a file hermes,conf in order to get the dirvers installed. correctly.

This is what I think I should be doing and I don't know where to go from here.

Although I don't need a GUI what I want to do is see the hermes orinoc prism II based driver under the fedora/kde control panel which I can't see. Under Suse, these drivers where there by defualt and wireless worked without the ndiswrapper in which I don't want to use because I want to use wireless in managaed mode so that I an use some packet capturing tools which don't work under ndis.

Thanks.

I would really recommend you to go to some mailing list. You can check out if anyone else has had any problems, if you do not find anything useful then sign up and mail them your problem. Since those guys are dedicated to that specific driver and chipset they know how to help you through it.