---
title: "Configure interfaces for Netsense"
canonical: "https://thoughtdata.refined.site/space/TUD/55643176/Configure%20interfaces%20for%20Netsense"
format: markdown
---
## Configuring Interfaces for Netsense

Determine the interface on which you wish to run Netsense in order to monitor the network traffic/packets that flow through that interface. Use the Linux interface configuration command ifconfig to get started.

![image](media://66763d26-d89b-4780-b4e8-e074998e3842)

Get available interface details

The system illustrated in the sample installation is running 3 interfaces:

- ens10
- eth0
- lo (loopback)

When you feed the traffic to Netsense packet sensor physical or virtual machine, you should be aware of which interface you are receiving the traffic to be monitored.

**Note**: These interface names/strings are samples only. They may not be the same in your installation scenario. Netsense can be configured to monitor one or more of these interfaces.

Go to **"cd /user/local/thoughtdata/netsense/etc".** Open the node.cfg file to configure an monitoring interface using the vi command as illustrated below

![image](media://8011eb31-6b6e-4132-becd-feeeac5899cb)

Set interfaces in the node.cfg file using the vi editor

In the sample section [worker-1] find the parameter **"interface" **and replace the string** "lo" **with the right interface name which you would like to monitor. Sample default config is shown below.

![image](media://18eee277-e80d-463a-b84c-c8b7abf73e1c)

Default config - node.cfg

**Note**: worker -1 represents an instance or Netsense packet sensor. By default it is set to the loopback (lo) interface.

Change the monitoring interface. For example eth0.

![image](media://3bcfbd3b-3cc4-42f7-abff-cadc61f8b91f)

The packet capture (pcap) interface of the thread worker- 1 changed to eth0

Save changes using the wq! command as illustrated.

![image](media://a875a0df-1260-4cb5-a128-16ffe972e6eb)

Save changes to the configuration file

**Note**: If you wish to monitor multiple interfaces, you have to configure Netsense to run as multiple process instances for different interfaces on same machine, repeat the above steps accordingly for [worker-2], [worker-3] and so on with their respective monitoring interfaces.

This step is optional. Complete it only if you require multiple instances of NetSense.  

      ‎Change worker - 2 packet capture interface. For example ens10.  

      ‎You can edit the existing worker - 2 section or copy the worker- 1 section, paste it and rename it as worker - 2 and change the interface string.

![image](media://bb6f1d95-4dc8-4314-bef1-6313c972332f)

Multiple instances of Netsense – for packet capture.

**Note**: Save the node.cfg file changes using the wq! command and exit.

  

      Configuring Netsense to monitor various interfaces on the system on which it is installed is now completed. Proceed to the next procedure of steps to configure Netsense to communicate with Enterprise360.