Hello Cory,
what you describe is WLC web authentication.
It mean that the device stay on the same layer 2 network and is
redirected to the captive portal if the device is unreg.
For the flow policy you can use the wlc qos for that.
http://www.packetfence.org/downloads/PacketFence/doc/PacketF
Hello (new to the forum) -
I've been tasked with a captive portal replacement for our companies
currently paid solution - sure we all know the 'green monster' with an 'X'.
I've read through deployment and admin guides but our needs require a very
vanilla offering to our customers - hospitality in
cboley@SRVCHPACKETFENCE:~$ cat /usr/local/pf/conf/pf-release
PacketFence 5.3.1
-Original Message-
From: packetfence-users-requ...@lists.sourceforge.net
[mailto:packetfence-users-requ...@lists.sourceforge.net]
Sent: Monday, November 09, 2015 12:10 PM
To: packetfence-users@lists.sourceforg
Nicola,
Is the DHCP handled by PacketFence for the inline segment ?
A locationlog entry is required by PacketFence to modify iptables / ipset. The
message you are getting seems to state that no such entry exists.
A locationlog, in inline, is created / modified by DHCP
Cheers!
dw.
—
Derek Wuelf
Hi there,
We have Packetfence 5.4 now working for staff using PF PKI and EAP via radius
back to AD.
Role based vlan swap from registration portal profile vlan to secure hidden
SSID vlan works.
We are now trying to setup parallel SSIDs and config for sponsored guest access.
Sponsor can approve a
They suggested me to open a request for enhancement…. I agree with you, they
will never implement this feature.
Regards
M
Da: Louis Munro [mailto:lmu...@inverse.ca]
Inviato: lunedì 16 novembre 2015 15.46
A: packetfence-users@lists.sourceforge.net
Oggetto: Re: [PacketFence-users] R: Meraki and P
Hello.
I have an installation of PacketFence under Debian (armhf).
Everythong seems to work, but when the ures logs in (or when I put the
node in "registered" state), its ip/MAC aren't added to ipset.
I get this in pfmon.log:
> Can't re-evaluate access because no open locationlog entry was found
Hi,
So I've finally got around to doing some further troubleshooting on this
connection issue via tracing on the windows machine. It appears that there
is something wrong with the server cert signature that the windows client
can't verify. I am getting this in the client TLS logs:
[960] 11-17 15: