From 496137b84b791f11b6d5260d09550e7e445ede7a Mon Sep 17 00:00:00 2001 From: Olivier Gayot Date: Mon, 21 Nov 2016 15:25:46 +0100 Subject: Added article about netctl undocumented features. Signed-off-by: Olivier Gayot --- posts/netctl-undocumented-features.rst | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 posts/netctl-undocumented-features.rst (limited to 'posts') diff --git a/posts/netctl-undocumented-features.rst b/posts/netctl-undocumented-features.rst new file mode 100644 index 0000000..a52b124 --- /dev/null +++ b/posts/netctl-undocumented-features.rst @@ -0,0 +1,28 @@ +.. title: Netctl undocumented features +.. slug: netctl-undocumented-features +.. date: 2016-11-21 15:08:18 UTC+01:00 +.. tags: +.. link: +.. description: There are undocumented features in Netctl. +.. type: text + +I use netctl to configuration my network interfaces. While some features seem +to be missing, here is a list of some useful features that are supported by the +tool but not documented: + +Passing options to your DHCP client +----------------------------------- + +Although currently, only **dhclient** and **dhcpcd** are officially supported, +it still seems quite a pain to pass them custom parameters without using the +environment. + +Some people suggest to use the **DHCPClient** variable to pass the name of the +binary along with their options. + +Nonetheless, it is possible to use the variables **DhcpcdOptions** or +**DhclientOptions**. + +Example (here, we pass a custom hostname and a custom metric to **dhcpcd**:: + + > DhcpcdOptions='-H hostname -m metric' -- cgit v1.2.3