DNxs wrote

Where can we take to read the description of SSH for EAP?

What description? In the User's Guide?

(Just saw your question in the other thread, yes, it's been there since beginning, but only in web UI, now also in the EAP controller).

SSH management can be easily enabled either in Management - SSH menu or in EAP controller latest version (but don't have it). Nothing more needed since it uses password authentication scheme.





Then just connect to the EAP using the username/password you did set:

yourlaptop $ ssh admin@192.168.0.254
The authenticity of host '192.168.0.254 (192.168.0.254)' can't be established.
RSA key fingerprint is f7:94:2d:1f:ae:20:35:01:38:5a:53:32:d0:91:23:7c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.254' (RSA) to the list of known hosts.
admin@192.168.0.254's password: ***********

BusyBox v1.01 (2015.06.11-11:22+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ ls
ash chmod dmesg grep login nart.out ping sh true
busybox date echo iptables-xml ls netstat ps sleep umount
cat df false kill mount pidof rm tar usleep
$


The interesting program there is /usr/bin/eap-cs, which seems to be the software communicating with EAP controller, but didn't investigate any further. It's probably easier to monitor communication between the controller and the EAP than trying to disassemble the program.

DNxs wrote

I mean a description is batches of commands, examples of scripts... which can help to manage the EAP Controller on SSH without webUI. Can we make voucher through SSH?))))))))))))))))))))

Yes, it would be helpful to have an API documentation of the eap-cs utility (or whatever is used to communicate with the EAP controller) and the device's config files, you are absolutely right! But according to the support team TP-Link won't disclose it. It's a pity, since it could help OEMs to sell more EAPs.

C:\Users\DNxs>ssh admin@127.0.0.1 -p 22

You need to use the EAP's IP address, not the localhost (127.0.0.1 is your PC). For this it is best to use a static IP for the EAP, not a dynamic IP which you have to lookup first.

Ah, I see. We are probably talking about different things. This ssh extension seems to be related to the machine running EAP controller, not the EAPs themself.

You are right, this description in the UG is very confusing, makes no sense to me (but I'm not familiar with Windows or EAP controller's security concept).

DNxs wrote

Could the EAP controller be implemented on Unix-like OS?

Technically: yes, it should be no problem for TP-Link to port it to Linux and MacOS (which is based on FreeBSD Unix).