From: Roy Marples <roy@marples.name>
Date: Wed, 30 Mar 2016 07:08:34 +0000 (+0000)
Subject: Describe how hardware based arping profiles work.
X-Git-Tag: v6.10.2~18
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a6162a7534b0f5f644da5d9f7b91e39207c7902b;p=thirdparty%2Fdhcpcd.git

Describe how hardware based arping profiles work.
---

diff --git a/dhcpcd.conf.5.in b/dhcpcd.conf.5.in
index f0a2da14..a4bb7f47 100644
--- a/dhcpcd.conf.5.in
+++ b/dhcpcd.conf.5.in
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd February 15, 2016
+.Dd March 30, 2016
 .Dt DHCPCD.CONF 5
 .Os
 .Sh NAME
@@ -67,8 +67,13 @@ Example:
 .D1 interface bge0
 .D1 arping 192.168.0.1
 .Pp
-.D1 profile 192.168.0.1
+.D1 # My specific 192.168.0.1 network
+.D1 profile dd:ee:aa:dd:bb:ee
 .D1 static ip_address=192.168.0.10/24
+.Pp
+.D1 # A generic 192.168.0.1 network
+.D1 profile 192.168.0.1
+.D1 static ip_address=192.168.0.98/24
 .It Ic authprotocol Ar protocol Ar algorithm Ar rdm
 Authenticate DHCP messages.
 See the Supported Authentication Protocols section.