> Try:
>
> systemctl restart packetfence-pfperl-api
>
> Thanks,
>
>
> Ludovic Zammit
>
>
>
>
>
> On Feb 14, 2020, at 3:46 PM, Chris Abel via PacketFence-users <
> packetfence-users@lists.sourceforge.net> wrote:
>
> Hi All,
>
> I just r
Hi All,
I just recently upgraded pf from 8.3 to 9.3. Everything seems to work
great, but I am unable to log into the new web admin interface. I get the
following message:
Couldn't find any information for the current token. Either it is invalid
or it has expired.
I am still able to authenticate
I have tested this issue with a clean install of packetfence 8.1 in CentOS
7 with VLAN enforcement and have found that the issue is there. This is NOT
my setup, but appears to be a bug in packetfence. Nicholas, do you mind
reopening the bug report that you had originally closed?
Let me know if I
Thanks for the help thus far Nicholas. Here is the DEBUG log when trying to
register:
Oct 16 09:47:40 pf packetfence_httpd.portal: httpd.portal(32415) DEBUG:
[mac:00:11:22:33:44:55] AUP is required and it's value is : 1
(captiveportal::PacketFence::Form::Authentication::check_aup_form)
Oct 16
Hi Nicolas,
Yes, I have applied all steps of the upgrade process. I have re-ran the
script and those commands and still seeing this issue.
I understand you tried the null source on a fresh install of 8.1, but did
you try the null source with the "Email Required" option? That is the
option that
Just an update,
I am still having this issue. The null authentication source simply does
not work after upgrading to pf 8.1 from pf 7.9 if you have email required
enabled. I have created a new authentication source, new connection
profile, and overwrote my authentication.pm file with the current
Hi again Nicolas,
1. I do indeed get the same message when I try to register using the
Preview button.
2. I'm not sure what you mean. I tried to register this device from an
Android phone so maybe that is why the log was generated? All devices are
getting this message though when trying to
sonal Device Registration
>
> On Thu, Sep 20, 2018 at 2:10 PM Nicolas Quiniou-Briand via
> PacketFence-users wrote:
>
>> Hello Crhis,
>>
>> On 2018-09-19 01:36 PM, Chris Abel via PacketFence-users wrote:
>> > I'm getting the following error mess
n Thu, Sep 20, 2018 at 2:10 PM Nicolas Quiniou-Briand via
PacketFence-users wrote:
> Hello Crhis,
>
> On 2018-09-19 01:36 PM, Chris Abel via PacketFence-users wrote:
> > I'm getting the following error message when a node tries to register
> > using the null authentication sou
I'm getting the following error message when a node tries to register using
the null authentication source that requires an email address:
Caught exception in captiveportal::Controller::Root->dynamic_application
"No authentication context provided at /usr/local/pf/lib/pf/
authentication.pm line
I am also seeing this with many android devices including my Samsung s8+.
LG phones are working fine though. I just installed pf 7.4 on a new CentOS
install.
On Wed, Feb 21, 2018 at 2:51 PM, Ian MacDonald via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
>
> We two pf
Hey All,
I was able to get deauth working with my Unifi APs and it seems everything
is working smoothly. Here is the configuration I used for the switch in
packetfence:
[Unifi AP IP Address or subnet]
description=Unifi Access Points
group=Unifi
radiusSecret=RaidusPassword
controllerIp=Unifi
So the reason why the captive portal was not showing up was because port 80
and 443 were not listening on the registration interface. They were only
listening on the local interface 127.0.0.1. Fabrice helped me figure this
out by pointing to the haproxy service which is responsible for forwarding
Hello all,
I am also trying to get my Unifi APs working with packetfence. It seems
that I am very close. I am able to get the portal to show up on the client
when in the registration vlan, but after registering, the client never
deauth's and disconnects from the access point. I can disable my
Hello all,
I have set up a new packetfence server set up with dynamic vlans in
out-of-band and am having issues with the captive portal popping up when
clients connect to the AP. The clients get put into the registration vlan
and are assigned the registration interface as the DNS server.
Hello all,
Something in my packetfence config is messing up my networking on the
centos machine. It seems to have assigned a self assigned ip address to all
of my interfaces and when I remove my vlan interfaces, they reappear after
a reboot. I'm really not sure what happened, but I've already
I realize the 169.254 addresses are link=local addresses that are assigned
from the /etc/networks file? Could these be causing issues. Does anyone
else have these addresses with their working packetfence? Also, my routed
networks do not show up in my routing table, but do show up in my routing
17 matches
Mail list logo
