Difference between revisions of "HowTo Setup A Server With Multiple Network Interface Adapters Using: "nstnetcfg""
(→Stealth Combo Setting Command) |
(→Network Interface Configuration: nstnetcfg) |
||
Line 83: | Line 83: | ||
</div> | </div> | ||
− | == '''Interface: em1''' == | + | == '''Static IPv4 Configured Interfaces''' == |
+ | |||
+ | === '''Interface: em1''' === | ||
<div class="screen"> | <div class="screen"> | ||
Line 92: | Line 94: | ||
</div> | </div> | ||
− | == '''Interface: em0''' == | + | === '''Interface: em0''' === |
<div class="screen"> | <div class="screen"> | ||
Line 101: | Line 103: | ||
</div> | </div> | ||
− | == '''Interface: em2''' == | + | == '''Stealth Confiogured Interfaces == |
+ | |||
+ | === '''Interface: em2''' === | ||
<div class="screen"> | <div class="screen"> | ||
Line 110: | Line 114: | ||
</div> | </div> | ||
− | == '''Interface: em3''' == | + | === '''Interface: em3''' === |
<div class="screen"> | <div class="screen"> | ||
Line 119: | Line 123: | ||
</div> | </div> | ||
− | == '''Interface: p2p1''' == | + | === '''Interface: p2p1''' === |
<div class="screen"> | <div class="screen"> | ||
Line 128: | Line 132: | ||
</div> | </div> | ||
− | == '''Interface: p2p2''' == | + | === '''Interface: p2p2''' === |
<div class="screen"> | <div class="screen"> | ||
Line 137: | Line 141: | ||
</div> | </div> | ||
− | == '''Interface: p4p1''' == | + | === '''Interface: p4p1''' === |
<div class="screen"> | <div class="screen"> | ||
Line 146: | Line 150: | ||
</div> | </div> | ||
− | == '''Interface: p4p2''' == | + | === '''Interface: p4p2''' === |
<div class="screen"> | <div class="screen"> | ||
Line 155: | Line 159: | ||
</div> | </div> | ||
− | == '''Interface: p6p1''' == | + | === '''Interface: p6p1''' === |
<div class="screen"> | <div class="screen"> | ||
Line 164: | Line 168: | ||
</div> | </div> | ||
− | == '''Interface: p6p2''' == | + | === '''Interface: p6p2''' === |
<div class="screen"> | <div class="screen"> | ||
Line 173: | Line 177: | ||
</div> | </div> | ||
− | == '''Stealth Interface Combo Setting Command''' == | + | === '''Stealth Interface Combo Setting Command''' === |
<div class="screen"> | <div class="screen"> |
Revision as of 19:43, 22 April 2013
Contents
Overview
For non-NST Pro users please use the script name: "nstipconf". The script name was changed to "nstnetcfg" post the NST 18 release. NST Pro users please perform your YUM Updates to get the latest version of the nstnetcfg script.
This page demonstrates how to setup networking with an NST server that is configured with multiple network interface adapters for performing simultaneous network computing surveillance tasks. The NST script: "nstnetcfg" command line tool was designed to make this task easy to accomplish using the underlying "network" service.
The diagram below will be used as a reference for setting up a multi-network interface adapter server using NST. The rear panel of a 1U Server is shown with NIC attachment to the network infrastructure. The network security staff for fictitious company: "TxyCorp" would like to use NST for monitoring different network segments throughout their network computing environment. In particular, they would like to monitor traffic entering and leaving their corporation, web server traffic, all client electronic business transactions and remote traffic to and from their satellite offices.
When booting up "NST Live" or after a hard disk installation, the "Network Manager" service is on by default for managing all network interfaces found on an NST system. Network Manager provides a quick and easy method for setting up networking on a system equipped with a wireless interface and uses DHCP for IPv4 Address configuration. When a system is configured with two or more wired network interfaces or requires a multi-homed network setup, the "network" service may be a better choice for setting up the network configuration.
The nstnetcfg script will help mitigate some of the error prone tasks necessary when setting up networking on a NST (Linux) system using the "network" service.
Network Interface Setup Configuration Information
In this section we will identify each network interface and how it should be setup using the 1U Server configuration illustrated in the reference diagram above. Network parameters such as the Subnet Mask, Host Name(s), Domain Name Servers, Domain Name, Gateway and Default Interface will also be identified. The table below depicts values that will be used when setting up networking for this demonstration using the nstnetcfg script.
Interface / Parameter | Configuration |
---|---|
em0 | IPv4 Address: 172.30.1.16, Network Routing Prefix: 24, Host Name: nstsurv1-mon, Gateway: 10.221.1.1 |
em1 | IPv4 Address: 10.221.5.14, Network Routing Prefix: 16, Host Name: nstsurv1, Gateway: 10.221.1.1 |
em2 | IPv4 Address: stealth |
em3 | IPv4 Address: stealth |
p2p1 | IPv4 Address: stealth |
p2p2 | IPv4 Address: stealth |
p4p1 | IPv4 Address: stealth |
p4p2 | IPv4 Address: stealth |
p6p1 | IPv4 Address: stealth |
p6p2 | IPv4 Address: stealth |
Domain Name Servers | 10.221.1.10, 10.221.1.11 |
Domain Name | txycorp.com |
Virtual Host (ssl.conf) | *.443 |
Server Name (ssl.conf) | nstsurv1.txycorp.com:443 |
Network Interface Configuration: nstnetcfg
Initialize All Network Interfaces
[root@probe ~]#
Static IPv4 Configured Interfaces
Interface: em1
[root@probe ~]#
Interface: em0
[root@probe ~]#
Stealth Confiogured Interfaces
Interface: em2
[root@probe ~]#
Interface: em3
[root@probe ~]#
Interface: p2p1
[root@probe ~]#
Interface: p2p2
[root@probe ~]#
Interface: p4p1
[root@probe ~]#
Interface: p4p2
[root@probe ~]#
Interface: p6p1
[root@probe ~]#
Interface: p6p2
[root@probe ~]#
Stealth Interface Combo Setting Command
[root@probe ~]#