> On Jun 6, 2016, at 11:05 , Morris, Andi wrote:
>
> When setting the reverse proxy to forward the original IP the packetfence
> server doesn’t seem to respond to the incoming request.
>
> Tcpdump output of the packetfence server shows:
> 16:01:51.644525 IP
I solved the VLAN issue.
On the xen hypervisor, you have to use a custom script (during loading of
the vm), which sets the proper VLANs fort he PF vm. (see /etc/xen/scripts)
using open-vswitch.
More specifically, I changed
do_or_die ovs-vsctl --timeout=30 \
-- --if-exists del-port
> Did you experienced this with the latest version (6.0.3)? I tried a fresh
install
> on Jessie and did not experienced this issue.
Yes, 6.0.3.
I must say I created the xen vm using xen-create-image which seems to
install only the bare minimum debian jessie.
>
> Although I am running this VM host
If you disable the error (in code) you must add back the 5.7 code that handles
the email activation:-
sub doEmailRegistration in
/usr/local/pf/html/captive-portal/lib/captiveportal/PacketFence/Controller/Activate/Email.pm
I think this was a MASSIVE mistake by the devs to force this setup on
When setting the reverse proxy to forward the original IP the packetfence
server doesn’t seem to respond to the incoming request.
Tcpdump output of the packetfence server shows:
16:01:51.644525 IP host86-176-129-66.range86-176.btcentralplus.com.51863 >
pfguestdev.internal.uwic.ac.uk.https:
I have a fix for this.
Andrew
From: Morris, Andi [mailto:amor...@cardiffmet.ac.uk]
Sent: 06 June 2016 15:19
To: packetfence-users@lists.sourceforge.net
Subject: Re: [PacketFence-users] Still a problem with registration process
Hi Andrew,
I'm also seeing the exact same issue. Users choose to
You need to hack the code in the file
/usr/local/pf/html/captive-portal/lib/captiveportal/PacketFence/Controller/Activate/Email.pm.
I simply added back the code for the from the 5.7 and called it instead of
generating the error message:-
#
# EDIT BY APKT to re-enable activation from a
On my current reverse proxy solution there’s very little config that can be
done. I can forward the original host header and/or I can proxy the request
with the original IP or the proxied IP.
When I choose to send the original IP the requests don’t seem to ever reach the
server, so I’m