1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
|
Currently only operating systems running on Linux kernels with the option
CONFIG_PACKET_MMAP enabled. This feature can be found even back to the days of
2.4 kernels. Most operating systems ship pre-compiled kernels that have this
config option enabled and even the latest kernel versions got rid of this
option and have this functionality already built-in. However, we recommend a
kernel >= 2.6.31, because the TX_RING is officially integrated since then. In
any case, if you have the possibility, consider getting the latest kernel from
Linus' Git repository, tweak and compile it, and run this one!
A note for distribution package maintainers can be found at the end of the file.
What additional tools next to your build-chain are required?
- ccache (optional)
- gpg (optional)
- pkg-config: all
- flex, bison: bpfc, trafgen
What libraries are required?
- libncurses: ifpps, flowtop
- libGeoIP >=1.4.8: astraceroute, flowtop, netsniff-ng
- libz: astraceroute, flowtop, netsniff-ng
- libnacl: curvetun
- libnetfilter-conntrack: flowtop
- libpcap: mausezahn, netsniff-ng (tcpdump-like filters)
- liburcu: flowtop
- libnl3: netsniff-ng, trafgen
- libcli: mausezahn
- libnet: mausezahn
What additional tools are recommended, but not mandatory after the build?
- cpp: trafgen
- ntpd: curvetun
- setcap: all
It is common, that these libraries are shipped as distribution packages
for an easy installation. We try to keep this as minimal as possible.
One-liner installation for *all* dependencies on Debian:
$ sudo apt-get install ccache flex bison libnl-3-dev \
libnl-genl-3-dev libgeoip-dev libnetfilter-conntrack-dev \
libncurses5-dev liburcu-dev libnacl-dev libpcap-dev \
zlib1g-dev libcli-dev libnet1-dev
One-liner installation for *all* dependencies on Fedora:
$ sudo yum install ccache flex bison ccache libnl3-devel \
GeoIP-devel libnetfilter_conntrack-devel ncurses-devel \
userspace-rcu-devel nacl-devel libpcap-devel zlib-devel \
libcli-devel libnet-devel
After downloading the netsniff-ng toolkit, you should change to the
repository root directory:
$ cd netsniff-ng/
The installation (deinstallation) process is fairly simple:
$ ./configure
$ make
# make install
(# make uninstall)
In order to remove all build files from the source tree:
$ make clean
To bring the source tree into a pristine state, there are two options.
The first one will remove all build and build config file, the latter
will also remove any manually added files:
$ make distclean
($ make mrproper)
You can also build/install/uninstall only a particular tool, e.g.:
$ make trafgen
# make trafgen_install
(# make trafgen_uninstall)
If you want to build all tools, but {curvetun,mausezahn} (i.e. because you
don't need the tunneling software and the NaCl build process lasts quite long):
$ make allbutcurvetun (allbutmausezahn)
# make install_allbutcurvetun (install_allbutmausezahn)
(# make uninstall)
In order to build curvetun, libnacl must be built first. A helper script
called nacl_build.sh is there to facilitate this process. If you want to
build NaCl in the directory ~/nacl, the script should be called this way:
$ cd curvetun
$ ./nacl_build.sh ~/nacl
There's also an abbreviation for this by simply typing:
$ make nacl
This gives an initial output such as "Building NaCl for arch amd64 on host
fuuubar (grab a coffee, this takes a while) ...". If the automatically
detected architecture (such as amd64) is not the one you intend to compile
for, then edit the (cc="gcc") variable within the nacl_build.sh script to
your cross compiler. Yes, we know, the build system of NaCl is a bit of a
pain, so you might check for a pre-built package from your distribution in
case you are not cross compiling.
If NaCl already has been built on the target, it is quicker to use
nacl_path.sh this way:
$ cd curvetun
$ ./nacl_path.sh ~/nacl/build/include/x86 ~/nacl/build/lib/x86
When done, netsniff-ng's build infrastructure will read those evironment
variables in order to get the needed paths to NaCl.
If you're unsure with any make targets, check out: make help
In order to run the toolkit as a normal user, set the following privilege
separation after the build/installation:
$ sudo setcap cap_net_raw,cap_ipc_lock,cap_sys_admin,cap_net_admin=eip {toolname}
For cross-compiling netsniff-ng, the process is faily simple. Assuming you
want to build netsniff-ng for the Microblaze architecture, update the PATH
variable first, e.g.:
$ export PATH=<cc-tools-path>/microblazeel-unknown-linux-gnu/bin:$PATH
And then, build the toolkit like this:
$ make CROSS_COMPILE=microblazeel-unknown-linux-gnu- \
CROSS_LD_LIBRARY_PATH=<cc-lib-search-path>
Note that some adaptations might be necessary regarding the CFLAGS, since not
all might be supported by a different architecture. Probably the most simple
way would be to run make CFLAGS="-O2 -Wall".
For power users we have a set of zsh auto completion files, have a look at all
file with ending *.zsh. There's also a BPF vim syntax highlighting file in the
tree called bpf.vim.
For doing a debug build of the toolkit with less optimizations and non-stripped
symbols, do:
$ make DEBUG=1
For debugging the build system, full commands are shown if every make target is
executed with:
$ make Q=
Concerning packaging the toolkit for a Linux distribution, by default,
netsniff-ng has some architecture-specific tuning options enabled that don't
belong into a package binary of a distribution. Hence, you might want to adapt
some build-related things before starting to package the toolkit. All
necessary things (e.g., CFLAGS,WFLAGS) can be found in Makefile. Hence,
you need to adapt it there. You can then build and install the toolkit into
a prefixed path like:
$ make PREFIX=<path-prefix-for-package>
$ make PREFIX=<path-prefix-for-package> install
Thanks for maintaining netsniff-ng in your distribution. Further questions
will be answered on the public mailing list.
|
