1
0
Fork 0
mirror of https://github.com/pavel-odintsov/fastnetmon synced 2024-04-28 09:35:16 +02:00
mirror of the fastnetmon repo with rewritten history
Go to file
Pavel Odintsov 0581c004b3
Renamed and fixed happy customers. REG.RU switched to different tool for this task
2017-12-03 22:05:13 +00:00
.github Fix name 2016-09-25 14:12:16 +03:00
debian debian: Bump Standards-Version to 4.0.0 2017-07-27 11:52:51 +02:00
docs Renamed and fixed happy customers. REG.RU switched to different tool for this task 2017-12-03 22:05:13 +00:00
packages/docker Fixed bunch of paths to old versions of FNM 2017-12-03 21:22:11 +00:00
src Fixed bunch of paths to old versions of FNM 2017-12-03 21:22:11 +00:00
.gitignore Add json_config and modified fastnetmon_a10_v02.py file 2016-07-12 13:41:31 -07:00
.travis.yml Fix build dir again 2016-08-13 12:50:01 +03:00
HAPPY_CUSTOMERS.md Renamed and fixed happy customers. REG.RU switched to different tool for this task 2017-12-03 22:05:13 +00:00
LICENSE Fixed bunch of paths to old versions of FNM 2017-12-03 21:22:11 +00:00
README.md Added path to official ports 2017-12-03 21:48:49 +00:00
THANKS.md Moved thanks file to top level fodler 2017-12-03 22:04:00 +00:00

FastNetMon Community Edition

FastNetMon - A high performance DoS/DDoS load analyzer built on top of multiple packet capture engines (NetFlow, IPFIX, sFLOW, SnabbSwitch, netmap, PF_RING, PCAP).

What can we do? We can detect hosts in our networks sending or receiving large volumes of packets/bytes/flows per second. We can call an external script to notify you, switch off a server, or blackhole the client.

To enable sFLOW, simply specify IP of the server running FastNetMon and specify (configurable) port 6343 To enable netflow, simply specify IP of the server running FastNetMon and specify (configurable) port 2055

Why did we write this? Because we can't find any software for solving this problem in the open source world!

What is a "flow" in FastNetMon terms? It's one or multiple UDP, TCP, or ICMP connections with unique src IP, dst IP, src port, dst port, and protocol.

License: GPLv2

Project

Supported packet capture engines

  • NetFlow v5, v9
  • IPFIX
  • sFLOW v4 (since 1.1.3), v5
  • Port mirror/SPAN capture with PF_RING (with ZC/DNA mode support need license), SnabbSwitch, NETMAP and PCAP

You can check out the comparison table for all available packet capture engines.

Complete integration with following vendors

Travis status: Travis

Features

  • Complete BGP Flow Spec support, RFC 5575
  • Process and distinguish incoming and/or outgoing traffic
  • Trigger block/notify script if an IP exceeds defined thresholds for packets/bytes/flows per second
  • Thresholds can be configured per-subnet with the hostgroups feature
  • Announce blocked IPs via BGP to routers with ExaBGP
  • GoBGP integration for unicast IPv4 announcements (you need build support manually).
  • Full integration with Graphite and InfluxDB
  • API (you need build support manually)
  • Redis integration
  • MongoDB integration
  • Deep packet inspection for attack traffic
  • netmap support (open source; wire speed processing; only Intel hardware NICs or any hypervisor VM type)
  • SnabbSwitch support (open source, very flexible, LUA driven, very-very-very fast)
  • Filter NetFlow v5 flows or sFLOW packets with LUA scripts (useful for excluding particular ports)
  • Supports L2TP decapsulation, VLAN untagging and MPLS processing in mirror mode
  • Works on server/soft-router
  • Detects DoS/DDoS in as little as 1-2 seconds
  • Tested up to 10Gb with 12 Mpps on Intel i7 3820 with Intel NIC 82599
  • Complete plugin support
  • Captures attack fingerprints in PCAP format
  • Complete support for most popular attack types

Running Fastnetmon

Supported platforms

  • Linux (Debian 6/7/8/9, CentOS 6/7, Ubuntu 12.04, 14.04, 16.04)
  • FreeBSD 9, 10, 11: offciail port.
  • Mac OS X Yosemite (only 1.1.2 release)

Supported architectures

  • x86 64 bit (recommended)
  • x86 32 bit

Hardware requirements

  • At least 1 GB of RAM for compilation purposes

Router integration instructions

Distributions supported

Screenshoots

Main program screenshot:

Main screen image

Example CPU load on Intel i7 2600 with Intel X540/82599 NIC at 400 kpps load: Cpu consumption

Example deployment scheme: Network diagramm

Example of notification email about detected attack.

Author: Pavel Odintsov

Follow us at Twitter and LinkedIn