infobri wrote

Hello there,

 

We are having difficulty setting up a guest network with portal in our multi-site environment.

 

In fact, whatever the configuration (internal or external portal), the guests always try to contact our controller via his IP address to find out what they should do.

Unfortunately in our network configuration we are not able to route this traffic to the vlan of the controller and therefore to the controller itself.

If the guest could try to contact the controller by a hostname, we could play with the DNS and make these requests arrive via the WAN, but unfortunately despite the configuration below (see image) it is always the controller's ip which is sought by the guest.

 

 

Are we missing out on something ?
Are we screwed ? :')
Maybe an OC200 physical controller can have an IP in VLAN 1 but also one in Guest VLAN and provide the correct one to the client ?

 

Thanks !

Dear  @infobri 

The Omada EAP portal is designed to be like that. 

Thank you for your kindly feedback! I will forward this feedback to the developer team for further evaluation.