In fact you need to restart the portal, haproxy and iptables to make it
available.
Le 2018-02-19 à 03:29, E.P. a écrit :
>
> And my further attempts to put two and two together and look back in
> time into this mailing list showed that Fabrice already answered this
> question before
>
> Yes,
Hi Tim,
I’ve added the portal interface to be on the same network with management and
from the perspective of PF I believe it is accepted
My current problem now is that haproxy service doesn’t start and the attempt to
start it from CLI in debugging mode throws out weird messages about
Folks,
I feel awkward to bombard this list with questions but I do hope I'm heard
and someone can help me.
On the way to make the captive portal to surface but stumbling upon the
redirect or rather packetfence not completing it.
I'm connecting to the guest SSID and open the web browser on the
Scratching my head trying to interpret these events having started haproxy in
the debug mode.
What’s wrong in the haproxy.conf or rather how it should look with the second
IP address added for portal?
I even removed the portal interface temporarily, i.e. there’s no 172.16.0.223
configured now
It's like the port is not open on the interface (443)
Le 2018-02-18 à 22:19, E.P. a écrit :
>
> Here it is, Fabrice
>
> 10.0.254.3 is the WiFi client and 172.16.0.222 is PF.
>
> Tcpdump.pcap is attached and it is made right on PF
>
> The second capture is made on the laptop connected to guest
Hello Ebrar,
what is the root portal module you use on your connection profile ?
And if it's the default what are the sources you defined ?
Regards
Fabrice
Le 2018-02-23 à 03:22, EbrarLeblebici via PacketFence-users a écrit :
> Hey All,
>
> I coud not see login page after I accept the terms
