Authentication of users

Splynx supports different ways of customers' central authentication in the network of Internet provider. It always depends on topology of ISP and technology that ISP decides to use. Access technologies are widely used and their advantages and disadvantages are described below:

  • PPPoE - easy to maintain and implement. Customer on CPE device setups username and password and all networking settings CPE receives from PPPoE NAS (Network Access Server). Also provides encryption if needed and accounting for getting statistics of usage. Had issues with MTU in past, but in last years these issues were fixed by main vendors.

  • IPoE (or DHCP) - DHCP is based on MAC address of client. Also can be linked to port of switch were customer is connected (DHCP option 82). In several vendors don't provide accounting capability (Mikrotik routers)

  • Wireless Authentication - when ISP has a wireless network, he needs to maintain access of CPE devices to his Access Points. For this purpose several wireless authentication methods are used, such as a password inside TDMA protocols or wireless access-lists

  • Hotspot - customer has to enter his username and password on the webpage before using the Internet. Many hotspot networks allow free limited access and then charge customers for addtional usage or advanced plans.

  • Static IP addressing - some ISPs don't have central management of authentication and setup static IP addresses to CPE devices. With Mikrotik RouterOS platform Splynx can manage even customers who's got static IPs in Vlan per customer scenario or plain IPv4 connection. Also Splynx can grab statistics from Mikrotik routers for such customers.

Below are manuals for different types of user authentication in Splynx ISP Framework: