dhcp: Only use DHCP server port if explicitly configured
If a DHCP server is running on the same host it isn't necessary to bind the server port and might even cause conflicts.
This commit is contained in:
@@ -15,6 +15,21 @@ charon.plugins.dhcp.identity_lease = no
|
||||
charon.plugins.dhcp.server = 255.255.255.255
|
||||
DHCP server unicast or broadcast IP address.
|
||||
|
||||
charon.plugins.dhcp.use_server_port = no
|
||||
Use the DHCP server port (67) as source port when a unicast server address
|
||||
is configured.
|
||||
|
||||
Use the DHCP server port (67) as source port, instead of the DHCP client
|
||||
port (68), when a unicast server address is configured and the plugin acts
|
||||
as relay agent. When replying in this mode the DHCP server will always send
|
||||
packets to the DHCP server port and if no process binds that port an ICMP
|
||||
port unreachables will be sent back, which might be problematic for some
|
||||
DHCP servers. To avoid that, enabling this option will cause the plugin to
|
||||
bind the DHCP server port to send its requests when acting as relay agent.
|
||||
This is not necessary if a DHCP server is already running on the same host
|
||||
and might even cause conflicts (and since the server port is already bound,
|
||||
ICMPs should not be an issue).
|
||||
|
||||
charon.plugins.dhcp.interface
|
||||
Interface name the plugin uses for address allocation.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user