Hi Derek,
Thanks for ur response, i was however able to resolve the issue. The
network service had been down.
------------------------------
On Tue, Jul 2, 2013 1:47 PM PDT Derek Wuelfrath wrote:
>Please paste output of:
>service packetfence status
>ps aufx | grep http
>ifconfig
>ip addr
>
>Derek
>
>--
>[email protected] :: +1.514.447.4918 (x110) :: www.inverse.ca
>Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
>(www.packetfence.org)
>
>On 2013-06-28, at 12:52 AM, frank muriuki <[email protected]> wrote:
>
>> Is it that no one has ever experienced my challenges or simply it's just a
>> delayed response.
>>
>> I really need help on this. Just possibly to understand where i would be
>> going wrong. I have configured one interface with 3 vlans i.e. Management,
>> Registration and Isolation. It works fine, until i restart the server thats
>> when i'm not able to access it via web browser.
>>
>> Guyz guyz...Help is needed right here!
>>
>>
>> From: frank muriuki <[email protected]>
>> To: "[email protected]"
>> <[email protected]>
>> Sent: Wednesday, June 26, 2013 6:38 PM
>> Subject: Re: [PacketFence-users] PacketFence: Interfaces & Networks
>> Configuration Disappear on Restart
>>
>> Hi,
>>
>> I solved the issue of the configuration getting lost on reboot (i realized
>> there were some services in CentOS that were down), however i now fail to
>> access packetfence via Web Browser.
>>
>> Kindly help me out on this.
>>
>> Regards,
>> Frank
>>
>>
>> From: frank muriuki <[email protected]>
>> To: "[email protected]"
>> <[email protected]>
>> Sent: Saturday, June 22, 2013 8:32 AM
>> Subject: Re: [PacketFence-users] PacketFence: Interfaces & Networks
>> Configuration Disappear on Restart
>>
>> Hi,
>>
>> The logs requested are as shown below;
>>
>> [root@localhost logs]# tail -f packetfence.log
>> Jun 22 08:16:58 pfdhcplistener(3469) FATAL: Unable to initiate packet
>> capture. Is eth0.20 an actual network interface? (main::dhcp_detector)
>> Jun 22 08:16:58 pfdhcplistener(3469) INFO: stopping pfdhcplistener for
>> interface eth0.20 (main::END)
>> Jun 22 08:16:58 pfdhcplistener(3458) INFO: pfdhcplistener_eth0.10 starting
>> and writing 3475 to /usr/local/pf/var/run/pfdhcplistener_eth0.10.pid
>> (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3475) WARN: Unable to open VLAN proc
>> description for eth0.10: No such file or directory
>> (pf::util::get_vlan_from_int)
>> Jun 22 08:16:58 pfdhcplistener(3475) INFO: DHCP detector on eth0.10 enabled
>> (main::)
>> Jun 22 08:16:58 pfdhcplistener(3459) INFO: pfdhcplistener_eth0 starting and
>> writing 3479 to /usr/local/pf/var/run/pfdhcplistener_eth0.pid
>> (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3479) WARN: Unable to open VLAN proc
>> description for eth0: No such file or directory (pf::util::get_vlan_from_int)
>> Jun 22 08:16:58 pfdhcplistener(3479) INFO: DHCP detector on eth0 enabled
>> (main::)
>> Jun 22 08:16:58 pfdhcplistener(3475) FATAL: Unable to initiate packet
>> capture. Is eth0.10 an actual network interface? (main::dhcp_detector)
>> Jun 22 08:16:58 pfdhcplistener(3475) INFO: stopping pfdhcplistener for
>> interface eth0.10 (main::END)
>>
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: Unseen before node added:
>> 00:25:22:18:67:96 (main::listen_dhcp)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: DHCPREQUEST from
>> 00:25:22:18:67:96 (10.2.1.44) (main::parse_dhcp_request)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: could not resolve 10.2.1.44 to
>> mac in ARP table (pf::iplog::ip2macinarp)
>> Jun 22 08:19:12 pfdhcplistener(3479) WARN: could not resolve 10.2.1.44 to
>> mac (pf::iplog::ip2mac)
>> Jun 22 08:19:12 pfdhcplistener(3479) WARN: unable to resolve
>> 00:25:22:18:67:96 to ip (pf::iplog::mac2ip)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: 00:25:22:18:67:96 requested an
>> IP. DHCP Fingerprint: OS::100 (Microsoft Windows XP). Modified node with
>> last_dhcp = 2013-06-22 08:19:12,computername =
>> ecs-afb570b54bc,dhcp_fingerprint = 1,15,3,6,44,46,47,31,33,249,43
>> (main::listen_dhcp)
>>
>> on running the command more packetfence.log..
>>
>> Jun 22 08:02:43 pfcmd.pl(2195) INFO: Executing pfcmd service pf start
>> (main::service)
>> Jun 22 08:02:43 pfcmd.pl(2195) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:02:43 pfcmd.pl(2195) FATAL: unable to connect to database: Can't
>> connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
>> at /usr/local/pf/lib/pf/person.pm line 77
>> (pf::db::db_connect)
>> Jun 22 08:16:16 pfcmd.pl(3215) INFO: Executing pfcmd service pf start
>> (main::service)
>> Jun 22 08:16:16 pfcmd.pl(3215) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:16 pfcmd.pl(3215) FATAL: unable to connect to database: Can't
>> connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
>> at /usr/local/pf/lib/pf/person.pm line 77
>> (pf::db::db_connect)
>> Jun 22 08:16:44 pfcmd.pl(3394) INFO: Executing pfcmd service pf start
>> (main::service)
>> Jun 22 08:16:44 pfcmd.pl(3394) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/named status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x named returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/dhcpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x dhcpd returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/snort status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x snort returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/bin/suricata status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x suricata returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/radiusd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x radiusd returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/httpd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/sbin/snmptrapd status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x snmptrapd returned 9832
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfdetect status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x pfdetect returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfsetvlan status
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: pidof -x pfsetvlan returned 9842
>> (pf::services::service_ctl)
>> Jun 22 08:16:46 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfdhcplistener
>> status (pf::services::service_ctl)
>> Jun 22 08:16:47 pfcmd.pl(3394) INFO: pfdhcplistener pids eth0.20 => ,
>> eth0.10 => , eth0 => (pf::services::service_ctl)
>> Jun 22 08:16:47 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfmon status
>> (pf::services::service_ctl)
>> Jun 22 08:16:47 pfcmd.pl(3394) INFO: pidof -x pfmon returned 0
>> (pf::services::service_ctl)
>> Jun 22 08:16:47 pfcmd.pl(3394) INFO: called reload_violation_config
>> (pf::config::cached::reload_violation_config)
>> Jun 22 08:16:47 pfcmd.pl(3394) INFO: called file_reload_violation_config
>> (pf::config::cached::file_reload_violation_config)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Instantiate a new iptables modification
>> method. pf::ipset (pf::inline::get_technique)
>> Jun 22 08:16:55 pfcmd.pl(3394) WARN: We are using IPSET
>> (pf::ipset::iptables_generate)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: flushing iptables
>> (pf::ipset::iptables_flush_mangle)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: restoring iptables from
>> /usr/local/pf/var/conf/iptables.conf (pf::iptables::iptables_restore)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: /usr/sbin/named start
>> (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Generating configuration file for named
>> (generate_named_conf) (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Starting named with '/usr/sbin/named -u
>> pf -c /usr/local/pf/var/conf/named.conf' (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Starting named with '/usr/sbin/named -u
>> pf -c /usr/local/pf/var/conf/named.conf' (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Daemon named took 0.081 seconds to
>> start. (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: /usr/sbin/dhcpd start
>> (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Generating configuration file for dhcpd
>> (generate_dhcpd_conf) (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Starting dhcpd with 'sudo
>> /usr/sbin/dhcpd -lf /usr/local/pf/var/dhcpd/dhcpd.leases -cf
>> /usr/local/pf/var/conf/dhcpd.conf -pf /usr/local/pf/var/run/dhcpd.pid eth
>> 0.10 eth0.20' (pf::services::service_ctl)
>> Jun 22 08:16:55 pfcmd.pl(3394) INFO: Starting dhcpd with 'sudo
>> /usr/sbin/dhcpd -lf /usr/local/pf/var/dhcpd/dhcpd.leases -cf
>> /usr/local/pf/var/conf/dhcpd.conf -pf /usr/local/pf/var/run/dhcpd.pid eth
>> 0.10 eth0.20' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon dhcpd took 0.093 seconds to
>> start. (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/sbin/snort start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: snort (/usr/sbin/snort) not started
>> because it's not required based on configuration (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/bin/suricata start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: suricata (/usr/bin/suricata) not
>> started because it's not required based on configuration
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/sbin/radiusd start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Generating configuration file for
>> radiusd (generate_radiusd_conf) (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting radiusd with 'sudo
>> /usr/sbin/radiusd -d /usr/local/pf/raddb/' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting radiusd with 'sudo
>> /usr/sbin/radiusd -d /usr/local/pf/raddb/' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon radiusd took 0.566 seconds to
>> start. (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfdetect start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: pfdetect (/usr/local/pf/sbin/pfdetect)
>> not started because it's not required based on configuration
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfdhcplistener start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting pfdhcplistener with 'sudo
>> /usr/local/pf/sbin/pfdhcplistener -i eth0.20 -d &'
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon pfdhcplistener took 0.003
>> seconds to start. (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting pfdhcplistener with 'sudo
>> /usr/local/pf/sbin/pfdhcplistener -i eth0.10 -d &'
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon pfdhcplistener took 0.003
>> seconds to start. (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting pfdhcplistener with 'sudo
>> /usr/local/pf/sbin/pfdhcplistener -i eth0 -d &' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon pfdhcplistener took 0.004
>> seconds to start. (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: /usr/local/pf/sbin/pfmon start
>> (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting pfmon with
>> '/usr/local/pf/sbin/pfmon -d &' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Starting pfmon with
>> '/usr/local/pf/sbin/pfmon -d &' (pf::services::service_ctl)
>> Jun 22 08:16:56 pfcmd.pl(3394) INFO: Daemon pfmon took 0.003 seconds to
>> start. (pf::services::service_ctl)
>> Jun 22 08:16:58 pfmon(0) INFO: pfmon starting and writing 3468 to
>> /usr/local/pf/var/run/pfmon.pid (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3453) INFO: pfdhcplistener_eth0.20 starting
>> and writing 3469 to /usr/local/pf/var/run/pfdhcplistener_eth0.20.pid
>> (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3469) WARN: Unable to open VLAN proc
>> description for eth0.20: No such file or directory
>> (pf::util::get_vlan_from_int)
>> Jun 22 08:16:58 pfdhcplistener(3469) INFO: DHCP detector on eth0.20 enabled
>> (main::)
>> Jun 22 08:16:58 pfmon(1) INFO: Starting cleanup thread (main::cleanup)
>> Jun 22 08:16:58 pfdhcplistener(3469) FATAL: Unable to initiate packet
>> capture. Is eth0.20 an actual network interface? (main::dhcp_detector)
>> Jun 22 08:16:58 pfdhcplistener(3469) INFO: stopping pfdhcplistener for
>> interface eth0.20 (main::END)
>> Jun 22 08:16:58 pfdhcplistener(3458) INFO: pfdhcplistener_eth0.10 starting
>> and writing 3475 to /usr/local/pf/var/run/pfdhcplistener_eth0.10.pid
>> (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3475) WARN: Unable to open VLAN proc
>> description for eth0.10: No such file or directory
>> (pf::util::get_vlan_from_int)
>> Jun 22 08:16:58 pfdhcplistener(3475) INFO: DHCP detector on eth0.10 enabled
>> (main::)
>> Jun 22 08:16:58 pfdhcplistener(3459) INFO: pfdhcplistener_eth0 starting and
>> writing 3479 to /usr/local/pf/var/run/pfdhcplistener_eth0.pid
>> (pf::util::createpid)
>> Jun 22 08:16:58 pfdhcplistener(3479) WARN: Unable to open VLAN proc
>> description for eth0: No such file or directory (pf::util::get_vlan_from_int)
>> Jun 22 08:16:58 pfdhcplistener(3479) INFO: DHCP detector on eth0 enabled
>> (main::)
>> Jun 22 08:16:58 pfdhcplistener(3475) FATAL: Unable to initiate packet
>> capture. Is eth0.10 an actual network interface? (main::dhcp_detector)
>> Jun 22 08:16:58 pfdhcplistener(3475) INFO: stopping pfdhcplistener for
>> interface eth0.10 (main::END)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: Unseen before node added:
>> 00:25:22:18:67:96 (main::listen_dhcp)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: DHCPREQUEST from
>> 00:25:22:18:67:96 (10.2.1.44) (main::parse_dhcp_request)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: could not resolve 10.2.1.44 to
>> mac in ARP table (pf::iplog::ip2macinarp)
>> Jun 22 08:19:12 pfdhcplistener(3479) WARN: could not resolve 10.2.1.44 to
>> mac (pf::iplog::ip2mac)
>> Jun 22 08:19:12 pfdhcplistener(3479) WARN: unable to resolve
>> 00:25:22:18:67:96 to ip (pf::iplog::mac2ip)
>> Jun 22 08:19:12 pfdhcplistener(3479) INFO: 00:25:22:18:67:96 requested an
>> IP. DHCP Fingerprint: OS::100 (Microsoft Windows XP). Modified node with
>> last_dhcp = 2013-06-22 08:19:12,computername = ecs
>> -afb570b54bc,dhcp_fingerprint = 1,15,3,6,44,46,47,31,33,249,43
>> (main::listen_dhcp)
>> Jun 22 08:25:58 pfmon(1) INFO: running expire check (main::cleanup)
>> Jun 22 08:25:58 pfmon(1) INFO: checking registered nodes for expiration
>> (main::cleanup)
>> Jun 22 08:25:58 pfmon(1) INFO: checking violations for expiration
>> (main::cleanup)
>> Jun 22 08:25:58 pfmon(1) INFO: checking accounting data for potential
>> bandwidth abuse (main::cleanup)
>> Jun 22 08:25:58 pfmon(1) INFO: getting violations triggers for accounting
>> cleanup (pf::accounting::acct_maintenance)
>> Jun 22 08:25:58 pfmon(1) INFO: Calling node acct maintenance total with
>> monthly and 1 for 21474836480 (pf::accounting::acct_maintenance)
>>
>>
>> [root@localhost logs]# tail -f catalyst.log
>> | Action | Time |
>> +------------------------------------------------------------+-----------+
>> | /graph/begin | 0.000165s |
>> | /graph/auto | 0.001902s |
>> | /graph/registered | 0.004712s |
>> | /end | 0.070655s |
>> | -> pfappserver::View::JSON->process | 0.070156s |
>> '------------------------------------------------------------+-----------'
>>
>> (Catalyst::finalize)
>>
>> on running the command more catalyst.log it only shows for 21st June.
>> (Catalyst::finalize)
>> Jun 21 12:26:54 httpd.admin(0) INFO: *** Request 6 (0.005/s) [14333] [Fri
>> Jun 21 12:26:54 2013] *** (Catalyst::__ANON__)
>> Jun 21 12:26:54 httpd.admin(0) INFO: Request took 0.142056s (7.039/s)
>> .------------------------------------------------------------+-----------.
>> | Action | Time |
>> +------------------------------------------------------------+-----------+
>> | /graph/begin | 0.000201s |
>> | /graph/auto | 0.030252s |
>> | /graph/dashboard | 0.101402s |
>> | /end | 0.003528s |
>> | -> pfappserver::View::HTML->process | 0.003033s |
>> '------------------------------------------------------------+-----------'
>>
>> (Catalyst::finalize)
>> Jun 21 12:26:54 httpd.admin(0) INFO: *** Request 7 (0.006/s) [14333] [Fri
>> Jun 21 12:26:54 2013] *** (Catalyst::__ANON__)
>> Jun 21 12:26:54 httpd.admin(0) INFO: Request took 0.084106s (11.890/s)
>> .------------------------------------------------------------+-----------.
>> | Action | Time |
>> +------------------------------------------------------------+-----------+
>> | /graph/begin | 0.000165s |
>> | /graph/auto | 0.001902s |
>> | /graph/registered | 0.004712s |
>> | /end | 0.070655s |
>> | -> pfappserver::View::JSON->process | 0.070156s |
>> '------------------------------------------------------------+-----------'
>>
>> (Catalyst::finalize)
>>
>> Kind Regards,
>> Frank Muriuki
>>
>> From: Derek Wuelfrath <[email protected]>
>> To: [email protected]
>> Sent: Friday, June 21, 2013 11:37 PM
>> Subject: Re: [PacketFence-users] PacketFence: Interfaces & Networks
>> Configuration Disappear on Restart
>>
>> Please send packetfence.log and catalyst.log files.
>> Thanks
>>
>> Cheers!
>> dw.
>>
>> --
>> [email protected] :: +1.514.447.4918 (x110) :: www.inverse.ca
>> Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
>> (www.packetfence.org)
>>
>> On 2013-06-21, at 5:58 AM, frank muriuki <[email protected]> wrote:
>>
>> Hi Fabrice,
>>
>> I carried the same installation on CentOS. I was successful in loading
>> https://@ip_of_packetfence:1443/configurator and carrying out the basic
>> configuration. However on rebooting the server the configuration on the
>> interfaces disappear and i'm also not able to run the url for the GUI.
>>
>> I'm able to start packetfence service but can't access it via Web.
>>
>> What do you think would be the problem.
>>
>> Regards,
>> Frank
>>
>>
>> From: frank muriuki <[email protected]>
>> To: "[email protected]"
>> <[email protected]>
>> Sent: Friday, June 21, 2013 8:04 AM
>> Subject: Re: [PacketFence-users] PacketFence: Interfaces & Networks
>> Configuration Disappear on Restart
>>
>> Hi Fabrice,
>>
>> Thanks for your response. I am using Packet Fence Version 4.0.1. I have
>> however decided to try CentOS linux and see if i end up getting the same
>> problem. I'll confirm on the same.
>>
>> If could kindly clarify what normal vlan, registration vlan, isolation vlan
>> and mac-detection vlan should be. Currently the users are on vlan 201 that
>> provides them access to data & internet. What vlan are users meant to be set
>> in at the switch?
>>
>> Kind Regards,
>> Frank
>>
>>
>> From: Fabrice DURAND <[email protected]>
>> To: [email protected]
>> Sent: Thursday, June 20, 2013 3:25 PM
>> Subject: Re: [PacketFence-users] PacketFence: Interfaces & Networks
>> Configuration Disappear on Restart
>>
>> Hello Frank,
>> what version of packetfence do you use ?
>> Because in the devel version a perl module was missing.
>>
>> Regards
>> Fabrice
>>
>> Le 2013-06-19 11:36, frank muriuki a écrit :
>>> Hi,
>>>
>>> I am experiencing some strange behavior in PacketFence configuration.
>>>
>>> I have installed packetfence in Ubuntu 12.10. Everytime i restart the Ubuntu
>>> server the settings/configuration i had made under interfaces & networks
>>> disappear. On the linux box it shows no ip defined on the sub-interfaces; i
>>> have to keep on re-configuring. Anyone with idea on how to resolve this?
>>>
>>> root <at> ecsnacsvr:~# ifconfig
>>> eth0 Link encap:Ethernet HWaddr e8:39:35:39:c1:eb
>>> inet addr:10.10.0.10 Bcast:10.10.0.15 Mask:255.255.255.240
>>> inet6 addr: fe80::ea39:35ff:fe39:c1eb/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:11961 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:1191641 (1.1 MB) TX bytes:45370 (45.3 KB)
>>>
>>> eth0.10 Link encap:Ethernet HWaddr e8:39:35:39:c1:eb
>>> inet6 addr: fe80::ea39:35ff:fe39:c1eb/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:4176 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:196380 (196.3 KB) TX bytes:3810 (3.8 KB)
>>>
>>> eth0.20 Link encap:Ethernet HWaddr e8:39:35:39:c1:eb
>>> inet6 addr: fe80::ea39:35ff:fe39:c1eb/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:1021 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:54723 (54.7 KB) TX bytes:3810 (3.8 KB)
>>>
>>> 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:405 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:405 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:1017697 (1.0 MB) TX bytes:1017697 (1.0 MB)
>>>
>>> Regards,
>>> Frank
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Windows:
>>>
>>> Build for Windows Store.
>>>
>>> http://p.sf.net/sfu/windows-dev2dev
>>>
>>>
>>> _______________________________________________
>>> PacketFence-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>> --
>> Fabrice Durand
>> [email protected] :: +1.514.447.4918 (x135) :: www.inverse.ca
>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
>> (http://packetfence.org)
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
>> PacketFence-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
