Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:dpi:dpi_components:utilities:oldutility:nfsen:nfsen_ext [2024/09/26 15:29] – external edit 127.0.0.1 | en:dpi:dpi_components:utilities:oldutility:nfsen:nfsen_ext [2025/08/29 09:45] (current) – elena.krasnobryzh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | {{indexmenu_n> | + | {{indexmenu_n> |
| - | NFSEN functionality | + | NFSEN is enhanced with capabilities for generating graphs |
| - | < | + | and protocol |
| - | -[[nfsen_ext_graph|Making charts]] | + | |
| - | -[[nfsen_ext_reports|Making reports]] | + | |
| - | -[[nfsen_full_netflow|Making reports by IP]] | + | |
| - | < | + | |
| + | - Graph generation | ||
| + | - Report generation | ||
| + | - IP-based report generation | ||
| + | |||
| + | ===== Graph Generation ===== | ||
| + | Before generating a graph, ensure that at least one day's worth of statistics has been accumulated. | ||
| + | |||
| + | For your convenience, | ||
| + | |||
| + | Run the script to create a profile with top protocols | ||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | where | ||
| + | consumers 8 - number of protocols displayed on the graph (maximum 10)\\ | ||
| + | divide-up-down - means incoming and outgoing traffic will be displayed separately relative to the zero axis\\ | ||
| + | profile-name top_8_protocols - name of the created profile((the profile is selected in the upper right corner of the NFSEN screen; if you cannot select the newly created profile, select the Stat tab in the top row)) | ||
| + | |||
| + | As a result of the script, the profile top_8_protocols will be created, where the top 8 protocols by volume will be highlighted in different colors on the graphs: | ||
| + | {{ nfsen-combined.png }} | ||
| + | Protocols not in the top will be combined into " | ||
| + | This profile is convenient for generating protocol reports, as indicated in the section [[dpi: | ||
| + | |||
| + | Furthermore, | ||
| + | Example: only torrents are left on the graph | ||
| + | {{ nfsen-torrents.png }} | ||
| + | |||
| + | Similarly, to create a profile with top directions, run the script: | ||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | As a result, the profile top_10_directions will be created, where you can, for example, visually observe | ||
| + | the difference in traffic volume to GOOGLE and VKONTAKTE services | ||
| + | {{ nfsen-vk-vs-google.png }} | ||
| + | |||
| + | |||
| + | ===== Report Generation ===== | ||
| + | Select the live profile (profile is selected in the upper right corner) or, if you previously created a separate profile with top directions, as indicated in the section [[dpi: | ||
| + | |||
| + | To create a report on autonomous systems, click the Details tab in the very top row and select on the graph | ||
| + | the required period (Time Window) or move the slider to the investigated moment in time (Single Timeslot) | ||
| + | |||
| + | Now in the Options section (under Netflow Processing), | ||
| + | |||
| + | {{ : | ||
| + | where Stat TopN - list of top directions\\ | ||
| + | Top: 10 - number of elements in the top\\ | ||
| + | Stat: Any AS Name/SRC AS Name or DST AS Name - consider all traffic or only in one direction\\ | ||
| + | Order By: bytes - calculate top by data volume\\ | ||
| + | and press the Process button.\\ | ||
| + | For the live profile, you must also select only Source: directions | ||
| + | |||
| + | As a result, a report on top data transmission directions will be prepared | ||
| + | {{ : | ||
| + | |||
| + | |||
| + | Similarly, when selecting Source: protocols or a separate profile with top protocols, you can generate | ||
| + | reports on protocols in both or one of the directions DPI Protocol/IN DPI Protocol/ | ||
| + | |||
| + | {{ : | ||
| + | {{ : | ||
| + | |||
| + | ===== IP-Based Report Generation ===== | ||
| + | 1. Add a new data receiver to the nfsen configuration | ||
| + | < | ||
| + | vi / | ||
| + | |||
| + | %sources = ( | ||
| + | ' | ||
| + | ' | ||
| + | ' | ||
| + | ); | ||
| + | </ | ||
| + | |||
| + | 2. Activate changes in the configuration | ||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | 3. Allow udp reception on port 9999 in iptables | ||
| + | < | ||
| + | vi / | ||
| + | -A INPUT -m state --state NEW -m udp -p udp --dport 9999 -j ACCEPT | ||
| + | service iptables restart | ||
| + | </ | ||
| + | |||
| + | 4. Activate full netflow sending to the created collector on dpi (in addition to protocol and direction collectors) | ||
| + | < | ||
| + | vi / | ||
| + | netflow=11 | ||
| + | netflow_full_collector=127.0.0.1: | ||
| + | netflow_passive_timeout=20 | ||
| + | netflow_active_timeout=60 | ||
| + | service fastdpi restart | ||
| + | </ | ||
| + | |||
| + | nfsen is not the best tool for investigating full netflow | ||
| + | but it allows generating simple reports (section on the Netflow Processing page, for example, top by ip) | ||
| + | |||
| + | In full netflow, the original port number is transmitted by default, | ||
| + | therefore, protocol reports do not work. To activate encoding protocol information in the port number, enable the setting | ||
| + | netflow_full_port_swap=1 | ||