Hello, I'm no expert in this particular subject, but you might check tcpdump while a client tries to obtain a DHCP address. Maybe the switch you use is filling arp tables or something..
Bebbet On 28-5-2016 21:05, mj wrote: > Hi, > > No replies, so I'm posting it again. We're just looking for some feedback... > > We have complaints that (during peak hours) users have difficulties > connecting to our packetfence 5.6.1 system, inline mode, running on > debian 7. > > Here is our email from two days ago again: > > 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. > > When the client tries again a fourth time: >> May 23 17:08:20 T430s dhclient: DHCPREQUEST of 10.19.227.120 on eth0 to >> 255.255.255.255 port 67 (xid=0x399c2476) > THEN 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? (should we check different logfiles, perhaps?) > > Are we on to something, or are we looking in the wrong files..? (or > misunderstanding packetfence workings..?) > > Is there a maximum number of dhcp requests packetfence can handle..? > (we're talking perhaps 200 clients inline, that's not too much, I guess..?) > > Feedback would be appreciated! > > MJ > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
