eurilex wrote

How to setup using one voucher that can connect to all SSID or devices.

You need to bind the same portal to all different SSIDs. Just select SSID1 and SSID2 etc. in the SSID field of the portal:

@eurilex, I think it could be a bug. Maybe @Fae could comment further on this behavior (thanks!)?

@R1D2 

R1D2 wrote

@eurilex, I think it could be a bug. Maybe @Fae could comment further on this behavior (thanks!)?

Sorry I don't think it is a bug. As far as I'm concerned, it's normal that it is required to input another voucher code to connect when switching to another SSID. It's the same on the SSIDs which are secured with the same WPA password, when switching from SSID1 to SSID2, we still need to input the WPA password to connect even if the password is the same. Maybe I'm wrong, have you met such a product that can share one voucher code between different SSIDs from different APs? If yes, may I ask what application scenario is it used for?

@eurilex 

But my only concern is when im connected to SSID1 using voucher, if im going to another area and want to connect to SSID2, its asking again for another voucher. How to setup using one voucher that can connect to all SSID or devices. 

 

May I know your application scenario? Why don't you use the same SSID for it?

@Fae, thanks for your reply.

I just was guessing b/c two or more SSIDs can be bound to the same portal, so I was under the impression that this portal is shared between SSIDs. Back in times when we did have user authentication with vouchers or self-registration in our portal software, we had common name spaces for portals, that means a voucher or self-registration of users was valid for all hotspots in the same name space even at different locations and independent of the SSIDs used by those hotspots.

However, vouchers and self-registration is seldom used in our country since the last amendment of the Telemedia Law in 2017, so most WLAN hotspots here use a No Authentication scheme nowadays.

You're right, if the voucher function is bound to a single SSID in Omada Controller intentionally, @eurilex should use the same SSID for all EAPs which should share vouchers.

@JSchnee21, anyway, I would like to know what's the intended purpose of being able to bind one portal to different SSIDs if the portal's authentication then is handled separately for each SSID, if only just to learn what can be done when a customer demands it for whatever reason. For me as a developer software should offer a mechanism, but not imply a certain policy (a basic UNIX/Linux philosophy often neglected).

Q.E.D.: It didn't take long for another TP-Link customer to request that a portal with voucher authentication be split over two separate SSIDs:

https://community.tp-link.com/en/business/forum/topic/228982