Hi,

Thanks for tips.
I start the httpd.admin process by hand and I could see the web page again.
There comes another issue, I open https://ip:1443 and it always redirect to
https:ip:1443/configurator/.
I tired different PC and browser, it doesn't make change.

Thanks,
Zlyzwy



On Sun, Jul 14, 2013 at 12:10 AM, Fabrice Durand <[email protected]> wrote:

>  Hi
>
>
> http://sourceforge.net/mailarchive/forum.php?thread_name=1373633549.16785.YahooMailNeo%40web164502.mail.gq1.yahoo.com&forum_name=packetfence-users
>
> Fabrice
>
> Le 2013-07-13 10:17, William Zhou a écrit :
>
> Hi All,
>
>  I just tried ZEN-Desktop, it seems I can setup the PacketFence through
> web.
> After I finished the 6-step configuration, I was unable to access the web
> page again.
>  There is no error when I start the Packetfence.
> Here is my conf file:
> ====================================================================
> /usr/local/pf/conf/pf.conf
>  [general]
> #
> # general.domain
> #
> # Domain name of PacketFence system.
> domain=zlyzwy.cn
> #
> # general.hostname
> #
> # Hostname of PacketFence system.  This is concatenated with the domain in
> Apache rewriting rules and therefore must be resolvable by clients.
> hostname=PacketFence
> #
> # general.dhcpservers
> #
> # Comma-delimited list of DHCP servers.  Passthroughs are created to allow
> DHCP transactions from even "trapped" nodes.
> dhcpservers=192.168.0.1
>
>  [alerting]
> #
> # alerting.emailaddr
> #
> # Email address to which notifications of rogue DHCP servers, violations
> with an action of "email", or any other
> # PacketFence-related message goes to.
> [email protected]
>
>  [database]
> #
> # database.pass
> #
> # Password for the mysql database used by PacketFence.
> pass=xxxxxxx
>
>  [interface eth0]
> ip=192.168.1.28
> type=management
> mask=255.255.255.0
>
>  [interface eth1]
> enforcement=inline
>  ip=192.168.0.1
> gateway=192.168.0.1
> type=internal
> mask=255.255.255.0
>  =====================================================================
> /usr/local/pf/conf/dhcpd.conf
>  # dhcpd configuration
> # This file is manipulated on PacketFence's startup before being given to
> dhcpd
> authoritative;
> ddns-update-style none;
> ignore client-updates;
>
>  %%networks%%
>
>  subnet 192.168.0.0 netmask 255.255.255.0 {
>
>        option routers                  192.168.0.1;
>         option subnet-mask              255.255.255.0;
>
>         option nis-domain               "zlyzwy.cn";
>         option domain-name              "zlyzwy.cn";
>         option domain-name-servers      8.8.8.8;
>
>         option time-offset              -18000; # Eastern Standard Time
>
>         range dynamic-bootp 192.168.0.100 192.168.0.200;
>         default-lease-time 21600;
>         max-lease-time 43200;
>
>  }
>  ======================================================================
> /usr/local/pf/conf/networks.conf
>  [192.168.0.0]
> dns=8.8.8.8
> dhcp_start=192.168.0.100
> gateway=192.168.0.1
> domain-name=inline.zlyzwy.cn
> named=enabled
> dhcp_max_lease_time=86400
> dhcpd=enabled
> type=inline
> netmask=255.255.255.0
> dhcp_end=192.168.0.246
> dhcp_default_lease_time=86400
>  =====================================================================
>  ifconfig -a
>  eth0      Link encap:Ethernet  HWaddr 00:0C:29:4F:63:94
>           inet addr:192.168.1.28  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::20c:29ff:fe4f:6394/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1417020 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:41193 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1147470612 (1.0 GiB)  TX bytes:3176415 (3.0 MiB)
>
>  eth1      Link encap:Ethernet  HWaddr 00:0C:29:4F:63:9E
>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::20c:29ff:fe4f:639e/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:6570 (6.4 KiB)
>
>  lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:152 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:11497 (11.2 KiB)  TX bytes:11497 (11.2 KiB)
> ===================================================================
>  [root@PacketFence ~]# service packetfence start
> Starting PacketFence...httpd.admin|already running
> Checking configuration sanity...
> service|command
> config files|start
> iptables|start
> named|already running
> dhcpd|already running
> snort|start
> suricata|start
> radiusd|already running
> httpd.webservices|already running
> httpd.portal|already running
> snmptrapd|already running
> pfdetect|start
> pfsetvlan|already running
> pfdhcplistener|already running
> pfmon|already running
>  =======================================================================
>
>
>  Thanks
> Zlyzwy
>
>
> On Sat, Jul 13, 2013 at 8:15 PM, William Zhou <[email protected]> wrote:
>
>>  Thanks for your reply.
>> I don't think it's about the firewall because I can access the PF by SSH.
>> But I did try, it doesn't change anything.
>>
>>  I just update to latest version of PF but it doesn't change anything
>> .....
>> If anyone had some idea on this issue,, Please help me....
>>
>>  Thanks
>> Zlyzwy
>>
>>
>> On Sat, Jul 13, 2013 at 3:42 AM, forbmsyn <[email protected]> wrote:
>>
>>> Did you check the firewall (iptables)?
>>>
>>>  In my case I always run the following command after PF reboot. I have
>>> not idea how to manage iptables from PF yet so I just simply allow
>>> everything from my network to PF. 192.168.10.0/24 is my network.
>>>
>>>  iptables -A INPUT -s 192.168.10.0/24 -i eth0 -j ACCEPT
>>>
>>>  Good luck!
>>>
>>>  Regards,
>>> Jacky
>>>
>>>
>>>
>>>  On Fri, Jul 12, 2013 at 12:55 PM, William Zhou <[email protected]>wrote:
>>>
>>>>  Hi All,
>>>>
>>>>  I've tried a lot in Debian, however there is no success. So I am
>>>> going to move the OS to Centos.
>>>>
>>>>   I just setup a fresh CentOS for PacketFence in VM Workstaion 9.
>>>> All the OS and PacketFence software are installed successful by
>>>> following the guide.
>>>>
>>>>  But I just can't open the configuration page -- '
>>>> https://@ip_of_packetfence:1443/configurator.'
>>>>  I can ping&SSH to the server without any problem.
>>>> What I've tried here:
>>>> 1. restart&reinstall the package and OS
>>>> 2. restart the httpd service
>>>> 3. try to start packetfence, there is some error for missing
>>>> configuration
>>>>
>>>>  Did anyone see this issue before?
>>>>
>>>>  Thanks again for any help...
>>>>
>>>>  Zlyzwy
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> PacketFence-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> PacketFence-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro 
> today!http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> PacketFence-users mailing 
> [email protected]https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to