File:  [ELWIX - Embedded LightWeight unIX -] / embedaddon / strongswan / conf / plugins / dhcp.opt
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Wed Jun 3 09:46:43 2020 UTC (5 years, 6 months ago) by misho
Branches: strongswan, MAIN
CVS tags: v5_9_2p0, v5_8_4p7, HEAD
Strongswan

    1: charon.plugins.dhcp.force_server_address = no
    2: 	Always use the configured server address.
    3: 
    4: 	Always use the configured server address. This might be helpful if the DHCP
    5: 	server runs on the same host as strongSwan, and the DHCP daemon does not
    6: 	listen on the loopback interface.  In that case the server cannot be reached
    7: 	via unicast (or even 255.255.255.255) as that would be routed via loopback.
    8: 	Setting this option to yes and configuring the local broadcast address (e.g.
    9: 	192.168.0.255) as server address might work.
   10: 
   11: charon.plugins.dhcp.identity_lease = no
   12: 	Derive user-defined MAC address from hash of IKE identity and send client
   13: 	identity DHCP option.
   14: 
   15: charon.plugins.dhcp.server = 255.255.255.255
   16: 	DHCP server unicast or broadcast IP address.
   17: 
   18: charon.plugins.dhcp.use_server_port = no
   19: 	Use the DHCP server port (67) as source port when a unicast server address
   20: 	is configured.
   21: 
   22: 	Use the DHCP server port (67) as source port, instead of the DHCP client
   23: 	port (68), when a unicast server address is configured and the plugin acts
   24: 	as relay agent.  When replying in this mode the DHCP server will always send
   25: 	packets to the DHCP server port and if no process binds that port an ICMP
   26: 	port unreachables will be sent back, which might be problematic for some
   27: 	DHCP servers.  To avoid that, enabling this option will cause the plugin to
   28: 	bind the DHCP server port to send its requests when acting as relay agent.
   29: 	This is not necessary if a DHCP server is already running on the same host
   30: 	and might even cause conflicts (and since the server port is already bound,
   31: 	ICMPs should not be an issue).
   32: 
   33: charon.plugins.dhcp.interface
   34: 	Interface name the plugin uses for address allocation.
   35: 
   36: 	Interface name the plugin uses for address allocation. The default is to
   37: 	bind to any (0.0.0.0) and let the system decide which way to route the
   38: 	packets to the DHCP server.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>