strongSwan as TNC Client¶

The following plugins must activated for strongSwan to take on the role of a TNC Client

Configuration as a TNCCS 2.0 Client with EAP-MD5 password-based authentication

./configure --prefix=/usr --sysconfdir=/etc --enable-curl
            --enable-eap-tls --enable-eap-ttls --enable-eap-identity --enable-eap-md5
            --enable-eap-tnc --enable-tnc-imc --enable-tnccs-20

/etc/strongswan.conf - strongSwan configuration file

charon {
  plugins {
    eap-tnc {
      protocol = tnccs-2.0
    }
  }
}

Configuration as a TNCCS 2.0 Client with EAP-TLS certicate-based authentication

./configure --prefix=/usr --sysconfdir=/etc --enable-curl
            --enable-eap-tls --enable-eap-ttls --enable-eap-identity --enable-eap-md5
            --enable-eap-tnc --enable-tnc-imc --enable-tnccs-20

/etc/strongswan.conf - strongSwan configuration file

charon {
  plugins {
    eap-tnc {
      protocol = tnccs-2.0
    }
  }
}

Configuration as a TNCCS 1.1 Client with EAP-TLS certicate-based authentication

./configure --prefix=/usr --sysconfdir =/etc --enable-curl
            --enable-eap-tls --enable-eap-ttls --enable-eap-identity --enable-eap-md5
            --enable-eap-tnc --enable-tnc-imc --enable-tnccs-11

/etc/strongswan.conf - strongSwan configuration file

charon {
  plugins {
    eap-tnc {
      protocol = tnccs-1.1
    }
  }
}