OC200 - problem with Captive Portal under VLAN

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

OC200 - problem with Captive Portal under VLAN

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OC200 - problem with Captive Portal under VLAN
OC200 - problem with Captive Portal under VLAN
2022-07-14 14:22:16 - last edited 2022-07-15 10:15:10
Model: OC200  
Hardware Version: V1
Firmware Version: 1.15.2 Build 20220323 Rel.60717

Hi everybody,

I have an Omada OC200 and two EAP225, two SSIDs (office and guest), guest network is, say, on VLAN22.

I can connect successfully on guest Wifi but now I'm trying to set a Captive Portal on that SSID but when the
client is asked to access the Captive Portal it times out because the OC200 IP is unreachable.

Following this topic https://community.tp-link.com/en/business/forum/topic/179834 I created an ACL under

"Authentication -> Access Control" with the OC200 IP and Captive Portal url, everything seems ok but the
Capitve Portal is still unreachable. I created the same ACL under "Network Security -> ACL - EAP ACL"
but then again still no luck

If I disable the Captive Portal the client can connect correctly to the guest network, so the VLANs are working.

I'm really new to Omada products so maybe I'm doing something wrong, but it seems fairly simple and I don't
know where I'm mistaking.

Please kindly advise.

 

Thanks

  0      
  0      
#1
Options
1 Accepted Solution
[Solved] Re:OC200 - problem with Captive Portal under VLAN-Solution
2022-07-15 10:15:04 - last edited 2022-07-15 10:15:10

I found the problem:

it was indeed a mistake on my part, I forgot to add a permit rule on the

firewall to make the guest wifi access the captive portal address.

Recommended Solution
  2  
  2  
#4
Options
3 Reply
Re:OC200 - problem with Captive Portal under VLAN
2022-07-14 15:29:16 - last edited 2022-07-14 15:32:30

  @zanond 

 

Please see their FAQ video here, particularly Section 4 (around 3:30 into video).

 

https://www.youtube-nocookie.com/embed/Xv5d-wYs2Yk

 

Obviously, in your case your 'departments' are Guest VLAN (where the users are) and Management VLAN (where the portal is).  You don't want to block entire subnets, but you do want to only enable access from Guest VLAN to the single IP of the OC200 in the Management VLAN.  Note that the ORDER you create the rules is important...ie create the permissive rule first, then the deny all rule second.  So first rule is 'allow access to OC200 for HTTP on Port XXXX' from Guest_VLAN, and the second rule is to DENY all traffic types to all IPs on the Management VLAN from users in Guest VLAN.

 

Note that for proper inter-VLAN ACLs you need an Omada capable switch from TPLINK..you cannot do it with just an OC200 and a router unfortunately (I learned this the hard way).

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options
Re:OC200 - problem with Captive Portal under VLAN
2022-07-15 07:17:23

  @d0ugmac1 Hi,
the link you suggested doesn't cover my situation, my network works just fine but there is a problem
accessing the Captive Portal from the Guest Wifi clients, as I said the VLANs are working correctly.

Please advice.

 

Thanks

  0  
  0  
#3
Options
[Solved] Re:OC200 - problem with Captive Portal under VLAN-Solution
2022-07-15 10:15:04 - last edited 2022-07-15 10:15:10

I found the problem:

it was indeed a mistake on my part, I forgot to add a permit rule on the

firewall to make the guest wifi access the captive portal address.

Recommended Solution
  2  
  2  
#4
Options

Information

Helpful: 0

Views: 1151

Replies: 3

Related Articles