You should be able to confirm that IEEE 802.1X is enabled during runtime. When you save IEEE 802.1X configuration changes,
immediately confirm an update of the /etc/IEEE 802.1X.conf file. The location of the file on the supplicant device filesystem is /etc/ieee8021x/wpa_supplicant_[adapter_name].conf. The settings contained in this file reflect the current values in the IEEE 802.1X Configuration view. The settings are not applied, however, until after a reboot.
When the QNX 7 network stack starts up, it checks for the configuration file. If it finds the file, the stack launches wpa_supplicant. You should be able to confirm through pidin arg that the application started with the following parameters:
/etc/ieee8021x/wpa_supplicant_en0.conf (EDGE) or /etc/ieee8021x/wpa_supplicant_dm0.conf (TITAN)
-P determines where the pid (process identifier) for the wpa_supplicant instance will be located.-i determines which interface the wpa_supplicant should use for IEEE 802.1X authentication.-D specifies which driver should be used with wpa_supplicant.-B specifies that the wpa_supplicant should be launched as a daemon process.-c specifies the configuration file to be used for wpa_supplicant.If you properly configured the wpa_supplicant, it is fairly easy to determine if it is working. If the results of ifconfig indicate that the adapter has an IP address, then wpa_supplicant is working. If you are unable to communicate to a JACE through
TCP/IP protocols, then wpa_supplicant is not properly configured.
You should also be able to determine that wpa_supplicant started from the following initialization message:
launching 802.1x supplicant for interface en0