• 0 voto(s) - 0 Media
  • 1
  • 2
  • 3
  • 4
  • 5

gps kismet malas coordenadas bu353usb

gps bu353usb+kismet malas coordenadas
Hola chicos haber si hay alguien que le sucedió lo mismo con este gps y puede echar una mano,deciros que vengo dando vueltas,foro de usglobalsat etc etc..., con el tema desde hace ya tiempo pero no he dado con la solución,vamos al tema:

Bajo winxp utilizando gpsinfo y sirfdemo la salida NMEA da las coordenadas correctas:

SiRFDemo Version 3.87 log file opened 11/11/11 21:41:59
SiRFDemo Build Date: June 20, 2007BAUD RATE: 9600

status: 3D
hdop: 1.1
PDOP: 1.9

Tx PC Time=1321044119.000
Tx: 0xA0A2000284000084B0B3
Tx PC Time=1321044119.000
Tx: 0xA0A2000298000098B0B3
Tx PC Time=1321044151.000
Tx: 0xA0A20018810201010001010105010101000100010001000100012580013AB0B3

bajo linux,utilizando kismet en bactrack5,linuxmint,cgps etc etc...

lat 40 21

long 5 084

la salida NMEA correcta pero en cuanto corres cualquier aplicación de las mencionadas anteriormente aparecen los datos erroneos(comprobados con gps de mano).

en el map view de sirfdemo idem de lo mismo.

en linux:

gpsctl -f -n -s 9600 /dev/ttyUSB0

la salida nmea correcta,abres kismet,cgps,etc... y vuelven aparecer los datos erroneos.

# Kismet config file
# Most of the "static" configs have been moved to here -- the command line
# config was getting way too crowded and cryptic. We want functionality,
# not continually reading --help!

# Version of Kismet config

# Name of server (Purely for organizational purposes)

# Prefix of where we log (as used in the logtemplate later)
# logprefix=/some/path/to/logs

# Do we allow plugins to be used? This will load plugins from the system
# and user plugin directiories when set to true (See the README for the default
# plugin locations).

# See the README for full information on the new source format
# ncsource=interface:options
# for example:
# ncsource=wifi0:type=madwifi
# ncsource=wlan0:name=intel,hop=false,channel=11

# Comma-separated list of sources to enable. This is only needed if you defined
# multiple sources and only want to enable some of them. By default, all defined
# sources are enabled.
# For example, if sources with name=prismsource and name=ciscosource are defined,
# and you only want to enable those two:
# enablesources=prismsource,ciscosource

# Control which channels we like to spend more time on. By default, the list
# of channels is pulled from the driver automatically. By setting preferred channels,
# if they are present in the channel list, they'll be set with a timing delay so that
# more time is spent on them. Since 1, 6, 11 are the common default channels, it makes
# sense to spend more time monitoring them.
# For finer control, see further down in the config for the channellist= directives.

# How many channels per second do we hop? (1-10)

# By setting the dwell time for channel hopping we override the channelvelocity
# setting above and dwell on each channel for the given number of seconds.

# Channels are defined as:
# channellist=name:ch1,ch2,ch3
# or
# channellist=name:range-start-end-width-offset,ch,range,ch,...
# Channels may be a numeric channel or a frequency
# Channels may specify an additional wait period. For common default channels,
# an additional wait period can be useful. Wait periods delay for that number
# of times per second - so a configuration hopping 10 times per second with a
# channel of 6:3 would delay 3/10ths of a second on channel 6.
# Channel lists may have up to 256 channels and ranges (combined). For power
# users scanning more than 256 channels with a single card, ranges must be used.
# Ranges are meant for "power users" who wish to define a very large number of
# channels. A range may specify channels or frequencies, and will automatically
# sort themselves to cover channels in a non-overlapping fashion. An example
# range for the normal 802.11b/g spectrum would be:
# range-1-11-3-1
# which indicates starting at 1, ending at 11, a channel width of 3 channels,
# incrementing by one. A frequency based definition would be:
# range-2412-2462-22-5
# since 11g channels are 22 mhz wide and 5 mhz apart.
# Ranges have the flaw that they cannot be shared between sources in a non-overlapping
# way, so multiple sources using the same range may hop in lockstep with each other
# and duplicate the coverage.
# channellist=demo:1:3,6:3,11:3,range-5000-6000-20-10

# Default channel lists
# These channel lists MUST BE PRESENT for Kismet to work properly. While it is
# possible to change these, it is not recommended. These are used when the supported
# channel list can not be found for the source; to force using these instead of
# the detected supported channels, override with channellist= in the source defintion
# IN GENERAL, if you think you want to modify these, what you REALLY want to do is
# copy them and use channellist= in the packet source.

# Client/server listen config
# People allowed to connect, comma seperated IP addresses or network/mask
# blocks. Netmasks can be expressed as dotted quad (/ or as
# numbers (/24)
# Maximum number of concurrent GUI's
# Maximum backlog before we start throwing out or killing clients. The
# bigger this number, the more memory and the more power it will use.

# Server + Drone config options. To have a Kismet server export live packets
# as if it were a drone, uncomment these.
# dronelisten=tcp://
# droneallowedhosts=
# dronemaxclients=5
# droneringlen=65535

# OUI file, expected format 00:11:22manufname
# IEEE OUI file used to look up manufacturer info. We default to the
# wireshark one since most people have that.

# Do we have a GPS?
# Do we use a locally serial attached GPS, or use a gpsd server?
# (Pick only one)
# gpstype=serial
# What serial device do we look for the GPS on?
# Host:port that GPSD is running on. This can be localhost OR remote!
# Do we lock the mode? This overrides coordinates of lock "0", which will
# generate some bad information until you get a GPS lock, but it will
# fix problems with GPS units with broken NMEA that report lock 0
# Do we try to reconnect if we lose our link to the GPS, or do we just
# let it die and be disabled?

# Do we export packets over tun/tap virtual interfaces?
# What virtual interface do we use

# Packet filtering options:
# filter_tracker - Packets filtered from the tracker are not processed or
# recorded in any way.
# filter_export - Controls what packets influence the exported CSV, network,
# xml, gps, etc files.
# All filtering options take arguments containing the type of address and
# addresses to be filtered. Valid address types are 'ANY', 'BSSID',
# 'SOURCE', and 'DEST'. Filtering can be inverted by the use of '!' before
# the address. For example,
# filter_tracker=ANY(!"00:00Big GrinE:AD:BE:EF")
# has the same effect as the previous mac_filter config file option.
# filter_tracker=...
# filter_dump=...
# filter_export=...
# filter_netclient=...

# Alerts to be reported and the throttling rates.
# alert=name,throttle/unit,burst
# The throttle/unit describes the number of alerts of this type that are
# sent per time unit. Valid time units are second, minute, hour, and day.
# Burst describes the number of alerts sent before throttling takes place.
# For example:
# alert=FOO,10/min,5
# Would allow 5 alerts through before throttling is enabled, and will then
# limit the number of alerts to 10 per minute.
# A throttle rate of 0 disables throttling of the alert.
# See the README for a list of alert types.

# Controls behavior of the APSPOOF alert. SSID may be a literal match (ssid=) or
# a regex (ssidregex=) if PCRE was available when kismet was built. The allowed
# MAC list must be comma-separated and enclosed in quotes if there are multiple
# MAC addresses allowed. MAC address masks are allowed.

# Known WEP keys to decrypt, bssid,hexkey. This is only for networks where
# the keys are already known, and it may impact throughput on slower hardware.
# Multiple wepkey lines may be used for multiple BSSIDs.
# wepkey=00Big GrinE:AD:C0Big GrinE:00,FEEDFACEDEADBEEF01020304050607080900

# Is transmission of the keys to the client allowed? This may be a security
# risk for some. If you disable this, you will not be able to query keys from
# a client.

# How often (in seconds) do we write all our data files (0 to disable)

# Do we use sound?
# Not to be confused with GUI sound parameter, this controls wether or not the
# server itself will play sound. Primarily for headless or automated systems.
# Path to sound player


# Does the server have speech? (Again, not to be confused with the GUI's speech)
# Binary used for speech (if not in path, full path must be specified)
# Specify raw or festival; Flite (and anything else that doesn't need formatting
# around the string to speak) is 'raw', festival requires the string be wrapped in
# SayText("...")

# How do we speak? Valid options:
# speech Normal speech
# nato NATO spellings (alpha, bravo, charlie)
# spell Spell the letters out (aye, bee, sea)

speech=new,"New network detected s.s.i.d. %1 channel %2"
speech=alert,"Alert %1"
speech=gpslost,"G.P.S. signal lost"
speech=gpslock,"G.P.S. signal O.K."

# How many alerts do we backlog for new clients? Only change this if you have
# a -very- low memory system and need those extra bytes, or if you have a high
# memory system and a huge number of alert conditions.

# File types to log, comma seperated. Built-in log file types:
# alert Text file of alerts
# gpsxml XML per-packet GPS log
# nettxt Networks in text format
# netxml Networks in XML format
# pcapdump tcpdump/wireshark compatible pcap log file
# string All strings seen (increases CPU load)

# Format of the pcap dump (PPI or 80211)
# pcapdumpformat=80211

# Default log title

# logtemplate - Filename logging template.
# This is, at first glance, really nasty and ugly, but you'll hardly ever
# have to touch it so don't complain too much.
# %p is replaced by the logging prefix + '/'
# %n is replaced by the logging instance name
# %d is replaced by the starting date as Mon-DD-YYYY
# %D is replaced by the current date as YYYYMMDD
# %t is replaced by the starting time as HH-MM-SS
# %i is replaced by the increment log in the case of multiple logs
# %l is replaced by the log type (pcapdump, strings, etc)
# %h is replaced by the home directory


# Where state info, etc, is stored. You shouldnt ever need to change this.
# This is a directory.

Un compañero de usglobalsat comentaba lo del cielo despejado y tal,lo digo por que eso ya se ha probado y nada,otro buen compañero de seguridadwireless comentaba que podria fallar el gpsd,que parece que todo apunta a eso ,he probado con versiones diferentes pero sin resultados correctos,sigo igual,me da que este gps al manejar dos protocolos nmea 0183,este segun el fabricante por defecto, y el sirf binary,por ahi puede venir el lio,no sé estoy ya casi por tirar la toalla,ya no se me ocurre qué más probar,o cambiar de gps que de momento va a ser que no,pero se admiten sugerencias :o
saludos y perdón por el peazo mensaje.

Salto de foro:

Usuarios navegando en este tema: 1 invitado(s)