Hello Jay,
You may have a beginning of answer with the iptables. It’s the iptables on the
system, not the one managed by PacketFence because during the configurator the
PF’s iptables is not started yet at the beginning.
Here’s the command to flush everything:
systemctl disable firewalld
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
Thanks,
Ludovic Zammit
lzam...@inverse.ca <mailto:lzam...@inverse.ca> :: +1.514.447.4918 (x145) ::
www.inverse.ca <http://www.inverse.ca/>
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>)
and PacketFence (http://packetfence.org <http://packetfence.org/>)
> On Jul 4, 2018, at 10:23 AM, Jay Hauss via PacketFence-users
> <packetfence-users@lists.sourceforge.net> wrote:
>
>
> Hello,
>
> I'm betting this is the same problem I mailed the list about last week (Re:
> Step 7 of the configuration failing)...
> No luck on getting advice here but I've been playing around trying to get
> things to work. Here's some information that I wish was mentioned in the
> installation guide...
>
> By default, the web GUI can only be accessed over the interface you set as
> Management during the configuration wizard.
>
> So if during the configuration you've changed the management network to
> something other than what you're connecting from/to, you'll get the timeout
> issue. It is very easy to lock yourself out of the PacketFence server if you
> set the management network wrong (I wish there was some sort of
> warning/reminder).
>
> The next thing that might block/interfere for whatever reason is the iptables
> service. I haven't had a chance to explore this but you could try disabling
> it (or flushing it) to see if this might also fix the problem. The command
> would be something like '/usr/local/pf/bin/pfcmd service iptables
> stop|restart|start'.
>
> -Jay
> Sent: Wednesday, July 04, 2018 at 8:12 AM
> From: "Ludovic Zammit via PacketFence-users"
> <packetfence-users@lists.sourceforge.net>
> To: packetfence-users@lists.sourceforge.net
> Cc: "Ludovic Zammit" <lzam...@inverse.ca>, Nicholas
> <nicholas....@advancedatan.com>
> Subject: Re: [PacketFence-users] Packetfence configuration
> Hello There,
>
> I will suggest you to check in the /usr/local/pf/logs/packetfence.log to see
> any error or fail message.
>
> You can also use the command /usr/local/pf/bin/pfcmd service pf status
>
> Thanks,
> Ludovic Zammit
> lzam...@inverse.ca <mailto:lzam...@inverse.ca> :: +1.514.447.4918 (x145) ::
> www.inverse.ca <http://www.inverse.ca/>
> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu
> <http://www.sogo.nu/>) and PacketFence (http://packetfence.org
> <http://packetfence.org/>)
>
>
>
>
> On Jul 3, 2018, at 11:26 PM, Advancedata Network via PacketFence-users
> <packetfence-users@lists.sourceforge.net
> <mailto:packetfence-users@lists.sourceforge.net>> wrote:
>
> Hi,
>
> I am first time configuring packetfence out of band.
> I’m using PF zen open virtual for VM. Once I extract and runs it. I update
> it,
> yum update
> Then I configure the packetfence.
> However, after few seconds later. The pf gui interface freeze. Then it says
> “This site can’t be reached. However, I still able to ping to the IP that
> appear once pf completely loaded.
> I reboot the vm also not solve the problem.
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org/>!
> http://sdm.link/slashdot_______________________________________________
> <http://sdm.link/slashdot_______________________________________________>
> PacketFence-users mailing list
> PacketFence-users@lists.sourceforge.net
> <mailto:PacketFence-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> <https://lists.sourceforge.net/lists/listinfo/packetfence-users>------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> <http://sdm.link/slashdot_______________________________________________>
> PacketFence-users mailing list PacketFence-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> <https://lists.sourceforge.net/lists/listinfo/packetfence-users>------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> PacketFence-users mailing list
> PacketFence-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
