Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-02-06 Thread Fabrice Durand via PacketFence-users
Hello Tom, sorry, this is a really busy period. What we can try to find the issue is to put the log in debug, since it looks that is on the portal that you have the issue we can try it first. So in conf/log.conf.d/httpd.portal.conf , replace INFO per TRACE (2nd line) and restart the portal.

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-02-02 Thread tom lo via PacketFence-users
Hi Fabrice, Just to see if you have any idea or suggestions for us to troubleshoot the issues. Regards, Tom On Thu, Jan 25, 2018 at 12:21 PM, tom lo wrote: > Hi Fabrice, > > Here is the content from the log file httpd.portal.access when the > user hit the portal. >

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-25 Thread tom lo via PacketFence-users
Hi Fabrice, Here is the content from the log file httpd.portal.access when the user hit the portal. 172.18.x.y - - [23/Jan/2018:11:31:37] "captive.apple.com" "GET /hotspot-detect.html HTTP/1.0" 302 1080 "-" "CaptiveNetworkSupport-355.30.1 wispr" 4896 172.18.x.y - - [23/Jan/2018:11:32:22]

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-24 Thread Durand fabrice via PacketFence-users
Le 2018-01-23 à 04:41, tom lo a écrit : Hi Fabrice, We tried to uncheck the box "locationlog Close On Accounting Stop", and restarted packetfence, but found the users are still stuck in registration VLAN. The queue count was zero at the moment. We got the mysql output during each steps in

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-23 Thread tom lo via PacketFence-users
Hi Fabrice, We tried to uncheck the box "locationlog Close On Accounting Stop", and restarted packetfence, but found the users are still stuck in registration VLAN. The queue count was zero at the moment. We got the mysql output during each steps in the registration process. 1. When user

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-22 Thread Fabrice Durand via PacketFence-users
Hello Tom, there : https://pf_mgmt:1443/admin/configuration#configuration/main/advanced Regards Fabrice Le 2018-01-20 à 19:03, tom lo a écrit : > Hi Durand, > > What change should I make on PF to "disable update locationlog on accounting"? > > > Regards, > Tom > > On Sun, Jan 21, 2018 at 4:31

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-22 Thread tom lo via PacketFence-users
Hi Durand, What change should I make on PF to "disable update locationlog on accounting"? Regards, Tom On Sun, Jan 21, 2018 at 4:31 AM, Durand fabrice wrote: > Hello Tom, > > > Le 2018-01-20 à 03:02, tom lo a écrit : >> >> Hi Durand, >> >> >> Thanks for your reply and

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-20 Thread Durand fabrice via PacketFence-users
Hello Tom, Le 2018-01-20 à 03:02, tom lo a écrit : Hi Durand, Thanks for your reply and please see if my understanding is correct about the locationlog. If the locationlog is correct, from mysql, I should see one entry when a device reach captive portal, and another entry immediately after

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-20 Thread tom lo via PacketFence-users
Hi Durand, Thanks for your reply and please see if my understanding is correct about the locationlog. If the locationlog is correct, from mysql, I should see one entry when a device reach captive portal, and another entry immediately after the authentication complete, with matching start / end

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-19 Thread Durand fabrice via PacketFence-users
Hello Tom, just after a radius request, can you check in the database if the locationlog is correct ? (the radius request is suppose to update the locationlog) And also when it failed. select * from locationlog where mac="ab:cd:ef:12:34:56"; Last thing, can you verify if the queue is full

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-19 Thread Durand fabrice via PacketFence-users
Hello Tom, how did you configured the Ruckus smartzone, are you doing web-auth, mac-auth or 802.1x ? Regards Fabrice Le 2018-01-16 à 09:57, tom lo via PacketFence-users a écrit : Hi Ludovic, We are still using ZoneDirector, not the newer SmartZone controller, and seems Packetfence start

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-17 Thread tom lo via PacketFence-users
Hi, We checked packetfence.log and did a comparison between working and non-working VLAN redirection. When VLAN redirection works properly, "re-evaluating access" related log has no warning. Jan 12 12:07:18 httpd.portal(3102) INFO: [mac:ab:cd:ef:12:34:56] re-evaluating access (manage_register

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-16 Thread tom lo via PacketFence-users
Hi Ludovic, We are still using ZoneDirector, not the newer SmartZone controller, and seems Packetfence start supporting SmartZone from version 6.5 In version 6.4, which we are using, there are only one switch type for select "Ruckus Wireless Controllers". So you would suggest we to try another

Re: [PacketFence-users] users stay in registration VLAN after authentication success

2018-01-16 Thread Ludovic Zammit via PacketFence-users
Hello there, PacketFence two different switch module, there is a legacy one and the other one is meant for the SmartZone controller. Have you tried to change the switch module ? Thanks, Ludovic Zammit lzam...@inverse.ca :: +1.514.447.4918 (x145) ::

[PacketFence-users] users stay in registration VLAN after authentication success

2018-01-16 Thread tom lo via PacketFence-users
Hi, We've been using Packetfence ZEN 6.4 with Ruckus ZoneDirector for a while, to authentication user against AD before putting them into production VLAN. It was working fine until recently that users report that when they doing authentication in captive portal, they start seeing the message