FQDN on omada captive portal

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

FQDN on omada captive portal

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
FQDN on omada captive portal
FQDN on omada captive portal
2019-10-16 17:00:00 - last edited 2019-10-16 17:01:15
Model: EAP225  
Hardware Version: V1
Firmware Version: 2.1.0 Build 20171109 Rel. 72971

Hello All,

 

Firstly, sorry for my English ; I'm a true french people ,who doesn't speak very well other languages ! :) .

 

I am a IT technician on a company who's specialised on hosting .

 

i'm working on updating our wifi . We have for now three EAP 220 , and a omada controller on ubuntu 18.04 . 

 

On this controller , i have created 2 SSID , public and private , with two captive portal .

 

This two captive portal (one for public with voucher , and private  with radius auth only on our ldap) , are working well , but never present themselves with FQDN , only with the IP address of the controler .

 

Is there a known way to change this ?

 

The problem is that we can't use trusted certificates on those webpages, and it gives a bad image to have a security warning in a company whose job it is .

 

do not hesitate if you want more details.

 

Regards,

 

Adrien

 

 

  0      
  0      
#1
Options

Information

Helpful: 0

Views: 1013

Replies: 0

Related Articles