Re: port kismet wont run as it should on openbsd current

2006-08-18 Thread Andreas Maus 

Hi.

Tested some wireless chipsets (ti,ra,ath0).
It seems that only ath doesn't show anything
in kismet (neither from ports nor from the latest
svn sources) - no powerlevel,no packets, no
packet rates.

Anyhow I would blame kismet,because
monitor mode can be set using ifconfig
ans I can see access points using
ifconfig -M.

So long,

Andreas.

P.S.: Is there a kismet mailinglist? I only found a forum
on there page.

--
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?

Re: port kismet wont run as it should on openbsd current

2006-08-18 Thread Matthias Kilian 
On Fri, Aug 18, 2006 at 09:04:40PM +0200, Andreas Maus wrote:
 P.S.: Is there a kismet mailinglist? I only found a forum
 on there page.

AFAIK there's only the web site.

For the ath problem, I'm sorry that I can't test or debug it, since
I don't have an ath, only wi and ral.

Ciao,
Kili

Re: port kismet wont run as it should on openbsd current

2006-08-18 Thread Jonathan Gray 
On Fri, Aug 18, 2006 at 09:46:10PM +0200, Matthias Kilian wrote:
 On Fri, Aug 18, 2006 at 09:04:40PM +0200, Andreas Maus wrote:
  P.S.: Is there a kismet mailinglist? I only found a forum
  on there page.
 
 AFAIK there's only the web site.
 
 For the ath problem, I'm sorry that I can't test or debug it, since
 I don't have an ath, only wi and ral.
 
 Ciao,
   Kili

The problem is probably that kismet does not read the
RSSI and MAX_RSSI radiotap portions.

Re: port kismet wont run as it should on openbsd current

2006-08-15 Thread Matthias Kilian 
On Sun, Aug 13, 2006 at 06:09:47PM +0300, Morganne witheredrose wrote:
 i am runnin openbsd-current and i ve installed kismet from the ports
 the only change i did in the kismet.conf is the 
 source=radiotap_bsd_b,ath0,scan

Did you try with other source types than radiotap_bsd_b?

 I run kismet, and it doesnt find any networks. It seems that it cant
 capture any packets.

Any error messages? What does ifconfig ath0 say, is the interface
in monitor mode?

 OpenBSD 4.0-beta (AWMN-CUSTOM) #0: Sun Aug 13 03:11:30 EEST 2006
^^^

And heere I stopped reading.

Ciao,
Kili

-- 
tabs are holier than spaces
-- Theo de Raadt

Re: port kismet wont run as it should on openbsd current

2006-08-15 Thread Andreas Maus 

On 8/15/06, Matthias Kilian [EMAIL PROTECTED] wrote:
Hi.


 source=radiotap_bsd_b,ath0,scan
Did you try with other source types than radiotap_bsd_b?

I never tried another source. I wasn't sure if a/g are working


Any error messages? What does ifconfig ath0 say, is the interface
in monitor mode?

If I remember correctly, yes.


And heere I stopped reading.

I confirm this behaviour with 3.8 and 3.9 (installed from CD)
But I blamed it to kismet, because ifconfig -M works as expected.

So long,

Andreas.

--
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?

Re: port kismet wont run as it should on openbsd current

2006-08-15 Thread Maxim Bourmistrov 
Works fine here on 4.0-beta with
source=radiotap_bsd_ab,rum0,radiotap_bsd_ab
So it's probably not a kismet-pkg err.

 
On Tuesday 15 August 2006 22:29, Matthias Kilian wrote:
 On Sun, Aug 13, 2006 at 06:09:47PM +0300, Morganne witheredrose wrote:
  i am runnin openbsd-current and i ve installed kismet from the ports
  the only change i did in the kismet.conf is the 
  source=radiotap_bsd_b,ath0,scan
 
 Did you try with other source types than radiotap_bsd_b?
 
  I run kismet, and it doesnt find any networks. It seems that it cant
  capture any packets.
 
 Any error messages? What does ifconfig ath0 say, is the interface
 in monitor mode?
 
  OpenBSD 4.0-beta (AWMN-CUSTOM) #0: Sun Aug 13 03:11:30 EEST 2006
   ^^^
 
 And heere I stopped reading.
 
 Ciao,
   Kili

Re: port kismet wont run as it should on openbsd current

2006-08-15 Thread pedro la peu 
 Did you try with other source types than radiotap_bsd_b?

This will only change the channels used. Kismet has one generic capture 
source and one for wi(4).

port kismet wont run as it should on openbsd current

2006-08-13 Thread Morganne witheredrose 

i am runnin openbsd-current and i ve installed kismet from the ports
the only change i did in the kismet.conf is the source=radiotap_bsd_b,ath0,scan

I run kismet, and it doesnt find any networks. It seems that it cant
capture any packets.
In paraller i run tcpdump -i ath0 -y IEEE802_11_RADIO and still no
captures via tcpdump

If i run ifconfig -M ath0 , ifconfig finds networks and tcpdump also
reports the packets.
i also downloaded the latest stable-devel svn of kismet wireless and
still the same thing. No networks.

Do you have any idea why is that happening ?

(By the way i only want kismet just to show the rssi and noise level
in dbm because ifconfig wont show such details.

Thank you in advance.

Bellow there is a dmesg of my system

OpenBSD 4.0-beta (AWMN-CUSTOM) #0: Sun Aug 13 03:11:30 EEST 2006
   [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/AWMN-CUSTOM
cpu0: Intel Pentium III (GenuineIntel 686-class) 932 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
real mem  = 402157568 (392732K)
avail mem = 358367232 (349968K)
using 4256 buffers containing 20209664 bytes (19736K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(f9) BIOS, date 01/06/01, BIOS32 rev. 0 @
0xfb190, SMBIOS rev. 2.2 @ 0xf0800 (43 entries)
bios0: VIA Technologies, Inc. VT82C694X
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0xdbb4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdb20/144 (7 entries)
pcibios0: PCI Exclusive IRQs: 10 11 12
pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 VIA VT82C691 PCI rev 0xc4
ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40
pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100,
channel 0 configured to compatibility, channel 1 configured to comp
atibility
wd0 at pciide0 channel 0 drive 0: QUANTUM FIREBALLlct08 13
wd0: 16-sector PIO, LBA, 12416MB, 25429824 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x16: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x16: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40
auvia0 at pci0 dev 7 function 5 VIA VT82C686 AC97 rev 0x50: irq 12
ac97: codec id 0x49434511 (ICEnsemble ICE1232)
ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D
audio at auvia0 not configured
vga1 at pci0 dev 9 function 0 Matrox MGA 1064SG 220MHz rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
dc0 at pci0 dev 12 function 0 3Com 3cSOHO 100B-TX rev 0x31: irq 10,
address 00:04:75:b4:fa:9e
ukphy0 at dc0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI
0x000749, model 0x0001
ath0 at pci0 dev 13 function 0 Atheros AR5212 rev 0x01: irq 11
ath0: AR5213 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, FCC2A*, address
00:0b:85:03:05:70
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask e765 netmask ef65 ttymask efe7
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
Kernelized RAIDframe activated
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302