• Print
  • Share
  • Dark

I set up a firewall, but the Kea server still receives packets. Why?

  • Updated on 08 Nov 2018
  • 1 minute to read
  • Contributors

Any DHCPv4 server must be able to receive from and send traffic to hosts that don't have an IPv4 address assigned yet. That is typically not possible with regular UDP sockets; therefore, the Kea DHCPv4 server uses raw sockets by default. Raw sockets mean that the incoming packets are received as raw Ethernet frames, thus bypassing the whole kernel IP stack, including any firewalling rules your kernel may provide.

If you do not want the server to use raw sockets, it is possible to configure the Kea DHCPv4 server to use UDP sockets instead. See the command dhcp-socket-type described in the dhcp4-interface-configuration section of the User Guide.

Using UDP sockets has certain limitations. In particular, they may not allow for sending responses directly to clients without IPv4 addresses assigned. That's not a problem, if all your traffic is coming through relay agents.

Was this article helpful?