[Kea-users] perfdhcp doubt

Fernando Ruza Rodriguez fernandor at sescam.jccm.es
Thu May 16 07:51:29 UTC 2019


Hi!

I'm doing some test with perfdhcp and I don't understand some things.
For example, I'm sending just one broadcast request with the following
command:

# perfdhcp -4 -b mac=fb:01:00:00:00:00 -R 1 -r 1 -n 1 -l ens256 -B
Running: perfdhcp -4 -b mac=fb:01:00:00:00:00 -R 1 -r 1 -n 1 -l ens256
-B
***Rate statistics***
Rate: 0.499512 4-way exchanges/second, expected rate: 1

***Statistics for: DISCOVER-OFFER***
sent packets: 1
received packets: 1
drops: 0

min delay: 30.692 ms
avg delay: 30.692 ms
max delay: 30.692 ms
std deviation: 0.000 ms
collected packets: 0

***Statistics for: REQUEST-ACK***
sent packets: 1
received packets: 1
drops: 0

min delay: 125.574 ms
avg delay: 125.574 ms
max delay: 125.574 ms
std deviation: 0.000 ms
collected packets: 0

The request is collected with a dhcp relay and send it to the kea dhcp
server which replying to the request. Why in a tcpdump in the kea dhcp
server I see so many Requests and Replys?, exactly 18:

09:13:04.762748 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762783 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762789 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762792 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762804 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762807 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762811 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762818 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.762823 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 262
09:13:04.788927 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.793097 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793127 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793133 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793139 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793145 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793150 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793154 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793159 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.793165 IP 192.168.100.1.bootps > 1.60.10.25.bootps: BOOTP/DHCP,
Request from fb:01:00:00:00:00, length 274
09:13:04.802209 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.819024 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.834386 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.850156 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.866358 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.882575 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.891431 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.897923 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.917773 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.938934 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.959246 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.972315 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.983266 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:04.995680 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:05.007024 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:05.021825 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299
09:13:05.035751 IP 192.168.100.6.bootps > 192.1.0.2.bootps: BOOTP/DHCP,
Reply, length 299

Many thanks for any answer.

Regards, Fernando.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20190516/7241ee6c/attachment.html>


More information about the Kea-users mailing list