Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WAP312 - Captive Portal does not work with VLAN tagged LAN

Hi there,

I need some help, maybe someone have already had the same or similar issue.

 

I have bought a Cisco WAP321 recently to build up a WLAN with captive Portal functionality.

 

Here MY Setup:

  • LAN
  1. Untagged VLAN: disabled
  2. Management VLAN ID: 50
  3. Static IP: 192.168.50.201
  • Wireless
    • VAP No. 0: 
      • VLAN ID = 50
      • SSID Name = MGMT
    • VAP No. 1:
      • VLAN ID = 20
      • SSID Name = Guest
  • Captive Portal
    • VAP 1 = Captive Portal instance wiz_cp_inst1 (created via the Setup)

 

Problem:

When connecting a Laptop (MacBook) to the Guest WLAN an ip address will be assigned by the DHCP Server correctly, but opening a webpage fails, the browser starts to load but stucks after a short while.

 

 

When changing the config to:

  • LAN
  1. Untagged VLAN: enabled
  2. Management VLAN ID: 1
  3. Static IP: 192.168.50.201
  • Wireless
    • VAP No. 0: 
      • VLAN ID = 50
      • SSID Name = MGMT
    • VAP No. 1:
      • VLAN ID = 1
      • SSID Name = Guest
  • Captive Portal
    • VAP 1 = Captive Portal instance wiz_cp_inst1 (created via the Setup)

 

Result:

Once connected to the guest WLAN an ip address will be assigned by the DHCP Server correctly AND the browser is being opened automatically with the captive Portal Login page.

 

Does anybody know what's wrong here?

Hope someone can support me here soon as i have to install the WLAN soon.

 

Many thanks in advance

Dirk

4 REPLIES
New Member

Hi,I have the same problem

Hi,

I have the same problem with new WAP371, firmware 1.0.1.5.

Captive portal works only on vap-s on vlan1 that is untagged.

 

New Member

OH NOOOOOOO, i just bought a

OH NOOOOOOO, i just bought a WAP371 yesterday. FUCK.

New Member

Hey d.martincic, i think i

Hey d.martincic,

 

i think i found a solution here. :-)

You have to associate the cp instance to VAP0 (usually your management WLAN) also.

See attachment, without association CaptivePortal didn't work for Guest VLAN, but it starts working after adding it.

Stupid config, but Cisco might have another logic.

Hope that will solve your issue also.

 

Bye

Dirk

New Member

Dirk, Thank You,this strange

Dirk, Thank You,

this strange solution works also for me.

 

Bye,

Danilo

255
Views
0
Helpful
4
Replies