Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/opusvl/p6-geotrack-daemon
Perl 6 daemon to slurp netXML files and parse the data into a PostgreSQL database.
https://github.com/opusvl/p6-geotrack-daemon
airmon-ng netxml perl6 perl6-application
Last synced: about 2 months ago
JSON representation
Perl 6 daemon to slurp netXML files and parse the data into a PostgreSQL database.
- Host: GitHub
- URL: https://github.com/opusvl/p6-geotrack-daemon
- Owner: OpusVL
- License: bsd-3-clause
- Created: 2019-10-11T13:31:11.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2019-11-14T11:54:44.000Z (about 5 years ago)
- Last Synced: 2024-10-11T20:42:52.195Z (2 months ago)
- Topics: airmon-ng, netxml, perl6, perl6-application
- Language: Perl 6
- Size: 17.6 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# p6-geotrack-daemon
Perl 6 daemon to slurp netXML files and parse the data into a PostgreSQL database.
## Dependencies
- Rakudo 2019.03 (Perl 6.d)
- libpq-dev
### Zef modules
```
zef install XML DB::Pg JSON::Fast Terminal::ANSIColor
```
## Configuration
## Preparing a PostgreSQL database
To prepare your PostgreSQL database, use the provided example [`database-tables.sql`](https://github.com/OpusVL/p6-geotrack-daemon/blob/master/database-tables.sql) file to create the two required tables. I've personally been testing with the [`mdillon/postgis`](https://hub.docker.com/r/mdillon/postgis) Dockerfile which gives us a not-so unreasonable PostgreSQL 11.2 to work with.
```sql
CREATE DATABASE geotrack;
CREATE EXTENSION postgis;
CREATE TABLE "access-points" (
name text NOT NULL,
description text,
location geography(POINT),
PRIMARY KEY (name)
);
CREATE TABLE "client-data" (
client text NOT NULL,
"client-manufacturer" text DEFAULT NULL,
"access-point" text NOT NULL,
"last-signal-dbm" int,
"last-noise-dbm" int,
"last-signal-rssi" int,
"last-noise-rssi" int,
"min-signal-dbm" int,
"min-noise-dbm" int,
"min-signal-rssi" int,
"min-noise-rssi" int,
"max-signal-dbm" int,
"max-noise-dbm" int,
"max-signal-rssi" int,
"max-noise-rssi" int,
timestamp timestamptz NOT NULL,
FOREIGN KEY ("access-point") REFERENCES "access-points"(name)
);
```
### Access Points
For each wireless basestation, you'll need to do some manual SQL queries to add a new 'access point' to the `access-points` table. This involves first discovering the coordinates of the physical location and using the PostGIS extension to convert that data into a `geography(POINT)`.
```sql
geotrack=# SELECT ST_GeometryFromText('POINT(52.3710507 -1.264331)', 4326);
st_geometryfromtext
----------------------------------------------------
0101000020E610000036D4DE967E2F4A40871A8524B33AF4BF
(1 row)
```
With this information, we can now add our new access point.
```sql
INSERT INTO "access-points" VALUES ('opusvlwifi', 'OpusVL Office Wifi', '0101000020E610000036D4DE967E2F4A40871A8524B33AF4BF');
```