Added article about netctl undocumented features.

Signed-off-by: Olivier Gayot <og@satcom1.com>

1 files changed, 28 insertions, 0 deletions

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'