1
- # Passive Identification of BackScatter
1
+ # Passive Identification of BackScatter (pibs)
2
+
2
3
Read a pcap file and display potential backscatter traffic on standard output
3
4
4
5
This is very early stage and subject to change.
5
6
6
-
7
7
# Install dependencies
8
8
9
- As there were some changes in libwiretap, at least the version 2.6.3-1 is needed.
9
+ As there were some changes in libwiretap, at least the version 2.6.3-1 is required.
10
+
10
11
``` shell
11
12
apt-get install libwiretap-dev
12
13
apt-get install libhiredis-dev
@@ -16,12 +17,11 @@ apt-get install libglib2.0-dev
16
17
make
17
18
```
18
19
19
- # How to use
20
+ # How to use pibs
20
21
21
- ``` shell
22
- ./pibs -r pcapfile.cap -b
22
+ ` ./pibs -r pcapfile.cap -b `
23
23
24
- ./pibs -u e344c4fb-442e-45a6-92b9-d8e30aeef448 -z 127.0.0.1 -p 6379 -y 2
24
+ ` ./pibs -u e344c4fb-442e-45a6-92b9-d8e30aeef448 -z 127.0.0.1 -p 6379 -y 2 `
25
25
26
26
Consumes the files from the worker queue and write potential backscatter on
27
27
standard output. The worker queue should include absolute filenames.
@@ -30,39 +30,38 @@ The redis database 2 is used as specified with the -y option.
30
30
The string e344c4fb-442e-45a6-92b9-d8e30aeef448 is the uuid that must be inline with the
31
31
worker.
32
32
33
- pibs -r source.cap.gz -w backscatter.cap
33
+ ` pibs -r source.cap.gz -w backscatter.cap `
34
34
35
35
Read the file source.cap.gz, identify potential backscatter and store it in the
36
36
file backscatter.cap to be further analysed with other tools such as wireshark
37
- ```
38
37
39
- pibs -r pcapfile.cap -s
38
+ ` pibs -r pcapfile.cap -s `
40
39
41
40
Read the file source.cap, identify potential backscatter and display the
42
41
usage of the used internal hash table. Feature for debugging purpose.
43
42
44
- pibs -r pcapfile.cap -d
43
+ ` pibs -r pcapfile.cap -d `
45
44
46
45
Dump the internal data structures for debugging purposes from the processing
47
46
of the pcapfile.
48
47
49
- pibs -n
48
+ ` pibs -n `
50
49
51
50
Create fresh internal data structure as shared memory for multi processing
52
51
purposes. The segment id is displayed on standard output.
53
52
54
- pibs -n -i myinstance.shm
53
+ ` pibs -n -i myinstance.shm `
55
54
56
55
Create a shared memory and store the segment identifier in the file
57
56
myinstance.shm
58
57
59
- pibs -r pcapfile.cap.gz -a -i instance.shm
58
+ ` pibs -r pcapfile.cap.gz -a -i instance.shm `
60
59
61
60
Read pcapfile.cap.gz identify potential backscatter and store it in the
62
61
shared memory segment with the identifier stored in the file instance.shm.
63
62
The previous states are taken into account.
64
63
65
- pibs -i instance.shm -a -s
64
+ ` pibs -i instance.shm -a -s `
66
65
67
66
Display the usage of the internal hash table from the shared memory segment
68
67
specified in the file instance.shm. This command can be executed in parallel
0 commit comments