少校
- 注册时间
- 2008-7-29
- 金币
- 623 个
- 威望
- 86 个
- 荣誉
- 25 个
尚未签到
|
9. GPS
/ w/ r t; H- Z8 d
7 Q/ b) s1 J/ e3 t, s0 x% ]# X Kismet can integrate with a GPS device to provide coordinates for8 x: T2 S& f" B; a: {% G. z/ t$ L
networks it has detected. These can be logged to the pcap file when PPI: [5 ^+ ^4 U2 z/ D" C6 `7 E
logging is enabled, and to an XML file for processing with Kismap, included
F7 o2 a. G8 _ } with the Kismet source, as well as other third-party tools.% [# W! m) z8 |) H. [
! `( W" V+ h1 O' S8 V
Kismet can use the GPS network daemon 'gpsd', or can parse NMEA directly, u q* E" Y7 t
from the GPS unit.( k4 \5 g; U! q" `1 o4 X
( o p+ |" W0 C d- W- O* y The GPS is controlled with the Kismet server config, kismet.conf. For
1 I/ x# ?' Q; H' J using gpsd with gpsd running on the local system: L1 E3 t7 j8 j J, B
, `0 A/ m- s, }9 ?" k
gps=true
( m: c: R3 @$ Y' q% l _ gpstype=gpsd" u! ?( y, {! \5 T+ q4 @( S0 f% B! Y
gpshost=localhost:2947
2 ?$ Z. ^3 m5 d" b gpsmodelock=false
- j9 ]& p" A! G0 C7 j, P9 j, e3 e gpsreconnect=true1 g' V4 n+ c1 M' r& _
0 s$ N5 I3 _% J+ ?+ n! n/ C9 z By specifying gpsreconnect, if gpsd crashes or Kismet otherwises looses$ ?9 C9 w( g& h& f' @
its connection, it will be re-established. Gpsmodelock compensates for7 L) F3 r/ K+ I8 \* o$ v$ v* G
certain broken GPS/GPSd combinations, where the GPS never reports a i9 T7 B9 K* ~6 ]+ r6 R; v# o
valid lock. By forcing a gpsmodelock=true, Kismet assumes the GPS! w+ S/ C' b8 O2 n8 z' w
always has a 2d lock.
" w8 a' I, V( t
# n2 @- Z! r4 _5 h8 U% p/ K For using a GPS device without gpsd:
4 ?) E6 H6 |) _. `* i+ X
. s* O* {5 j) R* Q1 A5 d T9 b$ e2 _ gps=true
( A2 k! _- J* t& M gpstype=serial! }' _# D# w+ `
gpsdevice=/dev/ttyS0
7 L1 T& ?/ w: F gpsreconnect=true
7 \1 t% A- f3 c( I" a4 Q+ A3 N
' Y& a" E9 @6 Q. E9 L% o The gpsdevice parameter should be set to the proper serial device for8 R' y% ?/ B- o- }3 ~. ]# _% A4 v
your GPS. For USB GPS devices this will typically be /dev/ttyUSB0, and
( P8 G% j2 H0 t7 d& ~ for bluetooth devices this will often by /dev/rfcomm0 or similar. Check
# y2 e8 ?" R8 N+ |/ U' h the output of "dmesg" after plugging in your device./ [" O+ I8 T6 @. z& S8 v9 @* L: r& P" q
4 w7 D% H; g4 a* k; ?& n
Kismet cannot know the location of a network, it can only know the
7 ^# Y& ]! ]2 ?$ U9 I location where it saw a signal. By circling the suspected location,
, j# ^5 K F+ Y" }) A( c; f you can provide more GPS data for processing the network center point.
3 Z1 u% P: K- Z. Z3 F4 A% D2 f I m5 p1 M V) G
Kismet keeps running averages of the network location, however this is
( X- z% N X3 i5 K9 |% w6 G! l not incredibly accurate, due to averaging and imprecision in
}% N6 t" J7 i3 G floating point math. For plotting network locations, the GPSXML file! P2 }. g2 m" f% h( o
should be used. |
|