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 restart.
How can i add listening directives (on port 80 and 443) for my management ip ? Regards On Fri, 19 Apr 2019 at 19:01, pro fence <[email protected]> wrote: > 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. on restart packetfence > recreates that same route. all the other vlan are reachable except for the > registration. > > thanks in advance for any help that i can get. > Regards > > On Thursday, 18 April 2019, Ludovic Zammit <[email protected]> wrote: > >> Perfect :) >> >> Have a nice day! >> >> >> Ludovic [email protected] :: +1.514.447.4918 (x145) :: >> www.inverse.ca >> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence >> (http://packetfence.org) >> >> >> >> >> >> On Apr 18, 2019, at 4:45 AM, pro fence <[email protected]> wrote: >> >> So i think i found the problem : communication problem beetween the vlan >> and the packetfence server's network. >> >> Thanks again Ludovic for taking the time to help me !!!! >> >> regards, >> >> >> On Thu, 18 Apr 2019 at 09:58, pro fence <[email protected]> wrote: >> >>> yes i already tried that, thanks Ludovic. >>> >>> If anyone else had already stumbled on this issue, please let me know >>> >>> Regards, >>> >>> On Wed, 17 Apr 2019 at 18:59, Ludovic Zammit <[email protected]> wrote: >>> >>>> You can do a portal preview via the connection profile section on the >>>> Packetfence web admin. >>>> >>>> Thanks >>>> >>>> On Apr 17, 2019, at 12:22 PM, pro fence <[email protected]> wrote: >>>> >>>> ok, thnk you for your help. >>>> one last question, do you know if there is a way to test the >>>> redirection url on the packetfence server ? because i don’t know exactly >>>> what the final working redirected url should look like ? >>>> >>>> because i dont’t think that a wget on >>>> http://packetfence_server/Cisco_WLC/sid.... >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Wednesday, 17 April 2019, Ludovic Zammit <[email protected]> wrote: >>>> >>>>> Those kind of issues are hard to troubleshoot. >>>>> >>>>> It would require a session to check all the configuration and the >>>>> behaviour in real time as well. >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> Ludovic [email protected] :: +1.514.447.4918 (x145) :: >>>>> www.inverse.ca >>>>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence >>>>> (http://packetfence.org) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Apr 17, 2019, at 11:33 AM, pro fence <[email protected]> wrote: >>>>> >>>>> HI, >>>>> >>>>> it's on, the only difference is the DHCP, i have none, and per the >>>>> logs above, an ip address is provided for the client. i have cisco wlc >>>>> 5508 >>>>> ios 8.3.141.0 >>>>> >>>>> <nac.png> >>>>> >>>>> Thank you Ludovic, >>>>> >>>>> On Wed, 17 Apr 2019 at 17:07, Ludovic Zammit <[email protected]> >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Make sure you have the “Cisco ISE” or “Radius NAC” support enable on >>>>>> your SSID config >>>>>> >>>>>> <SSID_6.png> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> Ludovic [email protected] :: +1.514.447.4918 (x145) :: >>>>>> www.inverse.ca >>>>>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence >>>>>> (http://packetfence.org) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Apr 17, 2019, at 10:13 AM, pro fence <[email protected]> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> no nothing in httpd.portal.access nor httpd.portal.error >>>>>> >>>>>> Thanks in advance for your help >>>>>> Regards, >>>>>> >>>>>> On Wed, 17 Apr 2019 at 15:33, Ludovic Zammit <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Do you see something in the logs/httpd.portal.access regarding your >>>>>>> connection ? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> >>>>>>> Ludovic [email protected] :: +1.514.447.4918 (x145) :: >>>>>>> www.inverse.ca >>>>>>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and >>>>>>> PacketFence (http://packetfence.org) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Apr 17, 2019, at 8:46 AM, pro fence <[email protected]> wrote: >>>>>>> >>>>>>> Hi Ludovic, >>>>>>> >>>>>>> thank you for your reply. >>>>>>> >>>>>>> Yes, on the management interface, the portal is added as an >>>>>>> additionnal listening daemon. >>>>>>> I think that it's an ACL issue on the WLC 5508; i have followed the >>>>>>> network guide and here is what i have so far : >>>>>>> >>>>>>> <acl.png> >>>>>>> >>>>>>> Thank you in advance, >>>>>>> Regards, >>>>>>> >>>>>>> >>>>>>> On Wed, 17 Apr 2019 at 13:55, Ludovic Zammit <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> You can ignore the inline message, it’s a Packetfence internal. >>>>>>>> >>>>>>>> Maybe your ACL Pre-Auth-For-WebRedirect is not configured >>>>>>>> correctly. Did you follow the network guide to configure it? >>>>>>>> >>>>>>>> You should allow dns,dhcp and all traffic http and https to >>>>>>>> Packetfence management up adresse. >>>>>>>> >>>>>>>> Make sure you have the portal daemon listening on the management >>>>>>>> interface as well. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> > On Apr 17, 2019, at 5:56 AM, pro fence via PacketFence-users < >>>>>>>> [email protected]> wrote: >>>>>>>> > >>>>>>>> > Pre-Auth-For-WebRedirect >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
