topic Web authentication users failed? in Wireless

Web authentication users failed?

rguzman.plannet — Sun, 04 Jul 2021 03:13:52 GMT

Hi,

I have a guest network and lately I have been experiencing troubles with some users.

The symptom, as I create a username and password and type'em in a laptop the authentication fields in the web authentication page don't keep the data as if I didn't type anything

WLC 4402-50

Version 7.0.98.210

Hope someone can help.

Thanks!

Re: Web authentication users failed?

Nicolas Darchis — Mon, 23 May 2011 06:35:50 GMT

What kind of OS and browser ?

Re: Web authentication users failed?

Richard Atkin — Tue, 24 May 2011 13:14:15 GMT

Are you using the WLC internal captive portal page or one hosted on a third-party device? Also, are you using any SSL Certificates and/or DNS on the Virtual Interface?

Rich

Re: Web authentication users failed?

rguzman.plannet — Wed, 25 May 2011 22:00:00 GMT

Sorry for the delay I am out of office so I can't check updates that often.

I am using internal web authentication page, and certificates crated by the WLC and no I am not using DNS.

It happens only to some users, it can work or not in the same computer depending on which user name are we typing in.

Regards!

Re: Web authentication users failed?

rguzman.plannet — Fri, 27 May 2011 17:31:38 GMT

Hello,

Here is an update of my case, I captured a debugg from a devie trying to connect to guest wlan with two different usernames and passwords. The firts didnt work but as soon as I tried another one it connected.

I was looking for some document that mentions something about "Orphan Packet", don't know what that means. I typed some comments below in the capture please notice them.

(Cisco Controller) >debug client d8:9e:3f:84:f8:aa

(Cisco Controller) >*apfMsConnTask_0: May 27 11:12:30.991: Deleting the client immediatly since WLAN is changed

*apfReceiveTask: May 27 11:12:47.960: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:47.967: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.001: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.013: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.019: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.038: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.514: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.518: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.531: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.541: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.550: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:12:48.560: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*spamReceiveTask: May 27 11:13:11.348: CCKM: Send CCKM cache entry

*apfReceiveTask: May 27 11:13:42.871: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:13:42.885: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:13:42.889: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:13:42.895: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:13:42.901: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*apfReceiveTask: May 27 11:13:42.904: d8:9e:3f:84:f8:aa Orphan Packet from 192.168.1.173 on mobile

*emWeb: May 27 11:13:43.023: d8:9e:3f:84:f8:aa Username entry (robertwireless) created for mobile <-- Here you can see when I tried with a username that does work. The loggs after that changed to the ones when I tried with the other username.

*emWeb: May 27 11:13:43.024: d8:9e:3f:84:f8:aa Setting guest session timeout for mobile d8:9e:3f:84:f8:aa to 1641958 seconds

*emWeb: May 27 11:13:43.024: d8:9e:3f:84:f8:aa Session Timeout is 1641958 - starting session timer for the mobile

*emWeb: May 27 11:13:43.024: d8:9e:3f:84:f8:aa 192.168.1.173 WEBAUTH_REQD (8) Change state to WEBAUTH_NOL3SEC (14) last state WEBAUTH_NOL3SEC (14)

*emWeb: May 27 11:13:43.024: d8:9e:3f:84:f8:aa apfMsRunStateInc

*emWeb: May 27 11:13:43.024: d8:9e:3f:84:f8:aa 192.168.1.173 WEBAUTH_NOL3SEC (14) Change state to RUN (20) last state RUN (20)

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa Session Timeout is 1641958 - starting session timer for the mobile

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa 192.168.1.173 RUN (20) Reached PLUMBFASTPATH: from line 4796

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa 192.168.1.173 RUN (20) Replacing Fast Path rule

type = Airespace AP Client

on AP 00:18:74:4b:d5:80, slot 0, interface = 1, QOS = 0

ACL Id = 255, Jumbo Frames = N

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa 192.168.1.173 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 5006 IPv6 Vlan = 17, IPv6 intf id = 8

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa 192.168.1.173 RUN (20) Successfully plumbed mobile rule (ACL ID 255)

*emWeb: May 27 11:13:43.025: d8:9e:3f:84:f8:aa Updating guest account information for user robertwireless at login.

Re: Web authentication users failed?

rguzman.plannet — Fri, 27 May 2011 17:33:50 GMT