RADIUSdesk

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
user_guide:md_on_lede_https [2016/11/17 15:41] – [Actions] adminuser_guide:md_on_lede_https [2016/11/17 16:13] (current) – [Requirements] admin
Line 9: Line 9:
   * A server with a public IP Address and FQDN having NGINX configured with a signed certificate by a known Certificate Authority (CA)   * A server with a public IP Address and FQDN having NGINX configured with a signed certificate by a known Certificate Authority (CA)
   * A LEDE build environment as stipulated in the page's parent document.   * A LEDE build environment as stipulated in the page's parent document.
-  * In our example we use here we have a server with a FQDN of 01.radiusdeskhosted.com+  * In our example we use here we have a server with a FQDN of 01.wifi-dashboard.com
   * We followed the standard instructions from LetsEncrypt to obtain a certificate for NGINX. (https://letsencrypt.org/)   * We followed the standard instructions from LetsEncrypt to obtain a certificate for NGINX. (https://letsencrypt.org/)
  
Line 57: Line 57:
 ==== redirssl ==== ==== redirssl ====
   * **redirssl** tells CoovaChilli to also listen on port 443 for incoming traffic.   * **redirssl** tells CoovaChilli to also listen on port 443 for incoming traffic.
-  * If Coova is listening on port 443 it will answer as if it is the onter side of the conversation. e.g. it will pretend to be https://www.youtube.com. \ +  * If Coova is listening on port 443 it will answer as if it is the other side of the conversation. e.g. it will pretend to be https://www.youtube.com. \ 
-  * Most browsers however are working in such a way as to check the certificate it got during the https transaction. If this certificate is not the same as that for which site it wants to go to it usually have a rediect to the login page mechanism.+  * Most browsers however are working in such a way as to check the certificate it got during the https transaction. If this certificate is not the same as that for which site it wants to go to it usually have a redirect to the login page mechanism.
   * Alternatively it will just stop with a message saying it thinks there is a man in the middle.   * Alternatively it will just stop with a message saying it thinks there is a man in the middle.
   * This is because in our case it expected Youtube's certificate but got WiFi-Dashboard instead.   * This is because in our case it expected Youtube's certificate but got WiFi-Dashboard instead.