Kismet (R.H 7.2 w/ Orinoco) - Compilation

Kismet (R.H 7.2 w/ Orinoco) - Compilation

Postby tomjones » Mon Aug 12, 2002 8:17 am

Hello,

With the help of numerous people I was able to get my Kismet setup to work. Thought I would post some of the conversations I had. I am fairly new to *nix so hopefully some of my basic questions will help others out. Thanks again to everyone who helped walk me through this process.

Great write up from alexm (tons of help)
http://www.cs.swt.edu/~am60347/rh72.html

Help from JimmyPopAli (monitor mode)
http://forums.netstumbler.com/showthread.php?s=&threadid=1831

Help from sauerc (Kismet)
http://forums.netstumbler.com/showthread.php?s=&threadid=3141


Emails with alexm:

> and can't find out what is wrong. I see at the bottom where there are
> cardmgr issues, but not sure what it means. lsmod comes up with no entries.

it means it did not link correctly...

> Also, in this step:
> # ln -s /lib/modules/2.4.18/pcmcia/hermes.o
> /lib/modules/2.4.18/kernel/drivers/net/wireless/hermes.o
> # ln -s /lib/modules/2.4.18/pcmcia/orinoco.o
> /lib/modules/2.4.18/kernel/drivers/net/wireless/orinoco.o
> # ln -s /lib/modules/2.4.18/pcmcia/orinoco.o
> /lib/modules/2.4.18/kernel/drivers/net/wireless/orinoco_cs.o
>
> I had to create the wireless folder under the net directory, there wasn't
> one there...did something not install correctly?

that is ok.

unresolved symbols errors mean that the module can not find function
addresses at expected locations.
this usually means that kernel and module versions do not match.

when you compile pcmcia-cs package provide it with the correct directory
for the kernel tree.
if you specify /usr/src/linux, then check if /usr/src/linux is really your
current kernel's tree (or a link to it) to avoid linking against a wrong
kernel.

check that, then make clean in your pcmcia-cs directory and redo make
config followed by make all and make install.

then in one terminal do "tail -f /var/log/message" and in another run:
service pcmcia stop
service pcmcia start

let me know if that worked. if not send me your config.mk from pcmcia-cs
directory.

-alexm

> i had to copy your orinoco.o, hermes.o, and orinoco_cs.o files. they were
> not placed anywhere through the install process.

did they insert correctly?

i suspect that in your config.mk DO_ORINOCO is set to 'n'.
if that is the case you are trying to use old drivers.
look at the timestamps on the files in /lib/modules/... dir and see if
they are "current".

let me know what heppens,

-alexm

ok, from your config.mk:
# Options from /usr/src/linux/.config
CONFIG_PCMCIA=y

your kernel is configured with pcmcia support.
in this case instead of "make config" in pcmcia-csxxxx run:
./Configure --force
this way the modules will still get compiled.
to be sure just cd pcmcia-csxxx/wireless and do a make all.
after that just copy hermes.o orinono.o orinoco_cs.o to /lib/modules/...
and restart pcmcia.
this should do it.

-alexm

> thanks for the help. i assume when you say kernel tree, you mean that the
> kernel folder is a subfolder of /usr/src/linux. for me, that is the case.
> it is a default install so it should be correct. under the kernel folder,
> there are no other folders, but numerous .o and .c files.
>
> "check that, then make clean in your pcmcia-cs directory and redo make
> config followed by make all and make install."
>
> after doing the make install, i got the following:
> depmod: *** Unresolved symbols in /lib/modules/2.4.18/pcmcia/hermes.o
> and two more of the same for orinoco.o and orinoco_cs.o.
>
> "then in one terminal do "tail -f /var/log/message" and in another run:
> service pcmcia stop
> service pcmcia start"
>
> tried anyway and got unresolved symbol errors.
>
>

ok, i do not know why it is necessary in this case but try this:
in you orinoco_cs.c file:
find and comment out the "return XXX" line in the 'if' statement where it
says:
if (serv.Revision != CS_RELEASE_CODE) {
printk(KERN_NOTICE "orinoco_cs: Card Services release "
"does not match!\n");
//return -EINVAL;
}

and of course recompile and try again.

-alexm

yes, that looks good.
you have the drivers working.
UNSPEC link means you have successfully entered the RF monitor mode.
you should see all the "raw" 802.11b frames now.
and yes, you need to "ifconfig eth1 promisc up" manually before sniffing.

if are you running kismet or airsnort they should work now.

good luck,

-alexm

> sorry to spam, but i think i have it...my eth1 looks similar to yours
>
> # ifconfig eth1
> eth1 Link encap:UNSPEC HWaddr
> 00-02-A5-2D-70-AD-00-00-00-00-00-00-00-00-00-00
> UP BROADCAST RUNNING 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:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:10 Base address:0x100
>
> UNSPEC is there and so is the long HWaddr. I also needed to bring up my
> eth1 manually.
tomjones
Mini Stumbler
 
Posts: 61
Joined: Fri May 10, 2002 9:05 am

Postby blackwave » Mon Aug 12, 2002 8:21 am

Thanks for the compiliation tomjones :)
-=BW=-
User avatar
blackwave
 
Posts: 4507
Joined: Mon Apr 15, 2002 3:00 am
Location: SoCal, OC


Return to Unix/Linux

Who is online

Users browsing this forum: No registered users and 4 guests

cron