Looks good now. Thanks
Steve
On 22 January 2015 at 12:24, Durand fabrice <[email protected]> wrote:
> Hello,
>
> let´s do a : [root@packetfence ~]# /sbin/service packetfence status
>
> You will be able to see all the services managed by packetfence, and
> to manage a service by hand:
> /usr/local/pf/bin/pfcmd services dhcpd restart
> /usr/local/pf/bin/pfcmd services httpd.portal restart
> ....
>
>
> Regards
> Fabrice
>
> Le 2015-01-22 07:14, Steve Allen a écrit :
> > Hi
> >
> > I tried what you suggested but that did not seem to have any
> > affect.
> >
> > When I first set up the test server I did mess around with the
> > network settings so to rule this out I have just wiped the server
> > and installed a fresh copy of CentOS 6.6 (and updated).
> >
> > I've reinstalled PF and I seem to have the same issue.
> >
> > I was just about to start pasting my complete config when something
> > really simple hit me!
> >
> > My test laptops did not receive a DHCP IP address because my PF
> > server was plugged into an access port. I changed the port to a
> > trunk and it worked 1st time!
> >
> > I do have one question:
> >
> > [root@packetfence ~]# /sbin/service dhcpd status dhcpd is stopped
> > [root@packetfence ~]#
> >
> > I take it this is not a problem as Packetfence takes care of it
> > differently?
> >
> > Thanks for all your help.
> >
> > Steve
> >
> >
> >
> >
> > On 22 January 2015 at 01:43, Durand fabrice <[email protected]>
> > wrote:
> >
> >> Hello Steve,
> >>
> >> Fix the dns and gateway (cf bellow) and launch pfcmd service
> >> dhcpd restart Also check the generated dhcpd config file in
> >> /usr/local/pf/var/conf/dhcpd.conf
> >>
> >> If it´s not working then paste your pf.conf too.
> >>
> >>
> >> Regards Fabrice
> >>
> >> Le 2015-01-21 09:03, Steve Allen a écrit :
> >>> Hi
> >>>
> >>> Below is output from my networks and dhcpd config files.
> >>>
> >>> Thanks Steve
> >>>
> >>>
> >>> ====== */usr/local/pf/conf/networks.conf* ======
> >>> [192.168.20.0] dns=192.168.20.2 dhcp_start=192.168.20.10
> >>> gateway=192.168.20.2
> >>> domain-name=vlan-registration.testlab.local
> >>> nat_enabled=disabled named=enabled dhcp_max_lease_time=30
> >>> fake_mac_enabled=disabled dhcpd=enabled dhcp_end=192.168.20.246
> >>> type=vlan-registration netmask=255.255.255.0
> >>> dhcp_default_lease_time=30
> >>>
> >>> [192.168.30.0] dns=192.168.30.0
> >> wrong, probably dns=192.168.30.2
> >>> dhcp_start=192.168.30.10 gateway=192.168.30.0
> >> wrong, probably gatway=192.168.30.2
> >>> domain-name=vlan-isolation.testlab.local nat_enabled=disabled
> >>> named=enabled dhcp_max_lease_time=30 fake_mac_enabled=disabled
> >>> dhcpd=enabled dhcp_end=192.168.30.246 type=vlan-isolation
> >>> netmask=255.255.255.0 dhcp_default_lease_time=30 ~
> >>> =====================
> >>>
> >>>
> >>> ====== */usr/local/pf/var/conf/dhcpd.conf* ====== # This file
> >>> is generated from a template at /usr/local/pf/conf/dhcpd.conf #
> >>> Any changes made to this file will be lost on restart
> >>>
> >>> # dhcpd configuration # This file is manipulated on
> >>> PacketFence's startup before being given to dhcpd
> >>> authoritative; ddns-update-style none; ignore client-updates;
> >>> log-facility local6;
> >>>
> >>> subnet 192.168.30.0 netmask 255.255.255.0 { option routers
> >>> 192.168.30.0; option subnet-mask 255.255.255.0; option
> >>> domain-name "vlan-isolation.testlab.local"; option
> >>> domain-name-servers 192.168.30.0; range 192.168.30.10
> >>> 192.168.30.246; default-lease-time 30; max-lease-time 30; }
> >>>
> >>> subnet 192.168.20.0 netmask 255.255.255.0 { option routers
> >>> 192.168.20.2; option subnet-mask 255.255.255.0; option
> >>> domain-name "vlan-registration.testlab.local"; option
> >>> domain-name-servers 192.168.20.2; range 192.168.20.10
> >>> 192.168.20.246; default-lease-time 30; max-lease-time 30; }
> >>>
> >>>
> >>> ~ ===========================
> >>>
> >>> On 21 January 2015 at 13:35, Fabrice DURAND
> >>> <[email protected]> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> the dhcpd configuration file is in /usr/local/pf/var/conf.
> >>>>
> >>>> Also it look like an error in network configuration. Paste
> >>>> your netwroks.conf and we will check what is wrong.
> >>>>
> >>>> Regards Fabrice
> >>>>
> >>>> Le 2015-01-21 06:49, Steve Allen a écrit :
> >>>>> Hi
> >>>>>
> >>>>> I have recently installed Packetfence version 4.5.1 and
> >>>>> everything is going OK expect for DHCP on the registration
> >>>>> VLAN. I have ticked the box for the DHCP to be handled by
> >>>>> the PacketFence server but no joy. I can see from Cisco
> >>>>> switch debug and packetfence log messages that the port is
> >>>>> correctly being put in the registration VLAN.
> >>>>>
> >>>>> When troubleshooting DHCP on the Packetfence server
> >>>>> (CentOS 6.6) I can see the dhcpd service is failing to
> >>>>> start.
> >>>>>
> >>>>> Below is the output from log messages and the dhcpd.conf
> >>>>> file. It looks like nothing is being written to the
> >>>>> dhcpd.conf file, is this normal?
> >>>>>
> >>>>> Please could someone advise how this can be resolved?
> >>>>>
> >>>>> Kind regards, Steve
> >>>>>
> >>>>>
> >>>>> ====== *Service Status and Start* ====== [root@packetfence
> >>>>> ~]# /sbin/service dhcpd status dhcpd is stopped
> >>>>> [root@packetfence ~]# /sbin/service dhcpd start Starting
> >>>>> dhcpd: [FAILED] [root@packetfence ~]# ============
> >>>>>
> >>>>> ====== */var/log/messages* ====== Jan 21 12:44:03
> >>>>> packetfence dhcpd: Internet Systems Consortium DHCP Server
> >>>>> 4.1.1-P1 Jan 21 12:44:03 packetfence dhcpd: Copyright
> >>>>> 2004-2010 Internet Systems Consortium. Jan 21 12:44:03
> >>>>> packetfence dhcpd: All rights reserved. Jan 21 12:44:03
> >>>>> packetfence dhcpd: For info, please visit
> >>>>> https://www.isc.org/software/dhcp/ Jan 21 12:44:03
> >>>>> packetfence dhcpd: Not searching LDAP since ldap-server,
> >>>>> ldap-port and ldap-base-dn were not specified in the
> >>>>> config file Jan 21 12:44:03 packetfence dhcpd: Wrote 0
> >>>>> leases to leases file. Jan 21 12:44:03 packetfence dhcpd:
> >>>>> Jan 21 12:44:03 packetfence dhcpd: No subnet declaration
> >>>>> for eth0.30 (192.168.30.0). Jan 21 12:44:03 packetfence
> >>>>> dhcpd: ** Ignoring requests on eth0.30. If this is not what
> >>>>> Jan 21 12:44:03 packetfence dhcpd: you want, please
> >>>>> write a subnet declaration Jan 21 12:44:03 packetfence
> >>>>> dhcpd: in your dhcpd.conf file for the network segment
> >>>>> Jan 21 12:44:03 packetfence dhcpd: to which interface
> >>>>> eth0.30 is attached. ** Jan 21 12:44:03 packetfence dhcpd:
> >>>>> Jan 21 12:44:03 packetfence dhcpd: Jan 21 12:44:03
> >>>>> packetfence dhcpd: No subnet declaration for eth0.20
> >>>>> (192.168.20.2). Jan 21 12:44:03 packetfence dhcpd: **
> >>>>> Ignoring requests on eth0.20. If this is not what Jan 21
> >>>>> 12:44:03 packetfence dhcpd: you want, please write a
> >>>>> subnet declaration Jan 21 12:44:03 packetfence dhcpd: in
> >>>>> your dhcpd.conf file for the network segment Jan 21
> >>>>> 12:44:03 packetfence dhcpd: to which interface eth0.20
> >>>>> is attached. ** Jan 21 12:44:03 packetfence dhcpd: Jan 21
> >>>>> 12:44:03 packetfence dhcpd: Jan 21 12:44:03 packetfence
> >>>>> dhcpd: No subnet declaration for eth0 (192.168.10.2). Jan
> >>>>> 21 12:44:03 packetfence dhcpd: ** Ignoring requests on
> >>>>> eth0. If this is not what Jan 21 12:44:03 packetfence
> >>>>> dhcpd: you want, please write a subnet declaration Jan
> >>>>> 21 12:44:03 packetfence dhcpd: in your dhcpd.conf file for
> >>>>> the network segment Jan 21 12:44:03 packetfence dhcpd:
> >>>>> to which interface eth0 is attached. ** Jan 21 12:44:03
> >>>>> packetfence dhcpd: Jan 21 12:44:03 packetfence dhcpd: Jan
> >>>>> 21 12:44:03 packetfence dhcpd: Not configured to listen on
> >>>>> any interfaces! Jan 21 12:44:03 packetfence dhcpd: Jan 21
> >>>>> 12:44:03 packetfence dhcpd: This version of ISC DHCP is
> >>>>> based on the release available Jan 21 12:44:03 packetfence
> >>>>> dhcpd: on ftp.isc.org <http://ftp.isc.org>. Features have
> >>>>> been added and other changes Jan 21 12:44:03 packetfence
> >>>>> dhcpd: have been made to the base software release in order
> >>>>> to make Jan 21 12:44:03 packetfence dhcpd: it work better
> >>>>> with this distribution. Jan 21 12:44:03 packetfence dhcpd:
> >>>>> Jan 21 12:44:03 packetfence dhcpd: Please report for this
> >>>>> software via the CentOS Bugs Database: Jan 21 12:44:03
> >>>>> packetfence dhcpd: http://bugs.centos.org/ Jan 21
> >>>>> 12:44:03 packetfence dhcpd: Jan 21 12:44:03 packetfence
> >>>>> dhcpd: exiting. ============
> >>>>>
> >>>>> ====== */etc/dhcp/dhcpd.conf* ====== [root@packetfence ~]#
> >>>>> vi /etc/dhcp/dhcpd.conf # # DHCP Server Configuration file.
> >>>>> # see /usr/share/doc/dhcp*/dhcpd.conf.sample # see 'man
> >>>>> 5 dhcpd.conf' # ~ ~ ~ ~ ~ ~ ============
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>>>
> >>>>
> >>
> >>
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> >>>>> GigeNET is offering a free month of service with a new
> >>>>> server in Ashburn. Choose from 2 high performing configs,
> >>>>> both with 100TB of bandwidth. Higher redundancy.Lower
> >>>>> latency.Increased capacity.Completely compliant.
> >>>>> http://p.sf.net/sfu/gigenet
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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)
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>>>
> >>>>
> >>
> >>
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> >>>> GigeNET is offering a free month of service with a new server
> >>>> in Ashburn. Choose from 2 high performing configs, both with
> >>>> 100TB of bandwidth. Higher redundancy.Lower
> >>>> latency.Increased capacity.Completely compliant.
> >>>> http://p.sf.net/sfu/gigenet
> >>>> _______________________________________________
> >>>> PacketFence-users mailing list
> >>>> [email protected]
> >>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>>>
>
> ------------------------------------------------------------------------------
> >>>
> >>>
> >> New Year. New Location. New Benefits. New Data Center in Ashburn,
> >> VA.
> >>> GigeNET is offering a free month of service with a new server
> >>> in Ashburn. Choose from 2 high performing configs, both with
> >>> 100TB of bandwidth. Higher redundancy.Lower latency.Increased
> >>> capacity.Completely compliant. http://p.sf.net/sfu/gigenet
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> PacketFence-users mailing list
> >>> [email protected]
> >>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> >>>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >>
> >>
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> >> GigeNET is offering a free month of service with a new server in
> >> Ashburn. Choose from 2 high performing configs, both with 100TB
> >> of bandwidth. Higher redundancy.Lower latency.Increased
> >> capacity.Completely compliant. http://p.sf.net/sfu/gigenet
> >> _______________________________________________ PacketFence-users
> >> mailing list [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> >>
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> > GigeNET is offering a free month of service with a new server in
> > Ashburn. Choose from 2 high performing configs, both with 100TB of
> > bandwidth. Higher redundancy.Lower latency.Increased
> > capacity.Completely compliant. http://p.sf.net/sfu/gigenet
> >
> >
> >
> > _______________________________________________ PacketFence-users
> > mailing list [email protected]
> > https://lists.sourceforge.net/lists/listinfo/packetfence-users
> >
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
--
Regards,
Steve Allen
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
