| Bug ID |
10431
|
| Summary |
Feature request: Add GPS coordinates to additional column
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Common utilities (libwsutil)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Hello,
regarding to future possibility of use wireshark for mobile capturing of
wireless packets, it can be very usefull to add to each line of received packet
additional column with GPS coordinates. It can be performed via additional
option in preferences, where can be selected number of serial port for GPS and
its parameters (mostly used GPS format NMEA 0183, baudrate etc.). If checkbox
in this option will be enabled, that it can be possible to add GPS coordinates
to each line of received packet, together with time and with possibility to
export this to csv or ecel file.
Additional, it can be nice to export of this captured file to google earth,
where it can be seen after click on each place, what was captured (of course it
depends what informations are exatly needed to show in, ie. information belllow
described).
Using this feature can be wide for mobile monitoring, what wireless devices
transmit and where.
>From my point of use, I want to use it to gather information about special
features of RLAN devices, which is transmitted only in beacon packets. Exatly,
if it is supported by device I can see, if that device use and where ie.
Spectrum Management (and comply with EU regulation), what frequency channels
use, if using TPC (transmit power control) and etc.
Somethink like above is possible via Kismet, but Wireshark is most user friedly
than Kismet and using this feature need more experience in linux (for other
people than me, it is very big problem and for this people is kismet in the
fact unusable).
Many thanks for Your time
Martin
You are receiving this mail because:
- You are watching all bug changes.