少校
- 注册时间
- 2008-7-29
- 金币
- 623 个
- 威望
- 86 个
- 荣誉
- 25 个
尚未签到
|
9. GPS
' H* `0 J" J- Y% T3 ~* E% Y, Z! ^8 [! }' g
Kismet can integrate with a GPS device to provide coordinates for
' L, P! x) o% v/ J6 v* A networks it has detected. These can be logged to the pcap file when PPI
* q& V6 X5 [0 ^# z7 s' p( q# V logging is enabled, and to an XML file for processing with Kismap, included
5 a L4 S% s6 k) u( t& B with the Kismet source, as well as other third-party tools.
" | }3 }9 b, h8 W5 Z( v5 x6 ?
/ v' N$ J% H7 R" X Kismet can use the GPS network daemon 'gpsd', or can parse NMEA directly1 t2 P" W4 E9 s7 k: I7 X" G) w
from the GPS unit.
( n5 i5 W: B3 Q+ \6 f
w' w) y3 F1 v" z9 }" h) u* X The GPS is controlled with the Kismet server config, kismet.conf. For7 c& f L# D" r- R* V
using gpsd with gpsd running on the local system:8 b6 H3 `4 V- }
' ]7 f1 @) b; `9 [; I
gps=true3 v- s2 O# W4 F7 L0 y
gpstype=gpsd1 W5 {2 @4 {, ]! n, ^0 k/ Z
gpshost=localhost:29477 z6 d' b7 a$ @) Q4 D
gpsmodelock=false8 E8 p% N; M/ t! l
gpsreconnect=true
- v E* h+ t$ K a" G `5 n
" Z# ?" F. k) s* F% e By specifying gpsreconnect, if gpsd crashes or Kismet otherwises looses; {! y- R! d' ?9 x
its connection, it will be re-established. Gpsmodelock compensates for- N5 m$ D9 P5 U N9 G& L9 M
certain broken GPS/GPSd combinations, where the GPS never reports a/ O3 ]- e8 k& Q, b/ U5 y$ r: D
valid lock. By forcing a gpsmodelock=true, Kismet assumes the GPS
5 C/ }' k3 Y, o. @ always has a 2d lock.0 t( R" B- }5 t
# ?, ~% i4 l' M+ O! K9 c# A; l2 e
For using a GPS device without gpsd:
2 \$ C+ ]- i( L6 \1 ~& n2 h+ b: b% n. ~( [( T- T& Q0 }5 ^0 A4 o- ?
gps=true/ E; y- J. b' p c+ g3 A: G x5 h; Y
gpstype=serial
- Q. y5 O5 }- c! z gpsdevice=/dev/ttyS0
$ o% O7 N, {& t1 c" o( ~9 K gpsreconnect=true
6 q+ o) z- S, [- ?- ?0 G( y8 D' H9 L
6 V1 R @1 r$ M+ v m! M The gpsdevice parameter should be set to the proper serial device for4 H: }7 d" i* _! H
your GPS. For USB GPS devices this will typically be /dev/ttyUSB0, and
+ D6 j/ O- e/ m7 V" `6 W for bluetooth devices this will often by /dev/rfcomm0 or similar. Check
5 ~; ~. o7 c5 Q4 q5 G( k the output of "dmesg" after plugging in your device.
3 n1 {- r7 t& J/ V8 [' o' Y
+ {/ A% ]6 G3 O/ P y8 A1 k Kismet cannot know the location of a network, it can only know the
* q7 S1 ^: U/ d+ n, Y location where it saw a signal. By circling the suspected location,
4 W( _; k# @2 j- I you can provide more GPS data for processing the network center point.
V% \5 `) g1 K U/ D9 R+ d& k9 C: m( W% _4 K* Q8 \0 Z3 N
Kismet keeps running averages of the network location, however this is
3 @$ u+ M0 |2 N2 ~" M4 O0 \ not incredibly accurate, due to averaging and imprecision in
. H. H5 U: R. ^) a$ n- K, h/ t floating point math. For plotting network locations, the GPSXML file
# c. }- `! Y; Q should be used. |
|