Hi Fabrice,
there it is :
=> cluster.conf
# Cluster configuration file for active/active
# This file will have it deactivated by default
# To activate the active/active mode, set a management IP in the cluster
section
# Before doing any changes to this file, read the documentation
#
Hello,
it's me again :-) , so the problem is definetly solved this time,
my cluster configuration was not correct thus preventing my portal from
showing up.
I was trying to make a 2 servers cluster using cluster installation guide
version 6.7.0
Thank you very much for your help Fabrice,
regards
Hello,
i noticed that you probably run a cluster, can you paste the
cluster.conf file ?
Also can you run that: pfcmd pfconfig show interfaces::portal_ints
and paste the output ?
Thanks
Fabrice
Le 19-04-30 à 09 h 41, pro fence via PacketFence-users a écrit :
don't mind the " backend has
don't mind the " backend has no server available" it was a false alarm.
I still dont know why the portal doesn't show up as i thought the
packetfence server management ip should listen on port 80 ... ?
Regards
On Tue, 30 Apr 2019 at 10:10, pro fence wrote:
> Hello,
>
> one thing i have in
Hello,
one thing i have in haproxy log file is :
backend registration_vlan_ip-backend has no server available!
backend isolation_vlan_ip-backend has no server available!
Any help is appreciated
Regards,
On Mon, 29 Apr 2019 at 16:06, pro fence wrote:
> Fabrice,
> here is what i have after
Fabrice,
here is what i have after issuing your commands :
tcp0 0 registration_vlan_ip:80 0.0.0.0:*
LISTEN 7758/haproxy
tcp0 0 isolation_vlan_ip:80 0.0.0.0:*
LISTEN 7758/haproxy
tcp0 0 127.0.0.1:800.0.0.0:*
LISTEN
Hello Fabrice,
thank you, here it is, i skipped the "alerting" section
#Subject prefix for email notifications of rogue DHCP servers, violations
with an action of "email", or any other
#PacketFence-related message.
subjectprefix=[PF Alertt]
[captive_portal]
#
#
Hello Pro,
haproxy is the process who is suppose to listen on the port 80 and 443.
It looks that the configuration is not correctly generated.
Can you you paste your pf.conf
and do that:
pfcmd pfconfig clear_backend
pfcmd configreload hard
pfcmd service haproxy-portal restart
pfcmd
HI,
thanks for the reply i have already did that.
Here is what i have
tcp0 0 127.0.0.1:80 0.0.0.0:*
LISTEN 9239/httpd
tcp0 0 127.0.0.1:80127.0.0.1:33796
SYN_RECV-
tcp0 0 registration_vlan_ip:80
Hello pro,
you just need to add and additional listening daemon on the management
interface:
https://@mgmt_ip:1443/admin/configuration#configuration/networks/interfaces
Then restart packetfence.
Regards
Fabrice
Le 19-04-29 à 08 h 49, pro fence via PacketFence-users a écrit :
Hi,
thanks
Hi,
thanks for the reply. but i still don't see how to active port 80 and 443
on management ip.
Any help is appreciated
Regards,
On Mon, 29 Apr 2019 at 14:06, Nicolas Quiniou-Briand via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
>
>
> On 2019-04-29 10:27 a.m., pro
HI,
my packetfence server is not listening on port 80 on the management
interface (and my portal is on that interface as per the installation
guide), but it is listening on registration and isolation.
changing the /usr/local/pf/var/conf/haproxy-portal.conf is useless because
it is lost on
Hi,
so, i found out that when i send a ping request to my packetfence server’s
ip address (so the management interface) there is a time out because
packetfence has created a route on the server for the registration Vlan
with a 0.0.0.0 gateway :
removing this route i am able to ping the server.
Hi,
i am sorry but i don't understand what you meant. I have configured the " Auth
Called Station ID Typ" on the cisco WLC gui.
so i don't know exactly what i am supposed to do in the
$PF/lib/pf/Switch.pm file ?
Regards,
On Wed, 17 Apr 2019 at 09:16, Nicolas Quiniou-Briand via PacketFence-users
so the mac detection thing is solved, i have activated it for the radius
accountin
g on wlc.
But i still have a blank captive portal and here is my packetfence.log :
packetfence_httpd.aaa: httpd.aaa(7066) INFO: [mac:] handling radius autz
request: from switch_ip => (ip), connection_type =>
Hello,
On 2019-04-16 4:27 p.m., pro fence via PacketFence-users wrote:
Also on the wlc i have configured " Auth Called Station ID Type = AP MAC
address:SSID"
Change this setting to:
* "xx:xx:xx:xx:xx:xx:SSID"
or
* ":SSID"
with xx:xx:xx:xx:xx:xx MAC address of node.
You can
For more details :
in the packetfence log, on the first line i can see the switch_mac =>
(bx:xx:)
but further, i have "Unable to extract MAC from Called-Station-Id" but the
ssid is well retrieved.
Also on the wlc i have configured " Auth Called Station ID Type = AP MAC
address:SSID"
On
Hi Everybody,
i am using packetfence 8.3 with cisco wlc 5508 ios 8.3.
the issue that i am encountering is that when my devices connect to the
ssid, a blank "captive.apple.com" appears and the logs show a redirection
to http://my_packetfence_server/Cisco::WLC_5500/sida2738f? i have also
tried with
18 matches
Mail list logo
