sts.sourceforge.net>'
<mailto:packetfence-users@lists.sourceforge.net>
Subject: RE: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
I started tcpdump on packetfence to filter for traffic to my Ruckus controller.
tcpdump didn’t catch any traffic between PacketFen
ric Rolleman mailto:eric.rolle...@cmsd.bc.ca>>
Subject: Re: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
I started tcpdump on packetfence to filter for traffic to my Ruckus controller.
tcpdump didn’t catch any traffic between PacketFence and the Ruckus Controller.
There
Thanks for the reply. I'll look into that.
___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
presume that the PacketFence to Ruckus communication to authorize the
> client will only happen if Ruckus does the redirecting to the captive
> portal rather than PacketFence’s dns-enforcement.
>
>
>
> *From:* Eric Rolleman
> *Sent:* Tuesday, December 18, 2018 2:52 PM
>
<mailto:packetfence-users@lists.sourceforge.net>
*Cc:* Eric Rolleman mailto:eric.rolle...@cmsd.bc.ca>>
*Subject:* [PacketFence-users] Captive Portal authorization Ruckus
Interface logging
Is there a log anywhere that I can look at to find out why clients
aren’t getting
: Eric Rolleman via PacketFence-users
Sent: Tuesday, December 18, 2018 2:52 PM
To: packetfence-users@lists.sourceforge.net
Cc: Eric Rolleman
Subject: Re: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
I started tcpdump on packetfence to filter for traffic to my Ruckus
than PacketFence’s dns-enforcement.
From: Eric Rolleman
Sent: Tuesday, December 18, 2018 2:52 PM
To: 'packetfence-users@lists.sourceforge.net'
Subject: RE: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
I started tcpdump on packetfence to filter for traffic to my
Absolutely. Hopefully we can determine what the fix is.
From: Caique Araujo via PacketFence-users
Sent: Tuesday, December 18, 2018 4:20 AM
To: packetfence-users@lists.sourceforge.net
Cc: Caique Araujo
Subject: Re: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
.
Is the hotspot feature of PacketFence broken in in 8.1?
From: Caique Araujo via PacketFence-users
Sent: Tuesday, December 18, 2018 4:20 AM
To: packetfence-users@lists.sourceforge.net
Cc: Caique Araujo
Subject: Re: [PacketFence-users] Captive Portal authorization Ruckus Interface
logging
t;
>
>
> The instructions tell me to type in a URL that is not supported…
>
>
>
> *From:* Eric Rolleman via PacketFence-users <
> packetfence-users@lists.sourceforge.net>
> *Sent:* Wednesday, December 12, 2018 5:07 PM
> *To:* packetfence-users@lists.sourceforge.net
&
-users] Captive Portal authorization Ruckus Interface
logging
Is there a log anywhere that I can look at to find out why clients aren't
getting authorized? I found the following dir: " /usr/local/pf/logs ", but none
of the logs appear to contain any data on why the my Ruckus Contro
Is there a log anywhere that I can look at to find out why clients aren't
getting authorized? I found the following dir: " /usr/local/pf/logs ", but none
of the logs appear to contain any data on why the my Ruckus Controller isn't
authorizing the client. Or if my configuration for the Web
12 matches
Mail list logo
