| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_components:utilities:management_utilities [2024/10/11 08:33] – elena.krasnobryzh | en:dpi:dpi_components:utilities:management_utilities [2026/03/02 14:28] (current) – [driverctl] elena.krasnobryzh |
|---|
| * ''unset-override 0000:04:00.0'' – exit the card from the DPDK mode\\ **The fastDPI process must first be stopped with the command ''service fastdpi stop''!** | * ''unset-override 0000:04:00.0'' – exit the card from the DPDK mode\\ **The fastDPI process must first be stopped with the command ''service fastdpi stop''!** |
| * ''-v set-override 0000:04:00.0 vfio-pci'' – return the cards back under DPDK control after working with the standard driver\\ **When switching cards to DPDK mode, be careful not to accidentally switch the server control interface to DPDK mode - communication with the server will be immediately interrupted!** | * ''-v set-override 0000:04:00.0 vfio-pci'' – return the cards back under DPDK control after working with the standard driver\\ **When switching cards to DPDK mode, be careful not to accidentally switch the server control interface to DPDK mode - communication with the server will be immediately interrupted!** |
| | |
| | <note important> |
| | Please note that Mellanox network interface cards cannot be switched to DPDK using the driverctl utility — their driver is installed in a different way. They also remain under operating system control, therefore the interfaces will still appear in the output of ip/ipconfig utilities. |
| | If it is necessary to install a driver to support DPDK on Mellanox network cards, please [[en:dpi:techsupport_info|contact technical support]]. |
| | </note> |
| |
| <note>Configuring DPDK in Hyper-V is described in detail in the appropriate [[en:dpi:dpi_components:platform:dpi_config#configuration_in_hyper-v|section]].</note> | <note>Configuring DPDK in Hyper-V is described in detail in the appropriate [[en:dpi:dpi_components:platform:dpi_config#configuration_in_hyper-v|section]].</note> |
| |
| =====checkproto===== | =====checkproto===== |
| Check if the address or port is included in the custom protocol.\\ Example of a port check: | Check if the address or port is included in the custom protocol.\\ Example of a address check: |
| <code bash>checkproto youtube</code> | <code bash>checkproto youtube.com</code> |
| |
| =====checknat===== | =====checknat===== |
| |
| Parameters: | Parameters: |
| * ''nthr'' – num work threads per cluster | * ''nthr'' – num work threads per cluster. Maximum value - 128 |
| * ''algo'' – **0** - hashmask (default), **1** - crc, **2** - rxdsp_2 | * ''algo'' – **0** - hashmask (default), **1** - crc, **2** - rxdsp_2 |
| * ''cidrs'' – list cidr white address | * ''cidrs'' – list cidr white address |
