Wrong client port in offer?!
perfdhcp -D 1024 -d 1024 -d 1024 -f 16 -L 12345 -l ens4 -n 1024 -n 1024 -r 16 -4 -R 4294967295 -W 0
on a back-to-back pair of interfaces with kea-dhcp4
, no relay involved. Notice the non-default port -L 12345
. perfdhcp
gets no response whatsoever. GDBed into the kea-dhcp4
, receives the query with remote_port_
12345
, but it populates the response's remote_port_
with 68
.
The -P
parameter on kea-dhcp4
's side could be used here, but what about a production situation?
I feel like I'm in the wrong cuz this would be detected quickly, but maybe nobody uses non-default ports for their clients and it also feels like perfdhcp
should get it's response. Help?