Overview

The supplicant is a LAN port that requests access to the services that are accessed through the authenticator for wireless or wired connections.

Satyav Networks provides an IEEE 802.1x based software used in the client station.

For example laptops, personnel computers, embedded wireless devices etc.

Satyav’s Supplicant modules can be run on any wireless or wireless client station or can be integrated with any hardware or OS platform.

Satyav’s supplicant stack is currently integrated with latest EAP methods like MD5, TLS and PEAP and because of it's modular design it is easy to extent with any new EAP methods. It also supports framework for 802.11i and WEP key management.

Supplicant can be used by OEM, network devices manufactures and embedded devices. Stack is available in source as well as binary form.

Following figure shows the Satyav’s supplicant role in 802.1x based Authentication process.

Currently stack is running on Linux and can be easily portable on any operating system. It's modular design and operation specific libraries makes easy to port on any platform. Demo version as well as sample code is available on request.

Satyav’s WiSupplicant Architecture

Highlights of the stack

• Stack written in C and C++.

• Runs on Linux, Windows, capable to run on embedded environment and easily portable on any platform.

• Multi layered and structured modular design architectures.

• Configurable role and configurable debug.

• SUPPLICANT can be used as DLL, shared library or main application.

• Extensive error handling to the application.

• Test cases and Test Programs are ready to use.

• Using Satyav Network’s WiSSL as SSL library

• Operating system specific Libraries, i.e transmit, receive. timer, thread, packet management etc. are used.

802.1x feature list that stack supports

• The Port Timer state machine

• The Supplicant PAE state machine

• The Supplicant Key Transmit state machine

• The Key Receive State machine

• Re-authenticator Timer state machine

• The backend Supplicant state machine

• The controlled direction state machine

  Authentication Support

• Tested with EAP-MD5, EAP-TLS, EAP-TTLS, EAP-PEAP, EAP-MSCHAPv2, EAP-SIM and EAP-AKA..

• 802.1x based state machine implementation support.

Well Documented APIs, Debug & Test Cases

• Well documented APIs for development integration efforts, easy customizing.

• Thoroughly prepared Debug to provide extensive error handling to the application.

• Properly written test cases that are tested to give well developed product.

• Complete control over stop, restart and shutdown of SUPPLICANT.

Note :- Please hover on image to view in large size.

Adapter Status Page

Advanced Wireless Settings Page

 EAP Settings Page

802.1x Internal Settings Page

Login Page

Network Settings

User Credentials

Wireless Network Authentication

Wireless Network List

Wireless Statistics

Technical specifications of WiSupplicant

• IETF based RFC Standards

  • 802.1X 2001 Draft, backward compatible.

  • 802.1x 2004 Draft.

• EAP Methods

  • Eap Md5.

  • Eap Peap

  • Eap Mschap

  • Eap Tls

  • Eap Ttls.

  • Eap Leap

  • Eap Sim

  • Eap Aka

• Platforms

  • Standard Intel platforms.

  • Standard AMD platform.

• WiFi Network Security Features

  • WEP.

  • WPA

• Operating System

  • Supplicant supports Windows (Xp and above), Linux and all its flavours, and MacOS.

  • Supplicant support is under development RTOS like SMX, iPhone and Android.
    Graphical User Interface

  • Supplicant supports GUI for windows operating system.

  • Supplicant GUI is developed in C#.Net code.

• Network Features

  • Supplicant supports many different types of networks.

  • Supplicant supports all types of WiFi networks.

• Dedicated WiFi Hardware

  • Supplicant supports Atheros AR52xx, AR600x.

  • Supplicant supports Broadcom BCM4318.

• SSL/ TLS Libraries

  • Supplicant currently uses WiSsl library of Satyav networks.

  • Supplicant supports OpenSsl Library.

• Documentation

  • Supplicant datasheet.

  • Supplicant Test Cases.

  • Release Notes

  • User Guide

  • Design Document.

• Memory Usage

  • Supplicant source code shows 10kb memory footprint without GUI support and more as SSL and other libraries add up.

• Code Portability

  • Written in C and C++

  • Any operating system supported

  • Any hardware environment supported

  • Any dedicated device supported.