Hi, We have a strange problem: packetfence inline on a HP Procurve 5412 chassis.
We have occasional problems with devices that cannot connect. The logs on the clientdevice indicate that client dhcp is trying to obtain an address: > May 23 17:07:56 T430s dhclient: DHCPREQUEST of 10.19.227.120 on eth0 to > 255.255.255.255 port 67 (xid=0x70d4fac) > May 23 17:08:02 T430s dhclient: DHCPREQUEST of 10.19.227.120 on eth0 to > 255.255.255.255 port 67 (xid=0x762d63ef) > May 23 17:08:17 T430s dhclient: DHCPREQUEST of 10.19.227.120 on eth0 to > 255.255.255.255 port 67 (xid=0x399c2476) However: NONE of the above requests are logged in the pfdhcplistener.log file. THEN the client tries again the same: > May 23 17:08:20 T430s dhclient: DHCPREQUEST of 10.19.227.120 on eth0 to 255.255.255.255 port 67 (xid=0x399c2476) and suddenly this request IS detected and logged in pfdhcplistener.log: > May 23 17:08:20 pfqueue(21972) INFO: [mac:unknown] DHCPREQUEST from > 3c:97:0e:2f:14:f8 (10.19.227.120) (pf::dhcp::processor::parse_dhcp_request) > May 23 17:08:22 pfqueue(21972) INFO: [mac:3c:97:0e:2f:14:f8] > 3c:97:0e:2f:14:f8 requested an IP with the following informations: last_dhcp > = 2016-05-23 17:08:20,computername = T430s,dhcp_fingerprint = > 1,28,2,3,15,6,119,12,44,47,26,121,42,121,249,33,252,42,dhcp_vendor = > (pf::dhcp::processor::process_packet) and this request is also answered, and my client can connect: > May 23 17:08:21 T430s dhclient: DHCPACK of 10.19.227.120 from 10.19.0.1 > May 23 17:08:21 T430s dhclient: bound to 10.19.227.120 -- renewal in 7226165 > seconds. Our question: Is it expected that so many requests (we have more examples like this) go 'unnoticed' in pfdhcplistener.log, and also seem to be left unanswered? We have complaints that (during peak hours) users have difficulties connecting to our system. Are we on to something, or are we looking in the wrong files..? (or misunderstanding packetfence workings..?) Any feedback would be appreciated! MJ ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
