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 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478
|
<HTML
><HEAD
><TITLE
>flow-tools-examples</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.71
"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="AEN1"
><SPAN
CLASS="APPLICATION"
>flow-tools-examples</SPAN
></A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN6"
></A
><H2
>Name</H2
><SPAN
CLASS="APPLICATION"
>flow-tools-examples</SPAN
> -- Example usage of flow-tools.</DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN10"
></A
><H2
>EXAMPLE - Configuring Cisco IOS Router</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN12"
></A
><P
></P
><P
>NetFlow is configured on each input interface, then global commands are
used to specify the export destination. To ensure a consistant source
address address Loopback0 is configured as the export source.
<PRE
CLASS="PROGRAMLISTING"
>ip cef distributed
ip flow-export version 5 origin-as
ip flow-export destination 10.0.0.100 5004
ip flow-export source Loopback0
interface Loopback0
ip address 10.1.1.1 255.255.255.255
interface FastEthernet0/1/0
ip address 10.0.0.1 255.255.255.0
no ip directed-broadcast
ip route-cache flow
ip route-cache distributed </PRE
>
Many other options exist such as aggregated NetFlow and sampled NetFlow which
are detailed at <A
HREF="http://www.cisco.com"
TARGET="_top"
>http://www.cisco.com</A
>.</P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN16"
></A
><H2
>EXAMPLE - Configuring Cisco CatIOS Switch</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN18"
></A
><P
></P
><P
>Some Cisco Catalyst switches support a different implementation of NetFlow
that is performed on the supervisor. With the cache based forwarding model
which is implemented in the Catalyst 55xx with Route Switch Module (RSM)
and NetFlow Feature Card (NFFC), the RSM processes the first flow and the
remaining packets in the flow are forwarded by the Supervisor. This is
also implemented in the early versions of the 65xx with MSFC. The
deterministic forwarding model used in the 65xx with MSFC2 do not use
NetFlow to determine the forwarding path, the flow cache is only used
for statistics as in the current IOS implementations. In all of
of the above configurations flow exports arrive from both the RSM/MSFC and
the Supervisor engines as distinct streams. In the worst cast the RSM
exports in version 5 and the Supervisor exports in version 7.
Fortunately flow-capture and flow-receive can sort all this out by
processing flows from both sources and converting them to a common
export format.</P
><P
>The router side running IOS is configured identically to the example
given above. The CatIOS NetFlow Data Export configuration follows:</P
><P
><PRE
CLASS="PROGRAMLISTING"
>set mls flow full
set mls nde version 7
set mls nde 10.0.0.1 9800
set mls nde enable</PRE
></P
><P
>When the 65xx is running in Native mode, from a users perspective the
switch is only running IOS.</P
><P
>More detailed examples can be found on Cisco's web site
<A
HREF="http://www.cisco.com"
TARGET="_top"
>http://www.cisco.com</A
>.</P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN26"
></A
><H2
>EXAMPLE - Configuring Juniper Router</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN28"
></A
><P
></P
><P
>Juniper supports flow exports by the routing engine sampling packet
headers and aggregating them into flows. Packet sampling is done by
defining a firewall filter to accept and sample all traffic,
applying that rule to the interface, then configuring the sampling
forwarding option.
<PRE
CLASS="PROGRAMLISTING"
>interfaces {
ge-0/3/0 {
unit 0 {
family inet {
filter {
input all;
output all;
}
address 10.0.0.1/24;
}
}
}
firewall {
filter all {
term all {
then {
sample;
accept;
}
}
}
}
forwarding-options {
sampling {
input {
family inet {
rate 100;
}
}
output {
cflowd 10.0.0.100 {
port 9800;
version 5;
}
}
}
}</PRE
></P
><P
>Other options exist such as aggregated flows which
are detailed at <A
HREF="http://www.juniper.net"
TARGET="_top"
>http://www.juniper.net</A
>.</P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN33"
></A
><H2
>EXAMPLE - Network topology and <TT
CLASS="FILENAME"
>flow.acl</TT
></H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN36"
></A
><P
></P
><P
>The network topology and flow.acl will be used for many of the examples
that follow. Flows are collected and stored in <TT
CLASS="FILENAME"
>/flows/R</TT
>.
<PRE
CLASS="SCREEN"
> ISP-A ISP-B
+ +
+ +
IP=10.1.2.1/24 + + IP=10.1.1.1/24
ifIndex=2 + + ifIndex=1
interface=serial1/1 + + interface=serial0/0
-----
| R | Campus Router
-----
+ +
IP=10.1.4.1/24 + + IP=10.1.3.1/24
ifIndex=4 + + ifIndex=3
interface=Ethernet1/1 + + interface=Ethernet0/0
+ +
Sales Marketing </PRE
>
<PRE
CLASS="PROGRAMLISTING"
>ip access-list standard sales permit 10.1.4.0 0.0.0.255
ip access-list standard not_sales deny 10.1.4.0 0.0.0.255
ip access-list standard marketing permit 10.1.3.0 0.0.0.255
ip access-list standard not_marketing deny 10.1.3.0 0.0.0.255
ip access-list standard campus permit 10.1.4.0 0.0.0.255
ip access-list standard campus permit 10.1.3.0 0.0.0.255
ip access-list standard not_campus deny 10.1.4.0 0.0.0.255
ip access-list standard not_campus deny 10.1.3.0 0.0.0.255
ip access-list standard evil_hacket permit host 10.6.6.6
ip access-list standard spoofer permit host 10.9.9.9
ip access-list standard multicast 224.0.0.0 15.255.255.255</PRE
></P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN41"
></A
><H2
>EXAMPLE - Finding spoofed addresses</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN43"
></A
><P
></P
><P
>A common problem on the Internet is the use of "spoofed" (addresses
that are not assigned to an organization) for use in DoS attacks or
compromising servers that rely on the source IP address for authentication.</P
><P
>Display all flow records that originate from the campus and are sent
to the Internet but are not using legal addresses.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Snot_campus -I1,2 | flow-print</B
></P
><P
>Summary of the destinations of the internally spoofed addresses sorted by octets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Snot_campus -I1,2 | flow-stat -f8 -S2</B
></P
><P
>Summary of the sources of the internally spoofed addresses sorted by flows.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Snot_campus -I1,2 | flow-stat -f9 -S1</B
></P
><P
>Summary of the internally spoofed sources and destination pairs sorted by packets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Snot_campus -I1,2 | flow-stat -f10 -S4</B
></P
><P
>Display all flow records that originate external to the campus that have
campus addresses. Many times these can be attackers trying to exploit host
based authentication mechanisms like unix r* commands. Another common
source is mobile clients which send packets with their campus addresses
before obtaining a valid IP.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Scampus -i1,2 | flow-print</B
></P
><P
>Summary of the destinations of the externally spoofed addresses sorted by octets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Scampus -i1,2 | flow-stat -f8 -S2</B
></P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN63"
></A
><H2
>EXAMPLE - Locate hosts using or running services</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN65"
></A
><P
></P
><P
>Find all SMTP servers active during the collection period
that have established connections to the Internet. Summarize sorted
by octets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -I1,2 -P25 | flow-stat -f9 -S2</B
></P
><P
>Find all outbound NNTP connections to the Internet. Summarize with source
and destination IP sorted by octets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -I1,2 -P119 | flow-stat -f10 -S3</B
></P
><P
>Find all inbound NNTP connections to the Internet. Summarize with source
and destination IP sorted by octets.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -i1,2 -P119 | flow-stat -f10 -S3</B
></P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN75"
></A
><H2
>EXAMPLE - Multicast usage</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN77"
></A
><P
></P
><P
>Summarize Multicast S,G where sources are on campus.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Dmulticast -I1,2 | flow-stat -f10 -S3</B
></P
><P
>Summarize Multicast S,G where sources are off campus.</P
><P
><B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -Dmulticast -i1,2 | flow-stat -f10 -S3</B
></P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN84"
></A
><H2
>EXAMPLE - Find scanners</H2
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN86"
></A
><P
></P
><P
>Find SMTP scanners with flow-dscan. This will also find SMTP clients which
try to contact many servers. This behavior is characterized by a
recent Microsoft worm.</P
><P
><P
CLASS="LITERALLAYOUT"
><B
CLASS="COMMAND"
>touch dscan.suppress.src dscan.suppress.dst</B
><br>
<br>
<B
CLASS="COMMAND"
>flow-cat /flows/R | flow-filter -P25 | flow-dscan -b</B
><br> </P
></P
><P
></P
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN92"
></A
><H2
>AUTHOR</H2
><P
>Mark Fullmer
<TT
CLASS="EMAIL"
><<A
HREF="mailto:maf@splintered.net"
>maf@splintered.net</A
>></TT
></P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN99"
></A
><H2
>SEE ALSO</H2
><P
><SPAN
CLASS="APPLICATION"
>flow-tools</SPAN
>(1)</P
></DIV
></BODY
></HTML
>
|