Hi Fabrice,
The simple term is the browser cannot open the captive portal. In the
bottom left of the browser it show 'Performing a TLS handshake to
pf01.domain' and then show 'time out' because after open
msftconnecttest.com/redirect it redirect to the pfserver
Hello Ibrahim,
Le 2018-05-10 à 21:06, Ibrahim Lubis via PacketFence-users a écrit :
Hi,
Im using packetfence as vlan enforcement mode, my testpc got into the
right vlan-registration, any website ip ping from testpc redirected to
the pf server. But when automaticly the ie browser
Hi,
Im using packetfence as vlan enforcement mode, my testpc got into the right
vlan-registration, any website ip ping from testpc redirected to the pf
server. But when automaticly the ie browser open(msftconnecttest.com/
redirect) to show captive portal its only connecting.
[network.conf]
Hello Thomas,
Le 2018-05-10 à 16:26, Thomas, Gregory A via PacketFence-users a écrit :
I have setup a test environment so that I can move to the new version
of Packetfence (currently running 7.4)
In this environment it is running as expected (with one concern), when
I move it to
tshark -i eth0 -f "port 389" -w /tmp/ldap.pcap
Le 2018-05-10 à 14:56, Rafael Rocha a écrit :
Hi Fabrice, I will try to do the pcap tomorrow for the LDAP source/Bind.
Can you share instructions how to do it ?
About the sponsor,
How the sponsor module should be working ? How it know where to
Hi Fabrice, I will try to do the pcap tomorrow for the LDAP source/Bind.
Can you share instructions how to do it ?
About the sponsor,
How the sponsor module should be working ? How it know where to look for my
authorized sponsors with the new version?
I remember that when working with other
I have setup a test environment so that I can move to the new version of
Packetfence (currently running 7.4)
In this environment it is running as expected (with one concern), when I move
it to production how do I set it up to issue IP Addresses on a supernet where
some addresses are reserved.
Hello Jeimerson,
it looks that your server packetfence2 is down.
Regards
Fabrice
Le 2018-05-10 à 06:19, Jeimerson C. Chaves via PacketFence-users a écrit :
Hello,
Sorry again, but you're experiencing the following sync error between
cluster nodes.
Thank you.
Com os melhores
