Hi all,
>> On Dec 14, 2015, at 3:37 , Mathieu Dirkx <[email protected]> wrote:
>>
>> 2. Can't bind : IO::Socket::INET: connect: Interrupted system call
>> 3. Can't bind : IO::Socket::INET: connect: Connection refused
>
>These look to me like failing OMAPI calls to the dhcpd daemon.
>
>That is odd because it’s a local service which PacketFence controls, so it’s
>worth looking into.
>
>Can you post your var/conf/dhcpd.conf and conf/networks.conf please?
---------------
/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;
# OMAPI for IP <-> MAC lookup
omapi-port 7911;
key pf_omapi_key {
algorithm HMAC-MD5;
secret "Q0WLBNJE4F+FWp8E/gUYrA7CrMz9yNPetwn0JPl/O8Q=";
};
omapi-key pf_omapi_key;
--------------------
/usr/local/pf/conf/networks.conf
--------------------
subnet 172.31.52.0 netmask 255.255.255.0 {
option routers 172.31.52.9;
option subnet-mask 255.255.255.0;
option domain-name "vlan-registration.piusx-college.nl";
option domain-name-servers 172.31.52.9;
range 172.31.52.12 172.31.52.254;
default-lease-time 300;
max-lease-time 86400;
}
subnet 172.31.54.0 netmask 255.255.254.0 {
option routers 172.31.54.9;
option subnet-mask 255.255.254.0;
option domain-name "vlan-isolation.piusx-college.nl";
option domain-name-servers 172.31.54.9;
range 172.31.54.12 172.31.55.254;
default-lease-time 30;
max-lease-time 30;
}
--------------------
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
