NeilR_M wrote

  @LolleQ The Portal Logout Domain is intended to provide an easy way for users to log out of the portal. When they enter the specified domain, it should log out their device. You can read the functionality on the FAQ here: How to configure Portal Authentication on Omada Controller (v6.2 and above) | Omada Network Support

 

If you can provide an explanation as to what you are trying to achieve, we can see if it is supported in the controller.

  @NeilR_M, I understand the idea, let's say.
It's guest network for visitors authenticated by vouchers. Not really intrested in log-out process of users, vouchers are valid for 8h and that's more than enough.
What's really, really strange - is that the logout domain (every string in format abc.yy) is intercepted to router's LAN IP as below:

PS C:\Users\Administrator> ping log.out

Pinging log.out [10.0.0.1] with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Is it inteded bahaviour and I miss some idea or is it bug?

And what am I trying to achieve? Woykd be nice to redirect logging-out users to specified, promotional domain, for example. Not really important, but maybe some day a customer want to use such mechanism.

  @NeilR_M 

Understood, but... The controller is hosted on public IP and logout redirects to 10.0.0.1, which is LAN IP of router. No offence, but this seems to be complete nonsense, if intended. The intercept of logout domain (i.e. logout.domain) to portal address would make sense if stated in the voucher ("Wanna log out? Enter hxxp://logout.domain") and not intercepted for normal VLANS, but only for guest network.