MediaWiki - User contributions [en]

Wireless

2026-04-15T15:36:32Z

Rwh: /* Broadcom Chipset Discovery */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network;
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci | rg Network;
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Driver Installation ==
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;
[nst@nst44-mbp ~]$ sudo systemctl reboot;

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:36:19Z

Rwh: /* Broadcom Chipset Discovery */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Driver Installation ==
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;
[nst@nst44-mbp ~]$ sudo systemctl reboot;

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:35:47Z

Rwh: /* Driver Installation = */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Driver Installation ==
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;
[nst@nst44-mbp ~]$ sudo systemctl reboot;

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:35:21Z

Rwh: /* Driver Installation = */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Driver Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;
[nst@nst44-mbp ~]$ sudo systemctl reboot;

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:33:52Z

Rwh: /* Installation = */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Driver Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:33:36Z

Rwh: /* Discovery */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Broadcom Chipset Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:33:14Z

Rwh: /* Recommended */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended Driver ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:32:47Z

Rwh: /* Discovery */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Discovery ==
First determine which Broadcom Chipset you have:

Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:32:30Z

Rwh: /* Discovery */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Discovery ==
First determine which Broadcom Chipset you have:
Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:32:06Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

== Discovery ==
* First determine which Broadcom Chipset you have:
Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

== Recommended ==
* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

== Installation ===
To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T15:30:39Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* First determine which Broadcom Chipset you have:
Example: 1 (BCM4360)
[root@nst44-mbp ~]# lspci | rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Dual Band Wireless Network Adapter (rev 03)

Example: 2 (BCM43602)
[root@ccii-nst42 ~]# lspci|rg Network
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)

* BCM4360 (many 2013–2015 models) → broadcom-wl
* BCM43224 / BCM4331 etc. → broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) Use the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T13:31:52Z

Rwh:

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T13:30:47Z

Rwh: /* Broadcom Modules Descriptions */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ nmcli radio wifi on;

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T13:28:57Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

== Enable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi on;

== Disable WiFi using nmcli ==
[nst@nst44-mbp ~]$ sudo nmcli radio wifi off;

Wireless

2026-04-15T12:25:33Z

Rwh: /* Broadcom Modules Descriptions */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (Optional) — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

Wireless

2026-04-15T12:25:10Z

Rwh: /* Broadcom Modules Descriptions */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl — A metapackage that pulls in a pre-built module for the newest kernel.
* akmods — The build tool itself (and kernel-devel is required for building).

Wireless

2026-04-15T12:23:51Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

== Broadcom Modules Descriptions ==
The akmod-wl package is an akmod (Automatic Kernel Module) package from RPM Fusion (non-free repository) that provides the proprietary Broadcom wl (STA) kernel module for certain legacy Broadcom Wi-Fi chipsets.

The wl driver is Broadcom's official closed-source Linux driver for many older Broadcom wireless cards (e.g., BCM43xx series like BCM4312, BCM4322, BCM43228, BCM4331, etc.).
Unlike the open-source b43 or brcmfmac drivers in the mainline kernel (which often have limited or no support for these chips), wl offers better performance/features for unsupported hardware.
akmod-wl does not contain a pre-built module. Instead, it contains the source code and build system so that the akmods framework can automatically compile the wl.ko module for your current (and future) kernel versions whenever you install a new kernel.

These are the related packages:

* broadcom-wl — Provides the license, README, configuration files, and firmware blobs (the actual driver source is in the akmod).
* kmod-wl (optional) — A metapackage that pulls in a pre-built module for the newest kernel (if available from RPM Fusion).
* akmods — The build tool itself (and kernel-devel is required for building).

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T12:16:23Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document describes the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Next use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn off the mouse for ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for a bluetooth connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

== How To Remove (Unpair) the Magic Mouse ==
Use this command to remove the magic mouse from the bluetooth adapter:

[nst@nst44-mbp ~]$ bluetoothctl
remove A4:E9:75:06:E5:BA
quit

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:17:10Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document describes the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Next use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn off the mouse for ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for a bluetooth connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:16:27Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document describes the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Next use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn off the mouse for ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:15:38Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document describes the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Next use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:14:10Z

Rwh: /* Overview */

__TOC__

= Overview =
This document describes the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:13:55Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document shows the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with your NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:13:37Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
This document shows the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guidelines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:12:39Z

Rwh: /* Overview */

__TOC__

= Overview =
This document shows the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enabled. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:12:00Z

Rwh: /* Overview */

__TOC__

= Overview =
This document shows the steps on how to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:10:53Z

Rwh: /* Scrolling Solution */

__TOC__

= Overview =
How to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
To allow a Magic Mouse to scroll add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:09:57Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
How to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:07:02Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
How to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA
quit

* The above sequence should allow for connection. Use the following to check:
[nst@nst44-mbp ~]$ bluetoothctl info A4:E9:75:06:E5:BA
Device A4:E9:75:06:E5:BA (public)
Name: RWH Mouse2
Alias: RWH Mouse2
Class: 0x00000580 (1408)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v004Cp0269d0192

= Scrolling Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T02:04:55Z

Rwh: /* Bluetooth Connection Sequence */

__TOC__

= Overview =
How to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =
Use the following guild lines to get an Apple Magic Mouse to work with you NST system:

* Start and enable the Bluetooth service:
[nst@nst44-mbp ~]$ sudo systemctl start bluetooth.service;
[nst@nst44-mbp ~]$ sudo systemctl enable bluetooth.service;

* Use the Bluetooth Applet to scan and determine the MAC Address of the mouse (e.g., A4:E9:75:06:E5:BA)

* Use the Bluetooth Control utility: bluetoothctl for trust, pair, bond and connection.
[nst@nst44-mbp ~]$ bluetoothctl
power on
agent on
default-agent
scan on

* Now put the mouse in pairing mode (i.e., Turn of the mouse ~5sec and then back on.):
trust A4:E9:75:06:E5:BA
pair A4:E9:75:06:E5:BA
connect A4:E9:75:06:E5:BA

= Scrolling Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T01:56:28Z

Rwh: /* Bluetooth Connection Sequence */

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T01:48:55Z

Rwh:

__TOC__

= Overview =
How to configure an Apple Magic Mouse using Bluetooth with scrolling. An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Bluetooth Connection Sequence =

= Scrolling Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

HowTos

2026-04-15T01:46:48Z

Rwh:

* [[HowTo Adjust The Display Brightness On A Laptop In Console Mode Using The Command Line]]
* [[HowTo Adjust The Keyboard Backlight Brightness On A Laptop In Console Mode Using The Command Line]]
* [[HowTo Backup And Restore The Master Boot Record (MBR)]]

* [[HowTo BackupPC SSH Key Authentication Setup For rsync Transfer]]
* [[HowTo Change The LVM Volume Group Name That Includes The Root Partition]]
* [[HowTo Configure And Run A Ring Buffer Capture Session Using: "nstringbufcap"]]
* [[HowTo Configure Apache SSL For davfs, subversion, etc.]]
* [[HowTo Configure The Default Terminal Application for ssh:// For A Browser]]
* [[HowTo Create A Patch File For A RPM]]
* [[HowTo Create A GPT Disk With EFI System And exFAT Partitions Using Parted]]
* [[HowTo Curl Examples]]
* [[HowTo Fix The rngd.service]]
* [[HowTo Determine If Hardware Virtualization Is Enabled]]
* [[HowTo Disable The "relatime" Method For File "atime" Updates]]
* [[HowTo Download From The Command Line Using: "wget"]]
* [[HowTo Dual Boot NST With Windows 8.1]]
* [[HowTo Enable The Gnome Sound Applet]]
* [[HowTo Configure An Apple Magic Mouse With Scrolling]]
* [[HowTo Generate a 3D Pie Chart of nDPI Detected Protocols]]
* [[HowTo Geolocate Data Using The NST WUI]]
* [[HowTo Headless Intel NUC vPro AMT]]
* [[HowTo Install Microsoft PowerShell]]
* [[HowTo Install The MATE (GNOME 2) Desktop]]
* [[HowTo Install VirtualBox]]
* [[HowTo Keep Processes Running After Logging Out Using: "setsid"]]
* [[HowTo Limit Remote Access To "ssh" Connections]]
* [[HowTo Monitor Network Traffic]]
* [[HowTo One Liners]]
* [[HowTo Perform A Security Audit With hping3 (DoS)]]
* [[HowTo Prevent A Laptop Lid Close Suspension]]
* [[HowTo Regenerate The TLS (SSL) Certificate For The NST WUI]]
* [[HowTo Remote Connect to a Mate Desktop Session Using the Vino Server]]
* [[HowTo Resize The "root" File System Using LVM]]
* [[HowTo Quickly Get A Project Started With Subversion]]
* [[HowTo Quickly Setup A VPN Using WireGuard On NST]]
* [[HowTo Put Multiple Live Images On One USB Memory Stick]]
* [[HowTo Recreate Grub Install And The Master Boot Record (MBR) If Corrupted]]
* [[HowTo Run A Script At Boot]]
* [[OpenVAS | HowTo Setup OpenVAS]]
* [[HowTo Setup An NST System With Multiple Network Interface Adapters Using: "nstnetcfg"]]
* [[HowTo Setup Guacamole]]
* [[HowTo Setup Suricata - A Simple Live Configuration]]
* [[HowTo Share A Terminal Session Using Screen]]
* [[HowTo Shutdown NST Using A USB Flash Drive Install For Relocation]]
* [[Upgrade to NST 20|HowTo Upgrade from NST 18 to NST 20]]
* [[HowTo Upscale An Image]]
* [[HowTo Use an Android Phone as a GPSd Source]]
* [[HowTo Use A Touch Device (iPad) with NST]]
* [[HowTo Use Gmail API to send emails]]
* [[HowTo Use The NST CloudShark Upload Manager]]
* [[HowTo Use The NST Network Tools Widgets]]
* [[NST Mapping Tools | HowTo Use The NST Map Tools Widgets]]
* [[HowTo Use The NST Shell Command Console]]
* [[HowTo Use The NST WUI arp-scan Page To Quickly Locate Hosts]]
* [[HowTo Use The Scapy: Multi-Traceroute - MTR]]
* [[Console Output and Serial Terminals | HowTo Setup Console Output and Serial Terminals]]
* [[DVD_md5sum | HowTo Verify The Md5Sum On An DVD ISO]]
* [[HowTo Install NST 2.16 on an Asus Zenbook Prime]]

HowTo Enable Scrolling With An Apple Magic Mouse

2026-04-15T01:45:55Z

Rwh: Rwh moved page HowTo Enable Scrolling With An Apple Magic Mouse to HowTo Configure An Apple Magic Mouse With Scrolling: Renamed for content

#REDIRECT [[HowTo Configure An Apple Magic Mouse With Scrolling]]

HowTo Configure An Apple Magic Mouse With Scrolling

2026-04-15T01:45:55Z

Rwh: Rwh moved page HowTo Enable Scrolling With An Apple Magic Mouse to HowTo Configure An Apple Magic Mouse With Scrolling: Renamed for content

__TOC__

= Overview =
An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "'''hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40'''".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

Then rebuild the grub2 configuration file:
[root@nst42-mbp grub2]# nstboot -v --grub2;

Wireless

2026-04-15T01:39:55Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Use the following if the built-in WiFi adapter does not appear as a network interface. Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

Wireless

2026-04-15T01:38:53Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

To install the broadcom-wl driver:

[nst@nst44-mbp ~]$ sudo dnf install broadcom-wl akmod-wl kernel-devel-$(uname -r) -y;
[nst@nst44-mbp ~]$ sudo akmods --force;
[nst@nst44-mbp ~]$ sudo depmod -a;
[nst@nst44-mbp ~]$ sudo modprobe -v wl;

Reboot.

Wireless

2026-04-15T01:35:53Z

Rwh: /* Apple MacBook Pro Broadcom Wireless Adapter */

= What Wireless Cards Are Supported? =

Unfortunately, getting a wireless card to work with Linux, can be quite tricky. Often, it comes down to searching the Internet, making your best guess from bits of information, and then purchasing a card and trying it. It doesn't help that manufacturers like to change chip sets without changing model numbers.

The following lists the manufacturers of WIFI card chip sets that we have had good luck with ''working out of the box''.

* [http://www.atheros.com/ Atheros]
* [http://www.intel.com/network/connectivity/products/wireless/ Intel]

See the "[http://linux-wless.passys.nl/ Linux wireless LAN support]" web site to access a WIFI compatibility database.

= How Do I Get My Broadcom Card Working? =

Since the NST system is based off of Fedora, it comes with a kernel module that can be used to support some Broadcom WIFI cards. The kernel module is named: ''b43''. Unfortunately, it appears that the required firmware for this module is not provided by Fedora.

Instructions and more information on dealing with Broadcom cards can be found on the "[http://wireless.kernel.org/en/users/Drivers/b43 b43 and b43legacy]" page at the [http://wireless.kernel.org/ Linux Wireless] web site.

= How do I determine the manufacturer of the chip set in my WIFI card? =

The '''lspci''' command is useful in determining who manufacturers the WIFI chip set in your WIFI adapter and what version of the chip set is used. For example:

[root@cayenne ~]# lspci | grep -i network
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
[root@cayenne ~]#

The output of the above command suggests that the WIFI card is manufactured by ''Atheros Communications Inc.'' and that it has a model number of ''AR9285''. This card happens to work well in a NST system, however if it didn't, a [http://www.google.com/search?q=Atheros+AR9285+Fedora Google search on "Atheros AR9285 Fedora"] would likely provide some clues as to what would need to be done to make it work.

= Will My Wireless Card Work At Boot? =

It is unlikely that when you boot a live NST system that it will use your wireless card at boot as the default network device. In order for this to occur during a ''Console'' mode boot, all of the following must be true:

* The NST system must recognize and support your WIFI card.
* The NST system must associate the ''eth0'' interface with your WIFI card (it typically won't do this if your system has any Ethernet devices).
* There must be a wireless access point within range that has no authentication/encryption in place.

However, if you boot a live NST system to ''Desktop'' mode instead of ''Console'' mode, the '''NetworkManager''' service will be running. The '''NetworkManager''' service tries very hard to determine and establish a connection to networks. If there is a open wireless access point within range of your system, its possible that your NST system will connect to it automatically when you log in.

= How Do I Configure My Wireless Card For Network Access? =

== From The GNOME Desktop ==

If you plan on using your WIFI card as your connection to the network, it is recommended to boot your NST system to ''Desktop'' mode, log into the system using the GNOME desktop manager and use the '''NetworkManager''' applet. There will be a network icon on the top bar of your desktop you click on to work with the applet. The '''NetworkManager''' applet makes it very easy to connect to different WIFI networks and to enter in the necessary key(s) to join encrypted networks.

== From The NST WUI ==

If you are not running the '''NetworkManager''' service, you can use the NST WUI to setup a secure WPA connection. From the top menu bar on the NST WUI, select: ''Network|Wireless|WPA-PSK Setup''. This should open up a page in the NST WUI which allows you to select which interface to configure, to scan for available networks and to enter your pre-shared key.

== WIFI From The Command Line (with NetworkManager) ==

If you are using NetworkManager to manage your wireless interface, you can use the '''nmcli''' (NetworkManager Command Line utility) to connect your wireless card to an access point. It works as follows:

* Scan your system for WIFI cards
* Scan for access points
* Connect to the access point

[root@chimi ~]# nmcli device wifi rescan
[root@chimi ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
ringo-2.4 Infra 9 54 Mbit/s 100 ▂▄▆█ WPA2
* ringo-5.0 Infra 153 54 Mbit/s 100 ▂▄▆█ WPA2
-- Infra 9 54 Mbit/s 67 ▂▄▆_ WPA2
HP-Print-88-ENVY 4500 series Infra 3 54 Mbit/s 52 ▂▄__ WPA2
NETGEAR58 Infra 10 54 Mbit/s 42 ▂▄__ WPA2
ATT8u3W7d9 Infra 6 54 Mbit/s 40 ▂▄__ WPA1 WPA2
belkin.d43.guests Infra 11 54 Mbit/s 30 ▂___ --
belkin.d43 Infra 11 54 Mbit/s 30 ▂___ WPA1 WPA2
ATT9Zug2Nn Infra 4 54 Mbit/s 29 ▂___ WPA2
2WIRE201 Infra 9 54 Mbit/s 29 ▂___ WPA1 WPA2
MotoVAP_M91427SA0MS8 Infra 108 54 Mbit/s 29 ▂___ WPA2
ATT2IAK24t_guest Infra 8 54 Mbit/s 25 ▂___ WPA2
HP-Print-5A-Deskjet 2540 series Infra 3 54 Mbit/s 24 ▂___ WPA2
NETGEAR58-5G Infra 153 54 Mbit/s 19 ▂___ WPA2
[root@chimi ~]#
[root@chimi ~]# nmcli device wifi connect ringo-5.0 password WIFI_PASSWORD
Device 'wlp3s0' successfully activated with 'ff3fee57-dbb1-4c04-854a-ee3a3c4f9b75'.
[root@chimi ~]#

== WEP From The Command Line (no NetworkManager) ==

We do not recommend using WEP for accessing WIFI networks as WEP does not provide much security. However, if you need to connect your NST system to a wireless access point using WEP, you should be able to use '''NetworkManager''' if you've logged into a GNOME desktop.

If you need to access WEP from the command line, here are some dated notes from 2005 which might prove useful:

The first problem is to determine the name of the device (eth0, eth1, wlan0, etc) which Linux associates with your wireless card. After inserting your wireless card into your system, you can use the '''iwconfig''' command to determine its device name.

[root@cayenne ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn Mode:Managed Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan0mon IEEE 802.11bgn Mode:Monitor Frequency:2.472 GHz Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

[root@cayenne ~]#

The above shows that ''wlan0'' is the device name associated with a wireless card.

Once you determine the device name of your wireless card, you will need to create the appropriate configuration file under the: "''/etc/sysconfig/network-scripts''" directory. The following shows how one could create the necessary configuration for the wireless card and then restart the network drivers to enable the card.

[root@probe root]# cdnet
[root@probe network-scripts]# cp nst-eth0.dhcp ifcfg-wlan0
[root@probe network-scripts]# vim ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes

ESSID="bogus"
MODE="Managed"
RATE="auto"

:wq
[root@probe root]# cat >| keys-wlan0
KEY="FEDCBA9876543210123456789A"
^D
[root@probe root]# chmod 600 keys-wlan0
[root@probe root]# service network restart
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface wlan0: [ OK ]
[root@probe root]#

For your card, you will need to change the values assigned to the ''ESSID'' and ''KEY'' variables above. You may also need to specify something other than ''wlan0'' if the '''iwconfig''' output shows your WIFI card having a different device name.

= Will My Wireless Card Work With Kismet and Airsnort? =

Some wireless cards that work perfectly fine for general networking, won't work with ''Kismet'' or ''Airsnort''. It turns out that in order for a wireless card to be used by either of these two programs, the driver for the card needs to support ''monitor mode''. If ''monitor mode'' is not supported, then you won't be able to use programs such as ''Kismet'' or ''Airsnort''.

The best way to determine whether your WIFI card supports ''monitor mode'' or not is to setup and try using ''Kismet''. To do this:

* Select ''Network|Wireless|Kismet Server'' from the NST WUI menu bar.
* Press the ''Setup System To Run Kismet'' button.
* Press the ''Return'' button after setup completes.
* Press the ''Kismet README'' file to read up on the ''ncsource'' configuration line.
* Press the ''Edit Kismet Config'' button and check and/or adjust the ''ncsource'' parameter.
* Press the ''Save & Return'' button.
* Press the ''Start'' button to start the ''kismet_server'' service.
* Press the ''Server Log'' button and look for ''ERROR'' messages indicating that ''Kismet'' failed to use your WIFI card or failed to put your WIFI card into ''monitor mode''.

Note for a complete walk through on setting up ''Kismet'', see: [[HowTo Geolocate kismet Data]] - you can ignore the steps related to setting up a GPS as you don't have to have a GPS connected to run ''Kismet''.

= Can I Monitor And Use the Wireless Card For Networking? =

Typically you can not use a wireless card for both monitoring and networking at the same time. It is definitely not possible if you enable channel hopping while using the wireless card in monitor mode.

= iwd Replacement for wpa_supplicant with Network Manager =
[https://wiki.archlinux.org/title/Iwd iwd] is a modern replacement for [https://wiki.archlinux.org/title/Wpa_supplicant wpa_supplicant], offering advantages like a smaller codebase, faster connections, and more intuitive command-line tools. wpa_supplicant is a more traditional and long-standing daemon, while iwd ((iNet wireless daemon) is a wireless daemon for Linux written by Intel) is a newer, faster alternative developed by Intel that uses only kernel functions for security. Both can be used as a backend for connection managers like [https://wiki.archlinux.org/title/NetworkManager NetworkManager], but iwd is generally considered more efficient and user-friendly for modern use cases.

Steps for iwd replacement of wpa_supplicant for a backend wireless daemon with NetworkManager:

* Install the iwd package:
[root@nst42-mbp ~]# dnf install iwd;

* Create a NetworkManager configuration file: "'''/etc/NetworkManager/conf.d/iwd.conf'''"
[device]
# Use iwd instead of wpa_supplicant
wifi.backend=iwd

* Restart the NetworkManager Service:
[root@nst42-mbp ~]# systemctl restart NetworkManager.service;

* Check that the iwd daemon is now running:
[root@nst42-mbp ~]# ps -ef|rg -i iwd
root 894 1 0 Dec03 ? 00:00:00 /usr/libexec/iwd
root 173022 172626 0 09:50 pts/1 00:00:00 rg -i iwd

* Make sure the wpa_supplicant daemon has terminated. If not kill the process.
[root@nst42-mbp ~]# ps -ef|rg -i wpa
root 173017 172626 0 09:50 pts/1 00:00:00 rg -i wpa

= Apple MacBook Pro Broadcom Wireless Adapter =

Common chips on MacBook Pro:

* BCM4360 (many 2013–2015 models) → usually needs broadcom-wl
* BCM43224 / BCM4331 etc. → also broadcom-wl
* Newer ones (BCM43602, BCM437x, etc.) sometimes work better with the in-kernel brcmfmac driver.

Wireless

2026-04-15T01:29:22Z

Rwh: /* iwd Replacement for wpa_supplicant with Network Manager */

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:50:37Z

Rwh: /* Solution */

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:48:41Z

Rwh: /* Solution */

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:47:58Z

Rwh: /* Solution */

__TOC__

= Overview =
An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:47:37Z

Rwh: /* Solution */

__TOC__

= Overview =
An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<pre class="computerOutput">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</pre>
</div>

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:44:41Z

Rwh: /* Solution */

__TOC__

= Overview =
An Apple Magic mouse by default does not have its scrolling enable. One must add Kernel parameters to enable scrolling.

= Solution =
Add the following parameters to the "'''/etc/nst/grub2/nst_grub2_defaults'''" file: "hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40".

<div class="screen">
<div class="screenTitle">''Section:'' NST Desktop (Graphical) Boot</div>
<div class="userInput"><span class="prompt">
#
# NST Desktop (Graphical) Boot
# --- ------- ----------- ----
NST_SERIAL[idx]="false";
NST_SERIAL_DEV[idx]="ttyS0";
NST_SERIAL_BAUD[idx]="115200";
NST_TITLE[idx]="Graphical Desktop";
NST_GRUB_CMDLINE_LINUX[idx]="audit=0 systemd.unit=graphical.target hid_magicmouse.emulate_3button=0 hid_magicmouse.scroll_acceleration=1 hid_magicmouse.scroll_speed=40";
NST_GRUB_SAVEDEFAULT[idx]="true";
NST_GRAPHICAL_BOOT[idx]="true";
idx=idx+1;
</div>
</div>

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:41:38Z

Rwh:

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:36:14Z

Rwh:

__TOC__

= Overview =

HowTo Configure An Apple Magic Mouse With Scrolling

2026-03-28T18:35:39Z

Rwh: Created page with "__toc__"

__toc__

HowTos

2026-03-28T18:34:13Z

Rwh:

* [[HowTo Adjust The Display Brightness On A Laptop In Console Mode Using The Command Line]]
* [[HowTo Adjust The Keyboard Backlight Brightness On A Laptop In Console Mode Using The Command Line]]
* [[HowTo Backup And Restore The Master Boot Record (MBR)]]

* [[HowTo BackupPC SSH Key Authentication Setup For rsync Transfer]]
* [[HowTo Change The LVM Volume Group Name That Includes The Root Partition]]
* [[HowTo Configure And Run A Ring Buffer Capture Session Using: "nstringbufcap"]]
* [[HowTo Configure Apache SSL For davfs, subversion, etc.]]
* [[HowTo Configure The Default Terminal Application for ssh:// For A Browser]]
* [[HowTo Create A Patch File For A RPM]]
* [[HowTo Create A GPT Disk With EFI System And exFAT Partitions Using Parted]]
* [[HowTo Curl Examples]]
* [[HowTo Fix The rngd.service]]
* [[HowTo Determine If Hardware Virtualization Is Enabled]]
* [[HowTo Disable The "relatime" Method For File "atime" Updates]]
* [[HowTo Download From The Command Line Using: "wget"]]
* [[HowTo Dual Boot NST With Windows 8.1]]
* [[HowTo Enable The Gnome Sound Applet]]
* [[HowTo Enable Scrolling With An Apple Magic Mouse]]
* [[HowTo Generate a 3D Pie Chart of nDPI Detected Protocols]]
* [[HowTo Geolocate Data Using The NST WUI]]
* [[HowTo Headless Intel NUC vPro AMT]]
* [[HowTo Install Microsoft PowerShell]]
* [[HowTo Install The MATE (GNOME 2) Desktop]]
* [[HowTo Install VirtualBox]]
* [[HowTo Keep Processes Running After Logging Out Using: "setsid"]]
* [[HowTo Limit Remote Access To "ssh" Connections]]
* [[HowTo Monitor Network Traffic]]
* [[HowTo One Liners]]
* [[HowTo Perform A Security Audit With hping3 (DoS)]]
* [[HowTo Prevent A Laptop Lid Close Suspension]]
* [[HowTo Regenerate The TLS (SSL) Certificate For The NST WUI]]
* [[HowTo Remote Connect to a Mate Desktop Session Using the Vino Server]]
* [[HowTo Resize The "root" File System Using LVM]]
* [[HowTo Quickly Get A Project Started With Subversion]]
* [[HowTo Quickly Setup A VPN Using WireGuard On NST]]
* [[HowTo Put Multiple Live Images On One USB Memory Stick]]
* [[HowTo Recreate Grub Install And The Master Boot Record (MBR) If Corrupted]]
* [[HowTo Run A Script At Boot]]
* [[OpenVAS | HowTo Setup OpenVAS]]
* [[HowTo Setup An NST System With Multiple Network Interface Adapters Using: "nstnetcfg"]]
* [[HowTo Setup Guacamole]]
* [[HowTo Setup Suricata - A Simple Live Configuration]]
* [[HowTo Share A Terminal Session Using Screen]]
* [[HowTo Shutdown NST Using A USB Flash Drive Install For Relocation]]
* [[Upgrade to NST 20|HowTo Upgrade from NST 18 to NST 20]]
* [[HowTo Upscale An Image]]
* [[HowTo Use an Android Phone as a GPSd Source]]
* [[HowTo Use A Touch Device (iPad) with NST]]
* [[HowTo Use Gmail API to send emails]]
* [[HowTo Use The NST CloudShark Upload Manager]]
* [[HowTo Use The NST Network Tools Widgets]]
* [[NST Mapping Tools | HowTo Use The NST Map Tools Widgets]]
* [[HowTo Use The NST Shell Command Console]]
* [[HowTo Use The NST WUI arp-scan Page To Quickly Locate Hosts]]
* [[HowTo Use The Scapy: Multi-Traceroute - MTR]]
* [[Console Output and Serial Terminals | HowTo Setup Console Output and Serial Terminals]]
* [[DVD_md5sum | HowTo Verify The Md5Sum On An DVD ISO]]
* [[HowTo Install NST 2.16 on an Asus Zenbook Prime]]

HowTo Setup A Server With Multiple Network Interface Adapters Using: "nstnetcfg"

2026-03-09T15:30:44Z

Rwh: /* Hot Plug In an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro */

__TOC__
= '''Overview''' =

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: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" command line tool was designed to make this task easy to accomplish using the underlying "'''NetworkManager'''" service via the '''nmcli''' utility.

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 attachments 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. 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. They will use a combination of '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' ('''S'''witched '''P'''ort '''A'''nalyzer) ports and a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Non-Aggregational Network TAP]''' to expose network traffic on these segments.

When booting up "'''[http://sourceforge.net/projects/nst/ NST Live]'''" or after a hard disk installation, the "'''[http://projects.gnome.org/NetworkManager/ 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 that 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 "'''nstnetcfg'''" script may be a better choice for setting up the network configuration.

The '''nstnetcfg''' utility can help mitigate some of the error prone tasks necessary by scripting when setting up networking on a NST (Linux) system using the "'''NetworkManager'''" service.

[[Image:Nstnetcfgserver.png|1024px|center|A Multi-Network Interface Adapter NST Server Configuration]]

<div class="centerBlock"><div class="noteMessage">'''Note:''' The "'''Sys Admin Network'''" is an out-of-band network for the management of enterprise servers within this network infrastructure. The "'''[http://en.wikipedia.org/wiki/Out-of-band_management ILOM]'''" (Integrated Lights Out Management) network interface (i.e., "'''NetMgt'''") and the "'''Serial Console'''" device (i.e., "'''ttyS0'''") are shown for completeness and are not used by "'''nstnetcfg'''".</div></div>

= '''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 by the '''nstnetcfg''' script.

{| border="1" cellspacing="0" cellpadding="2"
! align="center" style="background-color: lightgray;" |Interface / Parameter
! align="center" style="background-color: lightgray;" |Configuration Values
! align="center" style="background-color: lightgray;" |NetworkManager<br />Service
|-
|em0
|IPv4 Address: '''172.30.1.16''', Network Routing Prefix: '''24''', Host Name: '''nstsurv1-mon''', Gateway: '''10.221.1.1'''
|managed
|-
|em1
|IPv4 Address: '''10.221.5.14''', Network Routing Prefix: '''16''', Host Name: '''nstsurv1''', Gateway: '''10.221.1.1'''
|managed
|-
|em2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|em3
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p2p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p2p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p4p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p4p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p6p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p6p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|Domain Name Servers
|'''10.221.1.10''', '''10.221.1.11'''
|N/A
|-
|Domain Name
|'''txycorp.com'''
|N/A
|-
|Virtual Host (ssl.conf)
|'''*:443'''
|N/A
|-
|Server Name (ssl.conf)
|'''nstsurv1.txycorp.com:443'''
|N/A
|-
|}

 

= '''Network Interface Configuration: nstnetcfg''' =

The NST script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" will now be used for setting up networking on this server. This script will ''enable'' the "'''NetworkManager'''" service when setting up a static '''IPv4 Address''' (''--mode ipv4''). The "'''NetworkManager'''" service will also be ''enabled'' at boot time. Use the sequence of '''nstnetcfg''' invocations below to ''serve'' as an example for setting up networking on your particular server with NST.

<div class="centerBlock"><div class="noteMessage">'''Note:''' The reader is encouraged to review the man page for "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" as reference material prior to its use. One can also use the "'''--verbose'''" output parameter for greater visibility on the progress of '''nstnetcfg''' during its configuration stages.

[[Image:Warning.png‎]] The "'''nstnetcfg'''" script should only be run on a '''Serial Console''' or a '''Desktop Terminal''' due to the fact that the "'''IPv4 Addressing'''" for this NST system will most likely change.
</div></div>

== '''Initialize All Network Interfaces''' ==

The '''nstnetcfg''' mode: "'''init'''" will put the networking setup posture in a known ''initialized'' state. The "'''NetworkManager'''" service will be ''enabled'' all network adapters and assciated configuration files set to a default initialization state with no binding layer 3 addressing. The "'''LoopBack'''" interface device is never ''removed'' and ''reset'' to the factory default state with this mode. The '''[http://en.wikipedia.org/wiki/Name_Service_Switch Name Service Switch]''' configuration file: "'''/etc/nsswitch.conf'''" will have its '''hosts''' entry set to: "'''files dns'''". It is best practice to first use this mode ''prior'' to setting up networking so that any ''lingering'' "'''NetworkManager'''" configuration files will <u>Not</u> interfere with the use of the '''nstnetcfg''' operation.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode init;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Static IPv4 Configured Interfaces''' ==

The example NST server shown above uses a "'''Multi-Home'''" configuration with network interface devices: "'''em0'''" and "'''em1'''" set with static '''IPv4 Addresses:''' '''172.30.1.16''' and '''10.221.5.14''' respectively.

=== '''Interface: em1''' ===

The "'''em1'''" interface device is network attached to the "'''TxyCorp'''" Intranet. This network provides name services and external access to the Internet. The "'''Host Name'''", "'''Domain Name'''", "'''Name Servers'''" and "'''Gateway'''" values are set accordingly. A host name entry for "'''nstsurv1'''" will be added to the '''Hosts''' file: "'''/etc/hosts'''", the system host name will be set to: "'''nstsurv1'''". A "'''16'''" network routing prefix ('''[http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR]''' - Format) will be used. The configuration for this interface is shown below.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ipv4 --interface em1 --ipv4-addr-prefix 10.221.5.14/16 --gateway 10.221.1.1 --host-name nstsurv1 --domain-name txycorp.com --name-servers "10.221.1.10,10.221.1.11";</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: em0''' ===

The "'''em0'''" network interface is connected to the "'''Security Network'''" for performing network surveillance tasks using the "'''NST WUI'''" and the large collection of NST network security applications and tools. The "'''--hosts-file-only'''" setting is used so that only the '''Hosts''' file: "'''/etc/hosts'''" will be updated with a host name entry for: "'''nstserv1-mon'''". Note that there is <u>No</u> "'''--gateway'''" parameter used with this interface because there is only one default gateway (i.e., "'''10.221.1.1'''") for this '''Multi-Home''' example configuration. It is not necessary to again set the system "'''Host Name'''", "'''Domain Name'''" and "'''Name Servers'''" values since these were specified in the configuration for network interface "'''em1'''". A "'''24'''" network routing prefix ('''[http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR]''' - Format) will be used.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ipv4 --interface em0 --ipv4-addr-prefix 172.30.1.16/24 --host-name nstsurv1-mon --hosts-file-only;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''NetworkManager Ignore Certain Devices - Unmanaged''' ==
See this reference on how to configure NetworkManager to ignore certain devices: "'''[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-networkmanager-to-ignore-certain-devices_configuring-and-managing-networking Configuring NetworkManager to ignore certain devices]'''"

== '''Stealth Configured Interfaces''' ==

The "'''Stealth'''" network interfaces (i.e., An interface in the "'''UP'''" state with <u>No</u> binding '''IPv4 Address''') will now be configured. These interfaces are strategically network attached throughout the network infrastructure for surveillance monitoring.

=== '''Interface: em2''' ===

This network interface: "'''em2'''" is used to monitor the Transmit Data: "'''TxD'''" port on a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Network TAP]''' ('''T'''est '''A'''ccess '''P'''oint) for all traffic ''leaving'' (egress) the "'''TxyCorp'''" corporation at the '''Firewall Dirty Side'''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface em2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: em3''' ===

This network interface: "'''em3'''" is used to monitor the Receive Data: "'''RxD'''" port on a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Network TAP]''' for all traffic ''entering'' (ingress) the "'''TxyCorp'''" corporation at the '''Firewall Dirty Side'''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface em3;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p2p1''' ===

This network interface: "'''p2p1'''" is used to monitor specific "'''Web Server'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' ('''S'''witched '''P'''ort '''A'''nalyzer) port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p2p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p2p2''' ===

This network interface: "'''p2p2'''" is used to monitor specific "'''Web Server'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p2p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p4p1''' ===

This '''[https://en.wikipedia.org/wiki/10-gigabit_Ethernet 10 Gigabit Ethernet]''' network interface: "'''p4p1'''" is used to monitor specific "'''Business Transaction'''" data packets on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p4p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p4p2''' ===

This '''[https://en.wikipedia.org/wiki/10-gigabit_Ethernet 10 Gigabit Ethernet]''' network interface: "'''p4p2'''" is used to monitor specific "'''Business Transaction'''" data packets on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p4p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p6p1''' ===

This network interface: "p6p1" is used to monitor specific "'''Remote Office'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p6p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p6p2''' ===

This network interface: "p6p2" is used to monitor specific "'''Remote Office'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p6p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Stealth Interface Combo Setting Command''' ===

The output below is a compact way of using a '''[https://en.wikipedia.org/wiki/Bash_(Unix_shell) Bash]''' "''for loop'' " statement to configure all "'''Stealth'''" interfaces in one command line invocation.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>for i in em2 em3 p2p1 p2p2 p4p1 p4p2 p6p1 p6p2; do nstnetcfg --mode stealth --interface ${i}; done</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Apache SSL Configuration For Proper HTTPS NST WUI Access''' ==

If the "'''IPv4 Address'''" on an NST system is changed, the '''[http://httpd.apache.org/ Apache Web Server]''' '''[http://en.wikipedia.org/wiki/Secure_Sockets_Layer SSL]''' configuration file: "'''/etc/httpd/conf.d/ssl.conf'''" needs to be modified for proper '''[http://en.wikipedia.org/wiki/HTTP_Secure HTTPS]''' ''access'' to the "'''NST WUI'''". The following "'''nstnetcfg'''" command uses the "'''ssl'''" mode to allow all hosts "'''HTTPS'''" access to the "'''NST WUI'''" using '''Server Name:''' "'''nstsurv1.txycorp.com'''". A new "'''SSL'''" certificate and key file will also be ''generated''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ssl --interface em1 --virtual-host *:443 --server-name nstsurv1.txycorp.com:443;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Using A Bash Script With "nstnetcfg"''' ==
It may be better to use a '''[http://en.wikipedia.org/wiki/Bash Bash]''' script given the numerous invocations of "'''nstnetcfg'''" with this '''NST''' network configuration setup. A good location to store your script would be in directory: "'''/etc/nst'''". This will allow one to ''easily'' make changes to your network configuration by editing the script and running it. An example script below is shown for: "'''/etc/nst/net_cfg.sh"''' using the above invocations of "'''nstnetcfg'''". One can copy and paste this script as a starter template file for your usage.

<pre class="programListing">
#!/bin/bash

#
# Script: "net_cfg.sh"

#
# Description: Helper script for setting up the configuration of network interfaces
# on Server: "nstsurv1" using: "nstnetcfg".

#
# Short Usage: "nstnetcfg"
#
# nstnetcfg [-m|--mode TEXT] [-i|--interface DEVICE]
# [-a|--ipv4-addr-prefix IPv4ADDR/PREFIX] [-g|--gateway IPv4ADDR]
# [--mac-addr MACADDR] [--host-name TEXT] [--domain-name TEXT]
# [--name-servers IPv4ADDRLIST] [--hosts-file-only [true]|false]
# [--virtual-host TEXT] [--server-name TEXT]
# [-h|--help [true]|false] [-H|--help-long [true]|false]
# [-v|--verbose [true]|false] [--version [true]|false]
#
# Available Modes: ipv4, dhcp, ssl, stealth, netmgr, rmint, init, show

#
# Uncomment to enable verbosity
#VERBOSE=" --verbose";

#
# Network Interface: Initialization
/usr/bin/nstnetcfg --mode init${VERBOSE};

#
# Network Interface: em1
/usr/bin/nstnetcfg --mode ipv4 --interface em1 --ipv4-addr-prefix 10.221.5.14/16 --gateway 10.221.1.1 \
--host-name nstsurv1 --domain-name txycorp.com --name-servers "10.221.1.10,10.221.1.11"${VERBOSE};

#
# Network Interface: em0
/usr/bin/nstnetcfg --mode ipv4 --interface em0 --ipv4-addr-prefix 172.30.1.16/24 --host-name nstsurv1-mon \
--hosts-file-only${VERBOSE};

#
# Network Interface: em2
/usr/bin/nstnetcfg --mode stealth --interface em2${VERBOSE};

#
# Network Interface: em3
/usr/bin/nstnetcfg --mode stealth --interface em3${VERBOSE};

#
# Network Interface: p2p1
/usr/bin/nstnetcfg --mode stealth --interface p2p1${VERBOSE};

#
# Network Interface: p2p2
/usr/bin/nstnetcfg --mode stealth --interface p2p2${VERBOSE};

#
# Network Interface: p4p1
/usr/bin/nstnetcfg --mode stealth --interface p4p1${VERBOSE};

#
# Network Interface: p4p2
/usr/bin/nstnetcfg --mode stealth --interface p4p2${VERBOSE};

#
# Network Interface: p6p1
/usr/bin/nstnetcfg --mode stealth --interface p6p1${VERBOSE};

#
# Network Interface: p6p2
/usr/bin/nstnetcfg --mode stealth --interface p6p2${VERBOSE};

#
# Uncomment for using a Stealth Interface Combo Setting
#for i in em2 em3 p2p1 p2p2 p4p1 p4p2 p6p1 p6p2;
# do /usr/sbin/nstnetcfg --mode stealth --interface ${i};
#done

#
# Apache SSL Configuration
/usr/bin/nstnetcfg --mode ssl --interface em1 --virtual-host *:443 --server-name nstsurv1.txycorp.com:443${VERBOSE};
</pre>

=== '''Script Invocation''' ===

Make sure the script has it's '''execute''' permissions set:

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>chmod +x "/etc/nst/net_cfg.sh";</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Execute the script:

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/etc/nst/net_cfg.sh;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''List All Installed Network Interface Devices Using: "getipaddr"''' ==

The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can be used to list all available network interface devices on an '''NST''' system.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
lo
em0
em1
em2
em3
p2p1
p2p2
p4p1
p4p2
p6p1
p6p2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''List All 'Virtual' Installed Network Interface Devices Using: "getipaddr"''' ===
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D --virtual;</div>
<pre class="computerOutput">
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''List All 'Physical' Installed Network Interface Devices Using: "getipaddr"''' ===
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D --physical;</div>
<pre class="computerOutput">
em0
em1
em2
em3
p2p1
p2p2
p4p1
p4p2
p6p1
p6p2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Renaming A Network Interface Device''' ==

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 30<br /> SVN: 11210</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to rename a '''Network Interface Device''' thus providing a predictable Network Interface Name that is stable and available after each successive system reboot. In this section we will demonstrate how to ''rename'' a network interface device from: "'''eno16777984'''" to: "'''net0'''" using the "'''nstnetcfg'''" utility. This utility's '''rename''' mode generates a '''udev''' rules file that is used by '''[http://en.wikipedia.org/wiki/Systemd systemd/udev]''' at system boot time to automatically assign the predictable, stable network interface name for local Ethernet, WLAN and/or WWAN network interfaces.

 
 
 
 

The current Network Interface Devices available are shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
eno16777984
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The current IP Address configuration:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno16777984: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:e2:38:0b brd ff:ff:ff:ff:ff:ff
inet 10.222.222.120/24 brd 10.222.222.255 scope global dynamic net0
valid_lft 75211sec preferred_lft 75211sec
inet6 fe80::20c:29ff:fee2:380b/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''nstnetcfg'''" utility will now be used to ''rename'' the network interface device from: "'''eno16777984'''" to: "'''net0'''". Notice the creation and content of the generated custom '''udev''' network rules file: "'''/etc/udev/rules.d/79-my-net-name-slot.rules'''"

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] The "'''nstnetcfg'''" script should only be run on a '''Serial Console''' or a '''Desktop Terminal''' when changing the name of the '''Primary''' Network Interface Device. Otherwise, network connectivity may be lost if remotely connected to this NST system while performing this task.
</div></div>

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] Try to use simple network device names (e.g. '''net0''', '''netfw''', '''Net_DMZ''' or '''NetRt1'''). Avoid using '''hyphen''' (''''-'''') or '''space''' (' ') characters in the new network interface device name. Instead, use the '''underscore''' (''''_'''') character or '''CamelCase''' for separation clarity in your device naming convention.
</div></div>

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] By default the NetworkManager service will randomize Wifi MAC Addresses. If this occurs using "'''nstnetcfg'''" to rename a Wifi Network Interface will fail. One can disable this Network Manager feature using the following configuration directive. Create a file in directory: "'''/etc/NetworkManager/conf.d'''" containing the configuration "'''wifi.scan-rand-mac-address=no'''" directive. Below is an example file to ''disable'' Wifi MAC Address randomizing by the NetworkManager service:

<div class="screen">
<div class="userInput"><span class="prompt">[root@E6440 ~]# </span>cat /etc/NetworkManager/conf.d/wifi-static-mac.conf</div>
<pre class="computerOutput">
[device]
wifi.scan-rand-mac-address=no
</pre>
<div class="userInput"><span class="prompt">[root@E6440 ~]# </span></div>
</div>
</div></div>

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode rename --rename net0 --interface eno16777984 --verbose;</div>
<pre class="computerOutput">

Generating a new/updated custom 'udev' network rules file: "/etc/udev/rules.d/79-my-net-name-slot.rules":
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:0c:29:e2:38:0b", NAME="net0"

Renaming Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-eno16777984" to "/etc/sysconfig/network-scripts/ifcfg-net0"

Labeling Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-net0" - NAME="net0"

The Network Interface Device rename from: "eno16777984" to "net0" will take effect on the next system reboot.

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Now perform a system reboot:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl reboot;</div>
<pre class="computerOutput">
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

After a system '''Reboot''', the "'''nstnetcfg'''" utility is now run to verify the ''generated'' '''udev''' rules file: "'''/etc/udev/rules.d/79-my-net-name-slot.rules'''" which internally uses the '''[http://linux.die.net/man/8/udevadm udevadm]''' tool.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode testudev --interface net0 --verbose;</div>
<pre class="computerOutput">
/bin/udevadm test "/sys/class/net/net0";
calling: test
version 208
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

=== trie on-disk ===
tool version: 208
file size: 5882628 bytes
header size 80 bytes
strings 1299372 bytes
nodes 4583176 bytes
load module index
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-libgphoto2.rules
IMPORT found builtin 'usb_id --export %%p', replacing /usr/lib/udev/rules.d/40-libgphoto2.rules:11
read rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/56-hpmud.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-drm.rules
read rules file: /usr/lib/udev/rules.d/60-ffado.rules
read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
read rules file: /usr/lib/udev/rules.d/60-net.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-raw.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/62-multipath.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/65-libwacom.rules
read rules file: /usr/lib/udev/rules.d/65-md-incremental.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
read rules file: /usr/lib/udev/rules.d/69-pilot-link.rules
read rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-printers.rules
read rules file: /usr/lib/udev/rules.d/70-spice-vdagentd.rules
read rules file: /usr/lib/udev/rules.d/70-touchpad-quirks.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/70-wacom.rules
read rules file: /usr/lib/udev/rules.d/71-biosdevname.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
read rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /etc/udev/rules.d/79-my-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
read rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
read rules file: /usr/lib/udev/rules.d/85-regulatory.rules
read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-tools-firmware.rules
read rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
read rules file: /usr/lib/udev/rules.d/91-drm-modeset.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
read rules file: /etc/udev/rules.d/98-kexec.rules
read rules file: /etc/udev/rules.d/99-gpsd.rules
read rules file: /usr/lib/udev/rules.d/99-qemu-guest-agent.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 32346 bytes strings
29283 strings (243715 bytes), 26259 de-duplicated (214394 bytes), 3025 trie nodes used
PROGRAM '/lib/udev/rename_device' /usr/lib/udev/rules.d/60-net.rules:1
starting '/lib/udev/rename_device'
'/lib/udev/rename_device' [2075] exit with return code 0
PROGRAM '/sbin/biosdevname --policy physical -i net0' /usr/lib/udev/rules.d/71-biosdevname.rules:22
starting '/sbin/biosdevname --policy physical -i net0'
'/sbin/biosdevname --policy physical -i net0' [2076] exit with return code 4
IMPORT builtin 'net_id' /usr/lib/udev/rules.d/75-net-description.rules:6
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/75-net-description.rules:12
NAME 'net0' /etc/udev/rules.d/79-my-net-name-slot.rules:1
RUN '/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/$name --prefix=/proc/sys/net/ipv4/neigh/$name --prefix=/proc/sys/net/ipv6/conf/$name --prefix=/proc/sys/net/ipv6/neigh/$name' /usr/lib/udev/rules.d/99-systemd.rules:52
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:15.0/0000:03:00.0/net/net0
ID_BUS=pci
ID_MM_CANDIDATE=1
ID_MODEL_FROM_DATABASE=VMXNET3 Ethernet Controller
ID_MODEL_ID=0x07b0
ID_NET_LABEL_ONBOARD=enEthernet0
ID_NET_NAME_MAC=enx000c29e2380b
ID_NET_NAME_ONBOARD=eno16777984
ID_NET_NAME_PATH=enp3s0
ID_NET_NAME_SLOT=ens160
ID_OUI_FROM_DATABASE=VMware, Inc.
ID_PCI_CLASS_FROM_DATABASE=Network controller
ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
ID_VENDOR_FROM_DATABASE=VMware
ID_VENDOR_ID=0x15ad
IFINDEX=2
INTERFACE=net0
SUBSYSTEM=net
SYSTEMD_ALIAS=/sys/subsystem/net/devices/net0
TAGS=:systemd:
USEC_INITIALIZED=78468
run: '/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/net0 --prefix=/proc/sys/net/ipv4/neigh/net0 --prefix=/proc/sys/net/ipv6/conf/net0 --prefix=/proc/sys/net/ipv6/neigh/net0'
unload module index
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

One can see that the Network Interface device has been changed to: "'''net0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
net0
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The IP Address configuration after the device rename is shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: net0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:e2:38:0b brd ff:ff:ff:ff:ff:ff
inet 10.222.222.120/24 brd 10.222.222.255 scope global dynamic net0
valid_lft 75211sec preferred_lft 75211sec
inet6 fe80::20c:29ff:fee2:380b/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Managing IPv4 Secondary Addressing''' ==
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 30<br /> SVN: 11210</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to ''Create'' and ''Delete'' (i.e., ''Manage'') '''IPv4 Secondary Addressing'''. By example we will ''Add'', ''Display'' and ''Remove'' '''IPv4 Secondary Addresses:''' "'''10.222.222.241/24''' and "'''10.222.222.242/24''' to an '''NST''' system (e.g., '''striker''') on '''IPv4 Network Interface:''' "'''lan0'''". This example is shown in the sections below.
<br />
<br />
<br />
<br />
<br />
=== '''Adding IPv4 Secondary Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''add'' "'''IPv4 Secondary Addresses'''" to an '''NST''' system.

First, the current '''IP Address''' state on '''NST''' system: "'''striker'''" is shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.111/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Next, the first '''IPv4 Secondary Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Network Interface:''' "'''lan0'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary add -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "add" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.241/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'bound' IPv4 secondary Address: "10.222.222.241/24"
to Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Next, the second '''IPv4 Secondary Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Network Interface:''' "'''lan0'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary add -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "add" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.242/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'bound' IPv4 secondary Address: "10.222.222.242/24"
to Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Finally, the '''IP Address''' state is now shown with the two (2) '''IPv4 Secondary Addresses''' added:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip a;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.111/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary noprefixroute lan0
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

=== '''List IPv4 Primary / Secondary Addresses Using: "getipaddr"''' ===
The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can also be used to display all '''IPv4 Addresses''' including '''IP Secondary Addresses''' bound to '''Network Interface: "lan0"''' in CIDR notation:

<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>getipaddr --interface lan0 --ip-secondary --ip-address-cidr --net-int-devices;</div>
<pre class="computerOutput">
lan0 10.222.222.111/24
lan0 10.222.222.241/24 secondary
lan0 10.222.222.242/24 secondary
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

=== '''Removing IPv4 Secondary Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''remove'' "'''IPv4 Secondary Addresses'''" on an '''NST''' system.

First, we remove all '''IPv4 Secondary Addresses''' bound to Network Interface: "'''lan0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary remove -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "remove" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.241/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'unbound' the IPv4 secondary Address: "10.222.222.241/24"
associated with Network Interface device: "lan0".

</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.242/24 --secondary remove -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "remove" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.242/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'unbound' the IPv4 secondary Address: "10.222.222.242/24"
associated with Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Finally we display the '''IP Address''' state on NST system: '''striker'''
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>ip a;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>
<br />
<br />

== '''Managing IPv4 Alias Addresses''' ==

<div class="centerBlock"><div class="noteMessage">[[Image:Warning.png‎]] '''IPv4 Alias Addressing''' is no longer supported by script: '''nstnetcfg''' start with '''NST 30'''.</div></div>

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5663</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to ''Create'' and ''Delete'' (i.e., ''Manage'') '''IPv4 Alias Addresses'''. By example we will ''Add'' and ''Remove'' '''IPv4 Alias Addresses:''' "'''10.222.222.241/24''' and "'''10.222.222.242/24''' to an '''NST''' system on '''IPv4 Alias Network Interfaces:''' "'''p5p1:a1'''" and "'''p5p1:a2'''" respectively. This example is shown in the sections below.

<div class="centerBlock"><div class="noteMessage">'''Note:''' You can not manage IPv4 aliases for interfaces which are under NetworkManager control (the interface must be managed by the network service). In addition, you may need to review/update your routing after adding your aliases.</div></div>

=== '''Adding IPv4 Alias Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''add'' "'''IPv4 Alias Addresses'''" to an '''NST''' system.

First, the current '''IP Address''' state is shown on our demo '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a1'''" using the '''Gateway:''' "'''10.222.222.1'''" and '''Host Name:''' "'''probe-a1'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m ipv4 -i p5p1:a1 -a 10.222.222.241/24 -g 10.222.222.1 --host-name probe-a1 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a1" for IPv4 Alias Network Interface: "p5p1:a1".

Setting the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Up' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the second '''IPv4 Alias Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a2'''" using the '''Gateway:''' "'''10.222.222.1'''" and '''Host Name:''' "'''probe-a2'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m ipv4 -i p5p1:a2 -a 10.222.222.242/24 -g 10.222.222.1 --host-name probe-a2 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a2" for IPv4 Alias Network Interface: "p5p1:a2".

Setting the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Up' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the '''IP Address''' state is now shown with the two (2) '''IPv4 Alias Addresses''' added:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary p5p1:a1
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary p5p1:a2
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The '''IPv4 Alias Addresses''' wil also be configured in the hosts file "'''/etc/hosts'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>cat /etc/hosts;</div>
<pre class="computerOutput">
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

10.222.222.10 striker.nst.net striker
10.222.222.141 probe-a1
10.222.222.142 probe-a2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

<div class="centerBlock"><div class="noteMessage">'''Note:''' A network configuration file in directory: "'''/etc/sysconfig/network-scripts'''" was created for both '''IPv4 Alias Addresses''' above (i.e., "'''/etc/sysconfig/network-scripts/ifcfg-p5p1:a1'''" and "'''/etc/sysconfig/network-scripts/ifcfg-p5p1:a2'''"). This will allow the '''IPv4 Alias Address''' configuration to survive a system reboot. </div></div>

=== '''List All Installed Network Interface Devices Including IP Alias Interfaces Using: "getipaddr"''' ===
The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can also be used to list all available network interface devices including '''IP Alias Network Interfaces''' on an '''NST''' system.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -D --ip-alias;</div>
<pre class="computerOutput">
lo
p1p1
p1p2
p5p1
p5p1:a1
p5p1:a2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Display all '''IPv4 Addresses''' including '''IP Alias Addresses''' bound to '''Network Interface: "p5p1"''' in CIDR notation:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -i p5p1 -D --ip-alias --ip-network-address-cidr;</div>
<pre class="computerOutput">
p5p1 10.222.222.10/24
p5p1:a1 10.222.222.241/24
p5p1:a2 10.222.222.242/24
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Removing IPv4 Alias Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''remove'' "'''IPv4 Alias Addresses'''" on an '''NST''' system.

First, the current '''IP Address''' state is shown on our demo '''NST''' system with configured '''IPv4 Alias Addresses''':
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary p5p1:a1
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary p5p1:a2
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a1'''" is now ''removed'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m rmint -i p5p1:a1 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a1" for IPv4 Alias Interface: "p5p1:a1"

Clean all IPv4 Address entries: "10.222.222.241" in Hosts file: "/etc/hosts".

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds:
Successfully brought 'Up' Network Interface: "p5p1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a2'''" is now ''removed'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m rmint -i p5p1:a2 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a2" for IPv4 Alias Interface: "p5p1:a2"

Clean all IPv4 Address entries: "10.222.222.242" in Hosts file: "/etc/hosts".

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds:
Successfully brought 'Up' Network Interface: "p5p1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the '''IP Address''' state is shown on our demo '''NST''' system with all '''IPv4 Alias Addresses''' ''removed'':
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" also shows that no '''IP Alias Network Interfaces''' are configured on the '''NST''' demo system.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -D --ip-alias;</div>
<pre class="computerOutput">
lo
p1p1
p1p2
p5p1
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Promiscuous Mode Control''' ==

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 22<br /> SVN: 7000</center>]]''']]

=== '''Overview''' ===
The '''Promiscuous''' state of a network interface device can be ''manually'' controlled by the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script. Promiscuous mode allows a network interface device to intercept and read each network packet that arrives in its entirety which is essential for capturing all traffic received. One can also use the systemd service: "'''promisc.service'''" for ''automatically'' setting the Promiscuous state ''''On'''' for one or more network interface devices at system boot.

<div class="centerBlock"><div class="noteMessage">'''Note:''' One may not be able to set the Promiscuous state ''''Off'''' if another network application like '''[https://wiki.wireshark.org/ wireshark]''' or '''[https://en.wikipedia.org/wiki/Tcpdump tcpdump]''' is active and in capture mode. A counter is used by each '''Kernel''' network driver module and incremented for each application that requests the Promiscuous mode to be set ''''On'''' for the network interface device. Until these applications have all set the Promiscuous state ''''Off'''', can one control the device's Promiscuous mode with the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script.</div></div>

=== '''Manual Mode''' ===
This section will demonstrate how to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode for a network interface using either the interface method or the promiscuous configuration file method.

==== '''Interface Method''' ====
The current '''Network Interface Devices''' available are shown for demonstration in this section.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
lan0
lo
netmon0
netmon1
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

How to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode of network interface: "'''netmon0'''" to the ''''On'''' state:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode promiscon -i netmon0 -v;</div>
<pre class="computerOutput">

Setting the Promiscuous state 'On' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'On':
/sbin/ip link set promisc on netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

How to to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode of network interface: "'''netmon0'''" to the ''''Off'''' state:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode promiscoff -i netmon0 -v;</div>
<pre class="computerOutput">

Setting the Promiscuous state 'Off' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'Off':
/sbin/ip link set promisc off netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

==== '''Promiscuous Configuration File Method''' ====
Alternatively, one could add the network interface: "'''netmon0'''" to the '''NST''' promiscuous configuration file: "'''/etc/nst/promisc.conf'''" using "'''nstnetcfg'''" mode: "'''promisccfg'''" and then control the '''Promiscuous''' state using the following command sequence:

First configure the network Interface: "'''netmon0'''" in the '''NST''' promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promisccfg --promisc add -i netmon0 -v;</div>
<pre class="computerOutput">

Using Promiscuous configuration operation mode: "add" for Network Interface device: "netmon0".

Adding Network Interface device: "netmon0" to the Promiscuous configuration file.

Updated Promiscuous configuration file: "/etc/nst/promisc.conf".

Content of Promiscuous configuration file: "/etc/nst/promisc.conf"
==================================================================
#
# NST: 2015
#
# Configuration file for a list Network Interface Adapters
# that can have their promiscuous mode enabled or disabled
# by the NST Script: "nstnetcfg".
#
# Typically the NST script: "nstnetcfg" modes:
# 'promiscon, promiscoff or promisccfg' use or configure this file.
# Use a space character as the delimiter when multiple interfaces
# are specificied.

#
# Example for Network Interface Adapters: netmon0 and netmon1
# PROMISCINTS="netmon1 netmon2";

PROMISCINTS="netmon0";
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Setting Promiscuous mode ''''On'''' for network interface: "'''netmon0'''" using the promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promiscon -v;</div>
<pre class="computerOutput">

Found Network Interface(s): "netmon0" in promiscuous configuration file: "/etc/nst/promisc.conf"

Setting the Promiscuous state 'On' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'On':
/sbin/ip link set promisc on netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Setting Promiscuous mode ''''Off'''' for network interface: "'''netmon0'''" using the promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promiscoff -v;</div>
<pre class="computerOutput">

Found Network Interface(s): "netmon0" in promiscuous configuration file: "/etc/nst/promisc.conf"

Setting the Promiscuous state 'Off' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'Off':
/sbin/ip link set promisc off netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Automatic At System Boot''' ===
The '''NST''' systemd "'''promisc.service'''" service can be used to ''enable'' the '''Promiscuous''' mode on one or more network interface adapters during a system boot. The content of this service unit is shown below:
<pre class="programListing" style=" word-break: break-word;">
#
# NST: 2015

[Unit]
Description=Network Interface Promiscuous Mode Control
Documentation=man:nstnetcfg(1)
Documentation=http://wiki.networksecuritytoolkit.org/nstwiki/index.php/HowTo_Setup_A_Server_With_Multiple_Network_Interface_Adapters_Using:_%22nstnetcfg%22#Promiscuous_Mode_Control
Wants=network-online.target
After=network-online.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/nstnetcfg --mode promiscon
ExecStop=/usr/bin/nstnetcfg --mode promiscoff

[Install]
WantedBy=multi-user.target
</pre>

One can see the use of the "'''nstnetcfg'''" script for ''starting'' and ''stopping'' the service. Make sure you use mode: "'''--mode promisccfg'''" with the corresponding network interface that you are interested in ''enabling'' the promiscuous mode at system boot time. Then enable the "'''promisc.service'''" service. Below is an example for network interface device: "'''netmon1'''".

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg -m promisccfg -i netmon1 --promisc add -v;</div>
<pre class="computerOutput">

Using Promiscuous configuration operation mode: "add" for Network Interface device: "netmon1".

Adding Network Interface device: "netmon1" to the Promiscuous configuration file.

Updated Promiscuous configuration file: "/etc/nst/promisc.conf".

Content of Promiscuous configuration file: "/etc/nst/promisc.conf"
==================================================================
#
# NST: 2015
#
# Configuration file for a list Network Interface Adapters
# that can have their promiscuous mode enabled or disabled
# by the NST Script: "nstnetcfg".
#
# Typically the NST script: "nstnetcfg" modes:
# 'promiscon, promiscoff or promisccfg' use or configure this file.
# Use a space character as the delimiter when multiple interfaces
# are specificied.

#
# Example for Network Interface Adapters: netmon0 and netmon1
# PROMISCINTS="netmon1 netmon2";

PROMISCINTS="netmon1";
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl enable promisc.service;</div>
<pre class="computerOutput">
Created symlink from /etc/systemd/system/multi-user.target.wants/promisc.service to /usr/lib/systemd/system/promisc.service.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl reboot;</div>
</div>

== '''Managing a 'Bonding' Network Interface''' ==
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5765</center>]]''']]In this section we will use "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" to ''create'' a ''''Bond Master'''' Network Interface device: "'''bond0'''" by aggregating 2 (two) '''NIC''' adapters" "'''p1p1'''" and "'''p1p2'''" into a single interface. Behind the scene, the Linux bonding driver is performing the actual mechanism for creating and managing the bond device.
A bond interface device may be useful when working with an "'''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Non-Aggregational Network Tap]'''". By combining the non-aggregational ports of the TAP back into a single interface allows both '''Transmit''' and '''Receive''' network traffic to be seen by a listening network analysis or monitoring application.

 

The network diagram shown below will be used for the example bonding configuration demonstrated in this section. The '''NST WUI Ntopng IPv4 Hosts''' application is performing ''surveillance monitoring'' on the firewall dirty side using the Bonded Network Interface: "'''bond0'''".

[[Image:Nstnetcfgbonding.png|1024px|center|A NST "'''nstnetcfg'''" Bonding Configuration with Monitoring]]

<div class="centerBlock"><div class="noteMessage">'''Note:''' The network traffic monitored on the [http://www.dual-comm.com/etap3105-aggregation-and-non-aggregation-tap.htm Dualcomm ETAP 3105 10/100/1000Base-T Regeneration Network TAP] Aggregational Port: "'''3'''" (NST Probe Port: "'''p5p1'''") may be equal to or less than the traffic monitored on the Bonded Network Interface: "'''bond0'''" that is created in this section. If the combined effective data rate on the "'''Slave'''" Network Interfaces: "'''p1p1'''" and "'''p1p2'''" exceeds ''1Gb/sec'', then Aggregational Port: "'''3'''" (NST Probe Port: "'''p5p1'''") will start to buffer and eventually lose packets where as the Bonded Network Interface: "'''bond0'''" will not.</div></div>

=== '''Network Interface Bond Creation''' ===
First lets show the current network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
5: p5p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:22:17 brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''p1p1'''" and "'''p1p2'''" NIC adapters connected to the non-aggregational Network TAP (Ports: "'''4'''" and "'''5'''" respectively) will now be bonded into a single interface: "'''bond0'''" using '''nstnetcfg''' mode: "'''bonding'''". The bond interface is now in "'''Stealth'''" mode since it has no binding '''IPv4 Address'''.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode bonding --interface bond0 --bonding-slave-ints p1p1,p1p2 --bonding-opts "mode=balance-rr,miimon=100" -v;</div>
<pre class="computerOutput">

Attempting to configure 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Attempting to bring 'Down' Network Interface: "p1p1".
Successfully brought 'Down' Network Interface: "p1p1".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Attempting to bring 'Down' Network Interface: "p1p2".
Successfully brought 'Down' Network Interface: "p1p2".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Setting up a 'Bonding Master' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0"
for Network Interface: "bond0".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility is now shown after the creation of the "'''bond0'''" device:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
5: p5p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:22:17 brd ff:ff:ff:ff:ff:ff
18: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link tentative dadfailed
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Notice that the network interfaces: "'''p1p1'''" and "'''p1p2'''" have the "'''SLAVE'''" flag set and the bond network interface: "'''bond0'''" has the "'''MASTER'''" flag set. Network traffic can now be monitored or captured on this new Bonded Virtual Network Interface: "'''bond0'''".

=== '''Network Interface Bond Removal''' ===
In this section we will remove the bonding network interface: "'''bond'''" using "'''nstnetcfg'''" mode: "'''rmbonding'''":

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode rmbonding --interface bond0 -v;</div>
<pre class="computerOutput">

Attempting to remove 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Removing the "Linux Bonding Driver" module.

Removing the 'Bonding Master' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0".

Removing the 'Bonding Slave' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2".

Attempting to 'Initialize' Network Interface: "p1p2" to a 'Unmanaged' state.

Attempting to bring 'Down' Bonding Slave Network Interface: "p1p2".
Successfully brought 'Down' Bonding Slave Network Interface: "p1p2".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2" for Interface: "p1p2".

Setting up an 'Unmanaged' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Removing the 'Bonding Slave' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1".

Attempting to 'Initialize' Network Interface: "p1p1" to a 'Unmanaged' state.

Attempting to bring 'Down' Bonding Slave Network Interface: "p1p1".
Successfully brought 'Down' Bonding Slave Network Interface: "p1p1".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1" for Interface: "p1p1".

Setting up an 'Unmanaged' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

=== '''Binding an IPv4 Address to a 'Bonding' Network Interface''' ===
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5765</center>]]''']]In this section we will use "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" to bind an '''IPv4 Address''' to a '''Bonded''' Network Interface. This method can also use one of the available Linux bonding driver modes to increase the ''effective'' bandwidth from the NST system to the network.

 

The network diagram shown below will be used for the example '''IPv4 Address''' binding to the 'Bonded' Network Interface: "'''bond0'''". A Quad Gigabit NIC Adapter with ports: "'''p1p1'''", "'''p1p2'''", "'''p1p3'''" and "'''p1p4'''" will be bound together to form a new 'Bonding Master' Virtual Network Interface: "'''bond0'''".

[[Image:Nstnetcfgipv4bonding.png|1024px|center| Binding an IPv4 Address to a 'Bonded' Network Interface Using "'''nstnetcfg'''"]]

==== '''Network Interface Bond Creation''' ====
First lets show the current network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.224.2.33/16 brd 10.224.255.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:52 brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:53 brd ff:ff:ff:ff:ff:ff
5: p1p3: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:54 brd ff:ff:ff:ff:ff:ff
6: p1p4: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:55 brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''p1p1'''", "'''p1p2'''", "'''p1p3'''" and "'''p1p4'''" NIC LAN ports are now ''bonded'' into a single interface: "'''bond0'''" using '''nstnetcfg''' mode: "'''bonding'''". The bond interface is now currently in "'''Stealth'''" mode with no binding '''IPv4 Address'''.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode bonding --interface bond0 --bonding-slave-ints p1p1,p1p2,p1p3,p1p4 --bonding-opts "mode=balance-tlb,miimon=100" -v;</div>
<pre class="computerOutput">

Attempting to configure 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Attempting to bring 'Down' Network Interface: "p1p1".
Successfully brought 'Down' Network Interface: "p1p1".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Attempting to bring 'Down' Network Interface: "p1p2".
Successfully brought 'Down' Network Interface: "p1p2".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Attempting to bring 'Down' Network Interface: "p1p3".
Successfully brought 'Down' Network Interface: "p1p3".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p3"
for Network Interface: "p1p3".

Attempting to bring 'Down' Network Interface: "p1p4".
Successfully brought 'Down' Network Interface: "p1p4".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p4"
for Network Interface: "p1p4".

Setting up a 'Bonding Master' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0"
for Network Interface: "bond0".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The Linux bonding driver is configured for mode: '''Adaptive Transmit Load Balancing'''. This mode creates a channel bond that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each "'''Slave'''" Interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the '''MAC Address''' of the failed receiving slave.

==== '''IPv4 Address Binding to the Bond Interface''' ====
Next the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" utility is now used to ''bind'' the IPv4 Address: "'''172.18.1.11'''" to the 'Bond Master' Virtual network Interface: "'''bond0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode ipv4 --interface bond0 -a 172.18.1.11/24 -g 10.224.1.1 --hosts-file-only --host-name striker-bond -v;</div>
<pre class="computerOutput">
Configuring a static IPv4 Address: "172.18.1.11/24" for 'Bonding Master' Network Interface: "bond0".

Attempting to bring 'Down' Bonding Master Network Interface: "bond0".
Successfully brought 'Down' Bonding Master Network Interface: "bond0".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-bond0" for Network Interface: "bond0".

Updating the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Bonding Master Network Interface: "bond0" in 5 seconds.
Successfully brought 'Up' Bonding Master Network Interface: "bond0".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the network configuration is now shown using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" utility with IPv4 Address: "'''172.18.1.11'''" bound to the 'Bonding Master' Virtual Network Interface: "'''bond0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.224.2.33/16 brd 10.222.255.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state Up group default qlen 1000
link/ether a0:36:9f:00:71:52 brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:71:53 brd ff:ff:ff:ff:ff:ff
5: p1p3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state Up group default qlen 1000
link/ether a0:36:9f:00:71:54 brd ff:ff:ff:ff:ff:ff
6: p1p4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:71:55 brd ff:ff:ff:ff:ff:ff
12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet 172.18.1.11/24 brd 172.18.1.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Hot Plug In an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro''' ==
If you hot plug in an Apple Thunderbolt Gigabit Ethernet Adapter it needs to be registered as an authorized device using the '''boltctl''' utility. '''boltctl''' is part of the bolt RPM package. If you reboot the system with the adapter plugged in, one does not have to register the device. This is handled during the system boot process.

The following is an example of hot plugging in an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro for immediate use without rebooting:

* Install the bolt package:
[root@nst42-mbp ~]# dnf install bolt;

* Plug in the adapter and list all connected devices:
[root@nst42-mbp ~]# boltctl list;
● Apple Thunderbolt to Gigabit Ethernet Adapter
├─ type: peripheral
├─ name: Thunderbolt to Gigabit Ethernet Adapter
├─ vendor: Apple, Inc.
├─ uuid: 903d9407-0200-0100-ffff-ffffffffffff
├─ generation: Thunderbolt 1
├─ status: connected
│ ├─ domain: e0eec615-0a00-0100-ffff-ffffffffffff
│ ├─ rx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ ├─ tx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ └─ authflags: none
├─ connected: Mon 09 Mar 2026 02:46:57 PM UTC
└─ stored: no

* Current Network Device list - The Gigabit Ethernet Adapter does not appear. Device: '''enp2s0f0''' is the native built in Gigabit Adapter on this MacBook Pro:
[root@nst42-mbp ~]# nmcli d;
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected UTLNET_5_0GHZ
lo loopback connected (externally) lo
enp2s0f0 ethernet unavailable --

* Now authorize the Thunderbolt Gigabit adapter with its UUID:
[root@nst42-mbp ~]# boltctl authorize 903d9407-0200-0100-ffff-ffffffffffff;
[root@nst42-mbp ~]# boltctl list;
● Apple Thunderbolt to Gigabit Ethernet Adapter
├─ type: peripheral
├─ name: Thunderbolt to Gigabit Ethernet Adapter
├─ vendor: Apple, Inc.
├─ uuid: 903d9407-0200-0100-ffff-ffffffffffff
├─ generation: Thunderbolt 1
├─ status: authorized
│ ├─ domain: e0eec615-0a00-0100-ffff-ffffffffffff
│ ├─ rx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ ├─ tx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ └─ authflags: none
├─ authorized: Mon 09 Mar 2026 02:48:26 PM UTC
├─ connected: Mon 09 Mar 2026 02:46:57 PM UTC
└─ stored: no

* The Gigabit Adapter now appears in the Device list as '''ens9''':
[root@nst42-mbp ~]# nmcli d;
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected UTLNET_5_0GHZ
lo loopback connected (externally) lo
enp2s0f0 ethernet unavailable --
ens9 ethernet unavailable --

HowTo Setup A Server With Multiple Network Interface Adapters Using: "nstnetcfg"

2026-03-09T15:30:01Z

Rwh: /* Hot Plug In an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro */

__TOC__
= '''Overview''' =

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: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" command line tool was designed to make this task easy to accomplish using the underlying "'''NetworkManager'''" service via the '''nmcli''' utility.

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 attachments 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. 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. They will use a combination of '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' ('''S'''witched '''P'''ort '''A'''nalyzer) ports and a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Non-Aggregational Network TAP]''' to expose network traffic on these segments.

When booting up "'''[http://sourceforge.net/projects/nst/ NST Live]'''" or after a hard disk installation, the "'''[http://projects.gnome.org/NetworkManager/ 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 that 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 "'''nstnetcfg'''" script may be a better choice for setting up the network configuration.

The '''nstnetcfg''' utility can help mitigate some of the error prone tasks necessary by scripting when setting up networking on a NST (Linux) system using the "'''NetworkManager'''" service.

[[Image:Nstnetcfgserver.png|1024px|center|A Multi-Network Interface Adapter NST Server Configuration]]

<div class="centerBlock"><div class="noteMessage">'''Note:''' The "'''Sys Admin Network'''" is an out-of-band network for the management of enterprise servers within this network infrastructure. The "'''[http://en.wikipedia.org/wiki/Out-of-band_management ILOM]'''" (Integrated Lights Out Management) network interface (i.e., "'''NetMgt'''") and the "'''Serial Console'''" device (i.e., "'''ttyS0'''") are shown for completeness and are not used by "'''nstnetcfg'''".</div></div>

= '''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 by the '''nstnetcfg''' script.

{| border="1" cellspacing="0" cellpadding="2"
! align="center" style="background-color: lightgray;" |Interface / Parameter
! align="center" style="background-color: lightgray;" |Configuration Values
! align="center" style="background-color: lightgray;" |NetworkManager<br />Service
|-
|em0
|IPv4 Address: '''172.30.1.16''', Network Routing Prefix: '''24''', Host Name: '''nstsurv1-mon''', Gateway: '''10.221.1.1'''
|managed
|-
|em1
|IPv4 Address: '''10.221.5.14''', Network Routing Prefix: '''16''', Host Name: '''nstsurv1''', Gateway: '''10.221.1.1'''
|managed
|-
|em2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|em3
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p2p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p2p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p4p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p4p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p6p1
|IPv4 Address: '''stealth'''
|unmanaged
|-
|p6p2
|IPv4 Address: '''stealth'''
|unmanaged
|-
|Domain Name Servers
|'''10.221.1.10''', '''10.221.1.11'''
|N/A
|-
|Domain Name
|'''txycorp.com'''
|N/A
|-
|Virtual Host (ssl.conf)
|'''*:443'''
|N/A
|-
|Server Name (ssl.conf)
|'''nstsurv1.txycorp.com:443'''
|N/A
|-
|}

 

= '''Network Interface Configuration: nstnetcfg''' =

The NST script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" will now be used for setting up networking on this server. This script will ''enable'' the "'''NetworkManager'''" service when setting up a static '''IPv4 Address''' (''--mode ipv4''). The "'''NetworkManager'''" service will also be ''enabled'' at boot time. Use the sequence of '''nstnetcfg''' invocations below to ''serve'' as an example for setting up networking on your particular server with NST.

<div class="centerBlock"><div class="noteMessage">'''Note:''' The reader is encouraged to review the man page for "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" as reference material prior to its use. One can also use the "'''--verbose'''" output parameter for greater visibility on the progress of '''nstnetcfg''' during its configuration stages.

[[Image:Warning.png‎]] The "'''nstnetcfg'''" script should only be run on a '''Serial Console''' or a '''Desktop Terminal''' due to the fact that the "'''IPv4 Addressing'''" for this NST system will most likely change.
</div></div>

== '''Initialize All Network Interfaces''' ==

The '''nstnetcfg''' mode: "'''init'''" will put the networking setup posture in a known ''initialized'' state. The "'''NetworkManager'''" service will be ''enabled'' all network adapters and assciated configuration files set to a default initialization state with no binding layer 3 addressing. The "'''LoopBack'''" interface device is never ''removed'' and ''reset'' to the factory default state with this mode. The '''[http://en.wikipedia.org/wiki/Name_Service_Switch Name Service Switch]''' configuration file: "'''/etc/nsswitch.conf'''" will have its '''hosts''' entry set to: "'''files dns'''". It is best practice to first use this mode ''prior'' to setting up networking so that any ''lingering'' "'''NetworkManager'''" configuration files will <u>Not</u> interfere with the use of the '''nstnetcfg''' operation.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode init;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Static IPv4 Configured Interfaces''' ==

The example NST server shown above uses a "'''Multi-Home'''" configuration with network interface devices: "'''em0'''" and "'''em1'''" set with static '''IPv4 Addresses:''' '''172.30.1.16''' and '''10.221.5.14''' respectively.

=== '''Interface: em1''' ===

The "'''em1'''" interface device is network attached to the "'''TxyCorp'''" Intranet. This network provides name services and external access to the Internet. The "'''Host Name'''", "'''Domain Name'''", "'''Name Servers'''" and "'''Gateway'''" values are set accordingly. A host name entry for "'''nstsurv1'''" will be added to the '''Hosts''' file: "'''/etc/hosts'''", the system host name will be set to: "'''nstsurv1'''". A "'''16'''" network routing prefix ('''[http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR]''' - Format) will be used. The configuration for this interface is shown below.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ipv4 --interface em1 --ipv4-addr-prefix 10.221.5.14/16 --gateway 10.221.1.1 --host-name nstsurv1 --domain-name txycorp.com --name-servers "10.221.1.10,10.221.1.11";</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: em0''' ===

The "'''em0'''" network interface is connected to the "'''Security Network'''" for performing network surveillance tasks using the "'''NST WUI'''" and the large collection of NST network security applications and tools. The "'''--hosts-file-only'''" setting is used so that only the '''Hosts''' file: "'''/etc/hosts'''" will be updated with a host name entry for: "'''nstserv1-mon'''". Note that there is <u>No</u> "'''--gateway'''" parameter used with this interface because there is only one default gateway (i.e., "'''10.221.1.1'''") for this '''Multi-Home''' example configuration. It is not necessary to again set the system "'''Host Name'''", "'''Domain Name'''" and "'''Name Servers'''" values since these were specified in the configuration for network interface "'''em1'''". A "'''24'''" network routing prefix ('''[http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR]''' - Format) will be used.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ipv4 --interface em0 --ipv4-addr-prefix 172.30.1.16/24 --host-name nstsurv1-mon --hosts-file-only;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''NetworkManager Ignore Certain Devices - Unmanaged''' ==
See this reference on how to configure NetworkManager to ignore certain devices: "'''[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-networkmanager-to-ignore-certain-devices_configuring-and-managing-networking Configuring NetworkManager to ignore certain devices]'''"

== '''Stealth Configured Interfaces''' ==

The "'''Stealth'''" network interfaces (i.e., An interface in the "'''UP'''" state with <u>No</u> binding '''IPv4 Address''') will now be configured. These interfaces are strategically network attached throughout the network infrastructure for surveillance monitoring.

=== '''Interface: em2''' ===

This network interface: "'''em2'''" is used to monitor the Transmit Data: "'''TxD'''" port on a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Network TAP]''' ('''T'''est '''A'''ccess '''P'''oint) for all traffic ''leaving'' (egress) the "'''TxyCorp'''" corporation at the '''Firewall Dirty Side'''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface em2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: em3''' ===

This network interface: "'''em3'''" is used to monitor the Receive Data: "'''RxD'''" port on a '''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Network TAP]''' for all traffic ''entering'' (ingress) the "'''TxyCorp'''" corporation at the '''Firewall Dirty Side'''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface em3;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p2p1''' ===

This network interface: "'''p2p1'''" is used to monitor specific "'''Web Server'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' ('''S'''witched '''P'''ort '''A'''nalyzer) port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p2p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p2p2''' ===

This network interface: "'''p2p2'''" is used to monitor specific "'''Web Server'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p2p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p4p1''' ===

This '''[https://en.wikipedia.org/wiki/10-gigabit_Ethernet 10 Gigabit Ethernet]''' network interface: "'''p4p1'''" is used to monitor specific "'''Business Transaction'''" data packets on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p4p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p4p2''' ===

This '''[https://en.wikipedia.org/wiki/10-gigabit_Ethernet 10 Gigabit Ethernet]''' network interface: "'''p4p2'''" is used to monitor specific "'''Business Transaction'''" data packets on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p4p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p6p1''' ===

This network interface: "p6p1" is used to monitor specific "'''Remote Office'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p6p1;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Interface: p6p2''' ===

This network interface: "p6p2" is used to monitor specific "'''Remote Office'''" traffic on a '''[http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml#backinfo SPAN]''' port.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode stealth --interface p6p2;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Stealth Interface Combo Setting Command''' ===

The output below is a compact way of using a '''[https://en.wikipedia.org/wiki/Bash_(Unix_shell) Bash]''' "''for loop'' " statement to configure all "'''Stealth'''" interfaces in one command line invocation.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>for i in em2 em3 p2p1 p2p2 p4p1 p4p2 p6p1 p6p2; do nstnetcfg --mode stealth --interface ${i}; done</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Apache SSL Configuration For Proper HTTPS NST WUI Access''' ==

If the "'''IPv4 Address'''" on an NST system is changed, the '''[http://httpd.apache.org/ Apache Web Server]''' '''[http://en.wikipedia.org/wiki/Secure_Sockets_Layer SSL]''' configuration file: "'''/etc/httpd/conf.d/ssl.conf'''" needs to be modified for proper '''[http://en.wikipedia.org/wiki/HTTP_Secure HTTPS]''' ''access'' to the "'''NST WUI'''". The following "'''nstnetcfg'''" command uses the "'''ssl'''" mode to allow all hosts "'''HTTPS'''" access to the "'''NST WUI'''" using '''Server Name:''' "'''nstsurv1.txycorp.com'''". A new "'''SSL'''" certificate and key file will also be ''generated''.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode ssl --interface em1 --virtual-host *:443 --server-name nstsurv1.txycorp.com:443;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Using A Bash Script With "nstnetcfg"''' ==
It may be better to use a '''[http://en.wikipedia.org/wiki/Bash Bash]''' script given the numerous invocations of "'''nstnetcfg'''" with this '''NST''' network configuration setup. A good location to store your script would be in directory: "'''/etc/nst'''". This will allow one to ''easily'' make changes to your network configuration by editing the script and running it. An example script below is shown for: "'''/etc/nst/net_cfg.sh"''' using the above invocations of "'''nstnetcfg'''". One can copy and paste this script as a starter template file for your usage.

<pre class="programListing">
#!/bin/bash

#
# Script: "net_cfg.sh"

#
# Description: Helper script for setting up the configuration of network interfaces
# on Server: "nstsurv1" using: "nstnetcfg".

#
# Short Usage: "nstnetcfg"
#
# nstnetcfg [-m|--mode TEXT] [-i|--interface DEVICE]
# [-a|--ipv4-addr-prefix IPv4ADDR/PREFIX] [-g|--gateway IPv4ADDR]
# [--mac-addr MACADDR] [--host-name TEXT] [--domain-name TEXT]
# [--name-servers IPv4ADDRLIST] [--hosts-file-only [true]|false]
# [--virtual-host TEXT] [--server-name TEXT]
# [-h|--help [true]|false] [-H|--help-long [true]|false]
# [-v|--verbose [true]|false] [--version [true]|false]
#
# Available Modes: ipv4, dhcp, ssl, stealth, netmgr, rmint, init, show

#
# Uncomment to enable verbosity
#VERBOSE=" --verbose";

#
# Network Interface: Initialization
/usr/bin/nstnetcfg --mode init${VERBOSE};

#
# Network Interface: em1
/usr/bin/nstnetcfg --mode ipv4 --interface em1 --ipv4-addr-prefix 10.221.5.14/16 --gateway 10.221.1.1 \
--host-name nstsurv1 --domain-name txycorp.com --name-servers "10.221.1.10,10.221.1.11"${VERBOSE};

#
# Network Interface: em0
/usr/bin/nstnetcfg --mode ipv4 --interface em0 --ipv4-addr-prefix 172.30.1.16/24 --host-name nstsurv1-mon \
--hosts-file-only${VERBOSE};

#
# Network Interface: em2
/usr/bin/nstnetcfg --mode stealth --interface em2${VERBOSE};

#
# Network Interface: em3
/usr/bin/nstnetcfg --mode stealth --interface em3${VERBOSE};

#
# Network Interface: p2p1
/usr/bin/nstnetcfg --mode stealth --interface p2p1${VERBOSE};

#
# Network Interface: p2p2
/usr/bin/nstnetcfg --mode stealth --interface p2p2${VERBOSE};

#
# Network Interface: p4p1
/usr/bin/nstnetcfg --mode stealth --interface p4p1${VERBOSE};

#
# Network Interface: p4p2
/usr/bin/nstnetcfg --mode stealth --interface p4p2${VERBOSE};

#
# Network Interface: p6p1
/usr/bin/nstnetcfg --mode stealth --interface p6p1${VERBOSE};

#
# Network Interface: p6p2
/usr/bin/nstnetcfg --mode stealth --interface p6p2${VERBOSE};

#
# Uncomment for using a Stealth Interface Combo Setting
#for i in em2 em3 p2p1 p2p2 p4p1 p4p2 p6p1 p6p2;
# do /usr/sbin/nstnetcfg --mode stealth --interface ${i};
#done

#
# Apache SSL Configuration
/usr/bin/nstnetcfg --mode ssl --interface em1 --virtual-host *:443 --server-name nstsurv1.txycorp.com:443${VERBOSE};
</pre>

=== '''Script Invocation''' ===

Make sure the script has it's '''execute''' permissions set:

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>chmod +x "/etc/nst/net_cfg.sh";</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Execute the script:

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/etc/nst/net_cfg.sh;</div>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''List All Installed Network Interface Devices Using: "getipaddr"''' ==

The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can be used to list all available network interface devices on an '''NST''' system.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
lo
em0
em1
em2
em3
p2p1
p2p2
p4p1
p4p2
p6p1
p6p2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''List All 'Virtual' Installed Network Interface Devices Using: "getipaddr"''' ===
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D --virtual;</div>
<pre class="computerOutput">
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''List All 'Physical' Installed Network Interface Devices Using: "getipaddr"''' ===
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D --physical;</div>
<pre class="computerOutput">
em0
em1
em2
em3
p2p1
p2p2
p4p1
p4p2
p6p1
p6p2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Renaming A Network Interface Device''' ==

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 30<br /> SVN: 11210</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to rename a '''Network Interface Device''' thus providing a predictable Network Interface Name that is stable and available after each successive system reboot. In this section we will demonstrate how to ''rename'' a network interface device from: "'''eno16777984'''" to: "'''net0'''" using the "'''nstnetcfg'''" utility. This utility's '''rename''' mode generates a '''udev''' rules file that is used by '''[http://en.wikipedia.org/wiki/Systemd systemd/udev]''' at system boot time to automatically assign the predictable, stable network interface name for local Ethernet, WLAN and/or WWAN network interfaces.

 
 
 
 

The current Network Interface Devices available are shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
eno16777984
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The current IP Address configuration:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno16777984: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:e2:38:0b brd ff:ff:ff:ff:ff:ff
inet 10.222.222.120/24 brd 10.222.222.255 scope global dynamic net0
valid_lft 75211sec preferred_lft 75211sec
inet6 fe80::20c:29ff:fee2:380b/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''nstnetcfg'''" utility will now be used to ''rename'' the network interface device from: "'''eno16777984'''" to: "'''net0'''". Notice the creation and content of the generated custom '''udev''' network rules file: "'''/etc/udev/rules.d/79-my-net-name-slot.rules'''"

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] The "'''nstnetcfg'''" script should only be run on a '''Serial Console''' or a '''Desktop Terminal''' when changing the name of the '''Primary''' Network Interface Device. Otherwise, network connectivity may be lost if remotely connected to this NST system while performing this task.
</div></div>

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] Try to use simple network device names (e.g. '''net0''', '''netfw''', '''Net_DMZ''' or '''NetRt1'''). Avoid using '''hyphen''' (''''-'''') or '''space''' (' ') characters in the new network interface device name. Instead, use the '''underscore''' (''''_'''') character or '''CamelCase''' for separation clarity in your device naming convention.
</div></div>

<div class="centerBlock"><div class="noteMessage">
[[Image:Warning.png‎]] By default the NetworkManager service will randomize Wifi MAC Addresses. If this occurs using "'''nstnetcfg'''" to rename a Wifi Network Interface will fail. One can disable this Network Manager feature using the following configuration directive. Create a file in directory: "'''/etc/NetworkManager/conf.d'''" containing the configuration "'''wifi.scan-rand-mac-address=no'''" directive. Below is an example file to ''disable'' Wifi MAC Address randomizing by the NetworkManager service:

<div class="screen">
<div class="userInput"><span class="prompt">[root@E6440 ~]# </span>cat /etc/NetworkManager/conf.d/wifi-static-mac.conf</div>
<pre class="computerOutput">
[device]
wifi.scan-rand-mac-address=no
</pre>
<div class="userInput"><span class="prompt">[root@E6440 ~]# </span></div>
</div>
</div></div>

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode rename --rename net0 --interface eno16777984 --verbose;</div>
<pre class="computerOutput">

Generating a new/updated custom 'udev' network rules file: "/etc/udev/rules.d/79-my-net-name-slot.rules":
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:0c:29:e2:38:0b", NAME="net0"

Renaming Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-eno16777984" to "/etc/sysconfig/network-scripts/ifcfg-net0"

Labeling Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-net0" - NAME="net0"

The Network Interface Device rename from: "eno16777984" to "net0" will take effect on the next system reboot.

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Now perform a system reboot:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl reboot;</div>
<pre class="computerOutput">
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

After a system '''Reboot''', the "'''nstnetcfg'''" utility is now run to verify the ''generated'' '''udev''' rules file: "'''/etc/udev/rules.d/79-my-net-name-slot.rules'''" which internally uses the '''[http://linux.die.net/man/8/udevadm udevadm]''' tool.

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode testudev --interface net0 --verbose;</div>
<pre class="computerOutput">
/bin/udevadm test "/sys/class/net/net0";
calling: test
version 208
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

=== trie on-disk ===
tool version: 208
file size: 5882628 bytes
header size 80 bytes
strings 1299372 bytes
nodes 4583176 bytes
load module index
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-libgphoto2.rules
IMPORT found builtin 'usb_id --export %%p', replacing /usr/lib/udev/rules.d/40-libgphoto2.rules:11
read rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/56-hpmud.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-drm.rules
read rules file: /usr/lib/udev/rules.d/60-ffado.rules
read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
read rules file: /usr/lib/udev/rules.d/60-net.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-raw.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/62-multipath.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/65-libwacom.rules
read rules file: /usr/lib/udev/rules.d/65-md-incremental.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
read rules file: /usr/lib/udev/rules.d/69-pilot-link.rules
read rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-printers.rules
read rules file: /usr/lib/udev/rules.d/70-spice-vdagentd.rules
read rules file: /usr/lib/udev/rules.d/70-touchpad-quirks.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/70-wacom.rules
read rules file: /usr/lib/udev/rules.d/71-biosdevname.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
read rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules
read rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
read rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /etc/udev/rules.d/79-my-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
read rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
read rules file: /usr/lib/udev/rules.d/85-regulatory.rules
read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-tools-firmware.rules
read rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
read rules file: /usr/lib/udev/rules.d/91-drm-modeset.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
read rules file: /etc/udev/rules.d/98-kexec.rules
read rules file: /etc/udev/rules.d/99-gpsd.rules
read rules file: /usr/lib/udev/rules.d/99-qemu-guest-agent.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 32346 bytes strings
29283 strings (243715 bytes), 26259 de-duplicated (214394 bytes), 3025 trie nodes used
PROGRAM '/lib/udev/rename_device' /usr/lib/udev/rules.d/60-net.rules:1
starting '/lib/udev/rename_device'
'/lib/udev/rename_device' [2075] exit with return code 0
PROGRAM '/sbin/biosdevname --policy physical -i net0' /usr/lib/udev/rules.d/71-biosdevname.rules:22
starting '/sbin/biosdevname --policy physical -i net0'
'/sbin/biosdevname --policy physical -i net0' [2076] exit with return code 4
IMPORT builtin 'net_id' /usr/lib/udev/rules.d/75-net-description.rules:6
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/75-net-description.rules:12
NAME 'net0' /etc/udev/rules.d/79-my-net-name-slot.rules:1
RUN '/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/$name --prefix=/proc/sys/net/ipv4/neigh/$name --prefix=/proc/sys/net/ipv6/conf/$name --prefix=/proc/sys/net/ipv6/neigh/$name' /usr/lib/udev/rules.d/99-systemd.rules:52
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:15.0/0000:03:00.0/net/net0
ID_BUS=pci
ID_MM_CANDIDATE=1
ID_MODEL_FROM_DATABASE=VMXNET3 Ethernet Controller
ID_MODEL_ID=0x07b0
ID_NET_LABEL_ONBOARD=enEthernet0
ID_NET_NAME_MAC=enx000c29e2380b
ID_NET_NAME_ONBOARD=eno16777984
ID_NET_NAME_PATH=enp3s0
ID_NET_NAME_SLOT=ens160
ID_OUI_FROM_DATABASE=VMware, Inc.
ID_PCI_CLASS_FROM_DATABASE=Network controller
ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
ID_VENDOR_FROM_DATABASE=VMware
ID_VENDOR_ID=0x15ad
IFINDEX=2
INTERFACE=net0
SUBSYSTEM=net
SYSTEMD_ALIAS=/sys/subsystem/net/devices/net0
TAGS=:systemd:
USEC_INITIALIZED=78468
run: '/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/net0 --prefix=/proc/sys/net/ipv4/neigh/net0 --prefix=/proc/sys/net/ipv6/conf/net0 --prefix=/proc/sys/net/ipv6/neigh/net0'
unload module index
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

One can see that the Network Interface device has been changed to: "'''net0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
net0
lo
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The IP Address configuration after the device rename is shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: net0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:e2:38:0b brd ff:ff:ff:ff:ff:ff
inet 10.222.222.120/24 brd 10.222.222.255 scope global dynamic net0
valid_lft 75211sec preferred_lft 75211sec
inet6 fe80::20c:29ff:fee2:380b/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

== '''Managing IPv4 Secondary Addressing''' ==
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 30<br /> SVN: 11210</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to ''Create'' and ''Delete'' (i.e., ''Manage'') '''IPv4 Secondary Addressing'''. By example we will ''Add'', ''Display'' and ''Remove'' '''IPv4 Secondary Addresses:''' "'''10.222.222.241/24''' and "'''10.222.222.242/24''' to an '''NST''' system (e.g., '''striker''') on '''IPv4 Network Interface:''' "'''lan0'''". This example is shown in the sections below.
<br />
<br />
<br />
<br />
<br />
=== '''Adding IPv4 Secondary Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''add'' "'''IPv4 Secondary Addresses'''" to an '''NST''' system.

First, the current '''IP Address''' state on '''NST''' system: "'''striker'''" is shown:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.111/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Next, the first '''IPv4 Secondary Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Network Interface:''' "'''lan0'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary add -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "add" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.241/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'bound' IPv4 secondary Address: "10.222.222.241/24"
to Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Next, the second '''IPv4 Secondary Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Network Interface:''' "'''lan0'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary add -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "add" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.242/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'bound' IPv4 secondary Address: "10.222.222.242/24"
to Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Finally, the '''IP Address''' state is now shown with the two (2) '''IPv4 Secondary Addresses''' added:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip a;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.111/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary noprefixroute lan0
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

=== '''List IPv4 Primary / Secondary Addresses Using: "getipaddr"''' ===
The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can also be used to display all '''IPv4 Addresses''' including '''IP Secondary Addresses''' bound to '''Network Interface: "lan0"''' in CIDR notation:

<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>getipaddr --interface lan0 --ip-secondary --ip-address-cidr --net-int-devices;</div>
<pre class="computerOutput">
lan0 10.222.222.111/24
lan0 10.222.222.241/24 secondary
lan0 10.222.222.242/24 secondary
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

=== '''Removing IPv4 Secondary Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''remove'' "'''IPv4 Secondary Addresses'''" on an '''NST''' system.

First, we remove all '''IPv4 Secondary Addresses''' bound to Network Interface: "'''lan0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.241/24 --secondary remove -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "remove" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.241/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'unbound' the IPv4 secondary Address: "10.222.222.241/24"
associated with Network Interface device: "lan0".

</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span>nstnetcfg -m secondary -i lan0 -a 10.222.222.242/24 --secondary remove -v;</div>
<pre class="computerOutput">

Using IPv4 secondary Address binding operation mode: "remove" with
Network Interface device: "lan0" for IPv4 Address: "10.222.222.242/24".

Attempting to 'connect' device: "lan0" using nmcli.
Device 'lan0' successfully activated with 'ed61d84c-2f87-4cba-bb2a-42bbd7c7b998'.

Successfully 'unbound' the IPv4 secondary Address: "10.222.222.242/24"
associated with Network Interface device: "lan0".
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>

Finally we display the '''IP Address''' state on NST system: '''striker'''
<div class="screen">
<div class="userInput"><span class="prompt">[root@striker ~]# </span>ip a;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global noprefixroute lan0
valid_lft forever preferred_lft forever
inet6 fe80::94cd:ea04:55fe:ee9a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: netmon0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: netmon1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@striker ~]# </span></div>
</div>
<br />
<br />

== '''Managing IPv4 Alias Addresses''' ==

<div class="centerBlock"><div class="noteMessage">[[Image:Warning.png‎]] '''IPv4 Alias Addressing''' is no longer supported by script: '''nstnetcfg''' start with '''NST 30'''.</div></div>

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5663</center>]]''']]The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" can also be used to ''Create'' and ''Delete'' (i.e., ''Manage'') '''IPv4 Alias Addresses'''. By example we will ''Add'' and ''Remove'' '''IPv4 Alias Addresses:''' "'''10.222.222.241/24''' and "'''10.222.222.242/24''' to an '''NST''' system on '''IPv4 Alias Network Interfaces:''' "'''p5p1:a1'''" and "'''p5p1:a2'''" respectively. This example is shown in the sections below.

<div class="centerBlock"><div class="noteMessage">'''Note:''' You can not manage IPv4 aliases for interfaces which are under NetworkManager control (the interface must be managed by the network service). In addition, you may need to review/update your routing after adding your aliases.</div></div>

=== '''Adding IPv4 Alias Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''add'' "'''IPv4 Alias Addresses'''" to an '''NST''' system.

First, the current '''IP Address''' state is shown on our demo '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a1'''" using the '''Gateway:''' "'''10.222.222.1'''" and '''Host Name:''' "'''probe-a1'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m ipv4 -i p5p1:a1 -a 10.222.222.241/24 -g 10.222.222.1 --host-name probe-a1 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a1" for IPv4 Alias Network Interface: "p5p1:a1".

Setting the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Up' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the second '''IPv4 Alias Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a2'''" using the '''Gateway:''' "'''10.222.222.1'''" and '''Host Name:''' "'''probe-a2'''" is now ''added'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m ipv4 -i p5p1:a2 -a 10.222.222.242/24 -g 10.222.222.1 --host-name probe-a2 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a2" for IPv4 Alias Network Interface: "p5p1:a2".

Setting the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Up' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the '''IP Address''' state is now shown with the two (2) '''IPv4 Alias Addresses''' added:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary p5p1:a1
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary p5p1:a2
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The '''IPv4 Alias Addresses''' wil also be configured in the hosts file "'''/etc/hosts'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>cat /etc/hosts;</div>
<pre class="computerOutput">
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

10.222.222.10 striker.nst.net striker
10.222.222.141 probe-a1
10.222.222.142 probe-a2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

<div class="centerBlock"><div class="noteMessage">'''Note:''' A network configuration file in directory: "'''/etc/sysconfig/network-scripts'''" was created for both '''IPv4 Alias Addresses''' above (i.e., "'''/etc/sysconfig/network-scripts/ifcfg-p5p1:a1'''" and "'''/etc/sysconfig/network-scripts/ifcfg-p5p1:a2'''"). This will allow the '''IPv4 Alias Address''' configuration to survive a system reboot. </div></div>

=== '''List All Installed Network Interface Devices Including IP Alias Interfaces Using: "getipaddr"''' ===
The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" can also be used to list all available network interface devices including '''IP Alias Network Interfaces''' on an '''NST''' system.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -D --ip-alias;</div>
<pre class="computerOutput">
lo
p1p1
p1p2
p5p1
p5p1:a1
p5p1:a2
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Display all '''IPv4 Addresses''' including '''IP Alias Addresses''' bound to '''Network Interface: "p5p1"''' in CIDR notation:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -i p5p1 -D --ip-alias --ip-network-address-cidr;</div>
<pre class="computerOutput">
p5p1 10.222.222.10/24
p5p1:a1 10.222.222.241/24
p5p1:a2 10.222.222.242/24
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Removing IPv4 Alias Addresses''' ===
In this section we will show how the '''nstnetcfg''' script can be used to ''remove'' "'''IPv4 Alias Addresses'''" on an '''NST''' system.

First, the current '''IP Address''' state is shown on our demo '''NST''' system with configured '''IPv4 Alias Addresses''':
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet 10.222.222.241/24 brd 10.222.222.255 scope global secondary p5p1:a1
valid_lft forever preferred_lft forever
inet 10.222.222.242/24 brd 10.222.222.255 scope global secondary p5p1:a2
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.241/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a1'''" is now ''removed'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m rmint -i p5p1:a1 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a1".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a1" for IPv4 Alias Interface: "p5p1:a1"

Clean all IPv4 Address entries: "10.222.222.241" in Hosts file: "/etc/hosts".

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds:
Successfully brought 'Up' Network Interface: "p5p1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Next, the first '''IPv4 Alias Address:''' "'''10.222.222.242/24'''" bound to '''IPv4 Alias Network Interface:''' "'''p5p1:a2'''" is now ''removed'' to the '''NST''' system:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m rmint -i p5p1:a2 -v;</div>
<pre class="computerOutput">

Attempting to bring 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".
Successfully brought 'Down' Network Interface: "p5p1" for IPv4 Alias Interface: "p5p1:a2".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p5p1:a2" for IPv4 Alias Interface: "p5p1:a2"

Clean all IPv4 Address entries: "10.222.222.242" in Hosts file: "/etc/hosts".

Attempting to bring 'Up' Network Interface: "p5p1" in 5 seconds:
Successfully brought 'Up' Network Interface: "p5p1".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the '''IP Address''' state is shown on our demo '''NST''' system with all '''IPv4 Alias Addresses''' ''removed'':
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global p5p1
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
4: p1p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The '''NST''' script: "'''[http://nst.sourceforge.net/nst/docs/scripts/getipaddr.html getipaddr]'''" also shows that no '''IP Alias Network Interfaces''' are configured on the '''NST''' demo system.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>getipaddr -D --ip-alias;</div>
<pre class="computerOutput">
lo
p1p1
p1p2
p5p1
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Promiscuous Mode Control''' ==

[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 22<br /> SVN: 7000</center>]]''']]

=== '''Overview''' ===
The '''Promiscuous''' state of a network interface device can be ''manually'' controlled by the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script. Promiscuous mode allows a network interface device to intercept and read each network packet that arrives in its entirety which is essential for capturing all traffic received. One can also use the systemd service: "'''promisc.service'''" for ''automatically'' setting the Promiscuous state ''''On'''' for one or more network interface devices at system boot.

<div class="centerBlock"><div class="noteMessage">'''Note:''' One may not be able to set the Promiscuous state ''''Off'''' if another network application like '''[https://wiki.wireshark.org/ wireshark]''' or '''[https://en.wikipedia.org/wiki/Tcpdump tcpdump]''' is active and in capture mode. A counter is used by each '''Kernel''' network driver module and incremented for each application that requests the Promiscuous mode to be set ''''On'''' for the network interface device. Until these applications have all set the Promiscuous state ''''Off'''', can one control the device's Promiscuous mode with the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script.</div></div>

=== '''Manual Mode''' ===
This section will demonstrate how to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode for a network interface using either the interface method or the promiscuous configuration file method.

==== '''Interface Method''' ====
The current '''Network Interface Devices''' available are shown for demonstration in this section.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/getipaddr -D;</div>
<pre class="computerOutput">
lan0
lo
netmon0
netmon1
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

How to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode of network interface: "'''netmon0'''" to the ''''On'''' state:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode promiscon -i netmon0 -v;</div>
<pre class="computerOutput">

Setting the Promiscuous state 'On' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'On':
/sbin/ip link set promisc on netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

How to to use the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" script to ''manually'' set the '''Promiscuous''' mode of network interface: "'''netmon0'''" to the ''''Off'''' state:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg --mode promiscoff -i netmon0 -v;</div>
<pre class="computerOutput">

Setting the Promiscuous state 'Off' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'Off':
/sbin/ip link set promisc off netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

==== '''Promiscuous Configuration File Method''' ====
Alternatively, one could add the network interface: "'''netmon0'''" to the '''NST''' promiscuous configuration file: "'''/etc/nst/promisc.conf'''" using "'''nstnetcfg'''" mode: "'''promisccfg'''" and then control the '''Promiscuous''' state using the following command sequence:

First configure the network Interface: "'''netmon0'''" in the '''NST''' promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promisccfg --promisc add -i netmon0 -v;</div>
<pre class="computerOutput">

Using Promiscuous configuration operation mode: "add" for Network Interface device: "netmon0".

Adding Network Interface device: "netmon0" to the Promiscuous configuration file.

Updated Promiscuous configuration file: "/etc/nst/promisc.conf".

Content of Promiscuous configuration file: "/etc/nst/promisc.conf"
==================================================================
#
# NST: 2015
#
# Configuration file for a list Network Interface Adapters
# that can have their promiscuous mode enabled or disabled
# by the NST Script: "nstnetcfg".
#
# Typically the NST script: "nstnetcfg" modes:
# 'promiscon, promiscoff or promisccfg' use or configure this file.
# Use a space character as the delimiter when multiple interfaces
# are specificied.

#
# Example for Network Interface Adapters: netmon0 and netmon1
# PROMISCINTS="netmon1 netmon2";

PROMISCINTS="netmon0";
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Setting Promiscuous mode ''''On'''' for network interface: "'''netmon0'''" using the promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promiscon -v;</div>
<pre class="computerOutput">

Found Network Interface(s): "netmon0" in promiscuous configuration file: "/etc/nst/promisc.conf"

Setting the Promiscuous state 'On' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'On':
/sbin/ip link set promisc on netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Setting Promiscuous mode ''''Off'''' for network interface: "'''netmon0'''" using the promiscuous configuration file: "'''/etc/nst/promisc.conf'''"
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>nstnetcfg -m promiscoff -v;</div>
<pre class="computerOutput">

Found Network Interface(s): "netmon0" in promiscuous configuration file: "/etc/nst/promisc.conf"

Setting the Promiscuous state 'Off' for Network Interface: "netmon0".

First make sure the Network Interface: "netmon0" is up:
/sbin/ip link set up netmon0;

Next set the Promiscuous state: 'Off':
/sbin/ip link set promisc off netmon0;
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

=== '''Automatic At System Boot''' ===
The '''NST''' systemd "'''promisc.service'''" service can be used to ''enable'' the '''Promiscuous''' mode on one or more network interface adapters during a system boot. The content of this service unit is shown below:
<pre class="programListing" style=" word-break: break-word;">
#
# NST: 2015

[Unit]
Description=Network Interface Promiscuous Mode Control
Documentation=man:nstnetcfg(1)
Documentation=http://wiki.networksecuritytoolkit.org/nstwiki/index.php/HowTo_Setup_A_Server_With_Multiple_Network_Interface_Adapters_Using:_%22nstnetcfg%22#Promiscuous_Mode_Control
Wants=network-online.target
After=network-online.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/nstnetcfg --mode promiscon
ExecStop=/usr/bin/nstnetcfg --mode promiscoff

[Install]
WantedBy=multi-user.target
</pre>

One can see the use of the "'''nstnetcfg'''" script for ''starting'' and ''stopping'' the service. Make sure you use mode: "'''--mode promisccfg'''" with the corresponding network interface that you are interested in ''enabling'' the promiscuous mode at system boot time. Then enable the "'''promisc.service'''" service. Below is an example for network interface device: "'''netmon1'''".

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg -m promisccfg -i netmon1 --promisc add -v;</div>
<pre class="computerOutput">

Using Promiscuous configuration operation mode: "add" for Network Interface device: "netmon1".

Adding Network Interface device: "netmon1" to the Promiscuous configuration file.

Updated Promiscuous configuration file: "/etc/nst/promisc.conf".

Content of Promiscuous configuration file: "/etc/nst/promisc.conf"
==================================================================
#
# NST: 2015
#
# Configuration file for a list Network Interface Adapters
# that can have their promiscuous mode enabled or disabled
# by the NST Script: "nstnetcfg".
#
# Typically the NST script: "nstnetcfg" modes:
# 'promiscon, promiscoff or promisccfg' use or configure this file.
# Use a space character as the delimiter when multiple interfaces
# are specificied.

#
# Example for Network Interface Adapters: netmon0 and netmon1
# PROMISCINTS="netmon1 netmon2";

PROMISCINTS="netmon1";
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl enable promisc.service;</div>
<pre class="computerOutput">
Created symlink from /etc/systemd/system/multi-user.target.wants/promisc.service to /usr/lib/systemd/system/promisc.service.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/systemctl reboot;</div>
</div>

== '''Managing a 'Bonding' Network Interface''' ==
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5765</center>]]''']]In this section we will use "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" to ''create'' a ''''Bond Master'''' Network Interface device: "'''bond0'''" by aggregating 2 (two) '''NIC''' adapters" "'''p1p1'''" and "'''p1p2'''" into a single interface. Behind the scene, the Linux bonding driver is performing the actual mechanism for creating and managing the bond device.
A bond interface device may be useful when working with an "'''[http://www.networksecuritytoolkit.org/nstpro/order/dualcomm-singletap-nst-combo.html#usecase4 Non-Aggregational Network Tap]'''". By combining the non-aggregational ports of the TAP back into a single interface allows both '''Transmit''' and '''Receive''' network traffic to be seen by a listening network analysis or monitoring application.

 

The network diagram shown below will be used for the example bonding configuration demonstrated in this section. The '''NST WUI Ntopng IPv4 Hosts''' application is performing ''surveillance monitoring'' on the firewall dirty side using the Bonded Network Interface: "'''bond0'''".

[[Image:Nstnetcfgbonding.png|1024px|center|A NST "'''nstnetcfg'''" Bonding Configuration with Monitoring]]

<div class="centerBlock"><div class="noteMessage">'''Note:''' The network traffic monitored on the [http://www.dual-comm.com/etap3105-aggregation-and-non-aggregation-tap.htm Dualcomm ETAP 3105 10/100/1000Base-T Regeneration Network TAP] Aggregational Port: "'''3'''" (NST Probe Port: "'''p5p1'''") may be equal to or less than the traffic monitored on the Bonded Network Interface: "'''bond0'''" that is created in this section. If the combined effective data rate on the "'''Slave'''" Network Interfaces: "'''p1p1'''" and "'''p1p2'''" exceeds ''1Gb/sec'', then Aggregational Port: "'''3'''" (NST Probe Port: "'''p5p1'''") will start to buffer and eventually lose packets where as the Bonded Network Interface: "'''bond0'''" will not.</div></div>

=== '''Network Interface Bond Creation''' ===
First lets show the current network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:69:6b brd ff:ff:ff:ff:ff:ff
5: p5p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:22:17 brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''p1p1'''" and "'''p1p2'''" NIC adapters connected to the non-aggregational Network TAP (Ports: "'''4'''" and "'''5'''" respectively) will now be bonded into a single interface: "'''bond0'''" using '''nstnetcfg''' mode: "'''bonding'''". The bond interface is now in "'''Stealth'''" mode since it has no binding '''IPv4 Address'''.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode bonding --interface bond0 --bonding-slave-ints p1p1,p1p2 --bonding-opts "mode=balance-rr,miimon=100" -v;</div>
<pre class="computerOutput">

Attempting to configure 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Attempting to bring 'Down' Network Interface: "p1p1".
Successfully brought 'Down' Network Interface: "p1p1".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Attempting to bring 'Down' Network Interface: "p1p2".
Successfully brought 'Down' Network Interface: "p1p2".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Setting up a 'Bonding Master' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0"
for Network Interface: "bond0".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility is now shown after the creation of the "'''bond0'''" device:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.222.222.10/24 brd 10.222.222.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
5: p5p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:22:17 brd ff:ff:ff:ff:ff:ff
18: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet6 fe80::a236:9fff:fe00:696a/64 scope link tentative dadfailed
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Notice that the network interfaces: "'''p1p1'''" and "'''p1p2'''" have the "'''SLAVE'''" flag set and the bond network interface: "'''bond0'''" has the "'''MASTER'''" flag set. Network traffic can now be monitored or captured on this new Bonded Virtual Network Interface: "'''bond0'''".

=== '''Network Interface Bond Removal''' ===
In this section we will remove the bonding network interface: "'''bond'''" using "'''nstnetcfg'''" mode: "'''rmbonding'''":

<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode rmbonding --interface bond0 -v;</div>
<pre class="computerOutput">

Attempting to remove 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Removing the "Linux Bonding Driver" module.

Removing the 'Bonding Master' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0".

Removing the 'Bonding Slave' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2".

Attempting to 'Initialize' Network Interface: "p1p2" to a 'Unmanaged' state.

Attempting to bring 'Down' Bonding Slave Network Interface: "p1p2".
Successfully brought 'Down' Bonding Slave Network Interface: "p1p2".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2" for Interface: "p1p2".

Setting up an 'Unmanaged' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Removing the 'Bonding Slave' Network Interface configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1".

Attempting to 'Initialize' Network Interface: "p1p1" to a 'Unmanaged' state.

Attempting to bring 'Down' Bonding Slave Network Interface: "p1p1".
Successfully brought 'Down' Bonding Slave Network Interface: "p1p1".

Removing the previous Network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1" for Interface: "p1p1".

Setting up an 'Unmanaged' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

 

=== '''Binding an IPv4 Address to a 'Bonding' Network Interface''' ===
[[File:Thunderbolt.png|frame|left|'''[[Feature Release Symbol | <center>NST 20<br /> SVN: 5765</center>]]''']]In this section we will use "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" to bind an '''IPv4 Address''' to a '''Bonded''' Network Interface. This method can also use one of the available Linux bonding driver modes to increase the ''effective'' bandwidth from the NST system to the network.

 

The network diagram shown below will be used for the example '''IPv4 Address''' binding to the 'Bonded' Network Interface: "'''bond0'''". A Quad Gigabit NIC Adapter with ports: "'''p1p1'''", "'''p1p2'''", "'''p1p3'''" and "'''p1p4'''" will be bound together to form a new 'Bonding Master' Virtual Network Interface: "'''bond0'''".

[[Image:Nstnetcfgipv4bonding.png|1024px|center| Binding an IPv4 Address to a 'Bonded' Network Interface Using "'''nstnetcfg'''"]]

==== '''Network Interface Bond Creation''' ====
First lets show the current network configuration using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" network utility:
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,PROMISC,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.224.2.33/16 brd 10.224.255.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:52 brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:53 brd ff:ff:ff:ff:ff:ff
5: p1p3: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:54 brd ff:ff:ff:ff:ff:ff
6: p1p4: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a0:36:9f:00:71:55 brd ff:ff:ff:ff:ff:ff
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The "'''p1p1'''", "'''p1p2'''", "'''p1p3'''" and "'''p1p4'''" NIC LAN ports are now ''bonded'' into a single interface: "'''bond0'''" using '''nstnetcfg''' mode: "'''bonding'''". The bond interface is now currently in "'''Stealth'''" mode with no binding '''IPv4 Address'''.
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode bonding --interface bond0 --bonding-slave-ints p1p1,p1p2,p1p3,p1p4 --bonding-opts "mode=balance-tlb,miimon=100" -v;</div>
<pre class="computerOutput">

Attempting to configure 'Bonding Master' Network Interface: "bond0".

Stopping the "network" service.

Attempting to bring 'Down' Network Interface: "p1p1".
Successfully brought 'Down' Network Interface: "p1p1".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p1"
for Network Interface: "p1p1".

Attempting to bring 'Down' Network Interface: "p1p2".
Successfully brought 'Down' Network Interface: "p1p2".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p2"
for Network Interface: "p1p2".

Attempting to bring 'Down' Network Interface: "p1p3".
Successfully brought 'Down' Network Interface: "p1p3".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p3"
for Network Interface: "p1p3".

Attempting to bring 'Down' Network Interface: "p1p4".
Successfully brought 'Down' Network Interface: "p1p4".

Setting up a 'Bonding Slave' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-p1p4"
for Network Interface: "p1p4".

Setting up a 'Bonding Master' network configuration file: "/etc/sysconfig/network-scripts/ifcfg-bond0"
for Network Interface: "bond0".

Starting up the "network" service.

Enabling the "network" service at system boot time.
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

The Linux bonding driver is configured for mode: '''Adaptive Transmit Load Balancing'''. This mode creates a channel bond that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each "'''Slave'''" Interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the '''MAC Address''' of the failed receiving slave.

==== '''IPv4 Address Binding to the Bond Interface''' ====
Next the "'''[http://nst.sourceforge.net/nst/docs/scripts/nstnetcfg.html nstnetcfg]'''" utility is now used to ''bind'' the IPv4 Address: "'''172.18.1.11'''" to the 'Bond Master' Virtual network Interface: "'''bond0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/bin/nstnetcfg --mode ipv4 --interface bond0 -a 172.18.1.11/24 -g 10.224.1.1 --hosts-file-only --host-name striker-bond -v;</div>
<pre class="computerOutput">
Configuring a static IPv4 Address: "172.18.1.11/24" for 'Bonding Master' Network Interface: "bond0".

Attempting to bring 'Down' Bonding Master Network Interface: "bond0".
Successfully brought 'Down' Bonding Master Network Interface: "bond0".

Setting up the 'Static IPv4 Address' network configuration
file: "/etc/sysconfig/network-scripts/ifcfg-bond0" for Network Interface: "bond0".

Updating the hosts file: "/etc/hosts" with the IPv4 Address & Host Name.

The "network" service is already running, skip trying to 'start'.

Enabling the "network" service at system boot time.

Attempting to bring 'Up' Bonding Master Network Interface: "bond0" in 5 seconds.
Successfully brought 'Up' Bonding Master Network Interface: "bond0".

</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

Finally, the network configuration is now shown using the "'''[http://www.policyrouting.org/iproute2.doc.html ip]'''" utility with IPv4 Address: "'''172.18.1.11'''" bound to the 'Bonding Master' Virtual Network Interface: "'''bond0'''":
<div class="screen">
<div class="userInput"><span class="prompt">[root@probe ~]# </span>/usr/sbin/ip addr show;</div>
<pre class="computerOutput">
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 30:85:a9:44:7e:37 brd ff:ff:ff:ff:ff:ff
inet 10.224.2.33/16 brd 10.222.255.255 scope global eno0
valid_lft forever preferred_lft forever
inet6 fe80::3285:a9ff:fe44:7e37/64 scope link
valid_lft forever preferred_lft forever
3: p1p1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state Up group default qlen 1000
link/ether a0:36:9f:00:71:52 brd ff:ff:ff:ff:ff:ff
4: p1p2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:71:53 brd ff:ff:ff:ff:ff:ff
5: p1p3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state Up group default qlen 1000
link/ether a0:36:9f:00:71:54 brd ff:ff:ff:ff:ff:ff
6: p1p4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether a0:36:9f:00:71:55 brd ff:ff:ff:ff:ff:ff
12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether a0:36:9f:00:69:6a brd ff:ff:ff:ff:ff:ff
inet 172.18.1.11/24 brd 172.18.1.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::a236:9fff:fe00:696a/64 scope link
valid_lft forever preferred_lft forever
</pre>
<div class="userInput"><span class="prompt">[root@probe ~]# </span></div>
</div>

== '''Hot Plug In an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro''' ==
If you hot plug in an Apple Thunderbolt Gigabit Ethernet Adapter it needs to be registered as an authorized device using the '''boltctl''' utility. '''boltctl''' is part of the bolt RPM package. If you reboot the system with the adapter plugged in, one does not have to register the device. This is handled during the system boot process.

The following is an example of hot plugging in an Apple Thunderbolt Gigabit Ethernet Adapter on a MacBook Pro for immediate use without rebooting:

* Install the bolt package:
[root@nst42-mbp ~]# dnf install bolt;

* Plug in the adapter and list all connected devices:
[root@nst42-mbp ~]# boltctl list;
● Apple Thunderbolt to Gigabit Ethernet Adapter
├─ type: peripheral
├─ name: Thunderbolt to Gigabit Ethernet Adapter
├─ vendor: Apple, Inc.
├─ uuid: 903d9407-0200-0100-ffff-ffffffffffff
├─ generation: Thunderbolt 1
├─ status: connected
│ ├─ domain: e0eec615-0a00-0100-ffff-ffffffffffff
│ ├─ rx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ ├─ tx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ └─ authflags: none
├─ connected: Mon 09 Mar 2026 02:46:57 PM UTC
└─ stored: no

* Current Network Device list - The Gigabit Ethernet Adapter does not appear. Device: '''enp2s0f0''' is the native built in Gigabit Adapter on this MacBook Pro:
[root@nst42-mbp ~]# nmcli d;
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected UTLNET_5_0GHZ
lo loopback connected (externally) lo
enp2s0f0 ethernet unavailable --

* Now authorize the Thunderbolt Gigabit adapter with its UUID:
[root@nst42-mbp ~]# boltctl authorize 903d9407-0200-0100-ffff-ffffffffffff;
[root@nst42-mbp ~]# boltctl list;
● Apple Thunderbolt to Gigabit Ethernet Adapter
├─ type: peripheral
├─ name: Thunderbolt to Gigabit Ethernet Adapter
├─ vendor: Apple, Inc.
├─ uuid: 903d9407-0200-0100-ffff-ffffffffffff
├─ generation: Thunderbolt 1
├─ status: authorized
│ ├─ domain: e0eec615-0a00-0100-ffff-ffffffffffff
│ ├─ rx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ ├─ tx speed: 10 Gb/s = 1 lanes * 10 Gb/s
│ └─ authflags: none
├─ authorized: Mon 09 Mar 2026 02:48:26 PM UTC
├─ connected: Mon 09 Mar 2026 02:46:57 PM UTC
└─ stored: no

* Now the Gigabit Adapter appears in the Device list as '''ens9''':
[root@nst42-mbp ~]# nmcli d;
DEVICE TYPE STATE CONNECTION
wlp3s0 wifi connected UTLNET_5_0GHZ
lo loopback connected (externally) lo
enp2s0f0 ethernet unavailable --
ens9 ethernet unavailable --