]> git.ipfire.org Git - thirdparty/dhcpcd.git/commitdiff
Describe how hardware based arping profiles work.
authorRoy Marples <roy@marples.name>
Wed, 30 Mar 2016 07:08:34 +0000 (07:08 +0000)
committerRoy Marples <roy@marples.name>
Wed, 30 Mar 2016 07:08:34 +0000 (07:08 +0000)
dhcpcd.conf.5.in

index f0a2da147aafac6c20a21234e541c45705cfe069..a4bb7f47afbd1c50b24474d78bbcb4e1289a5dda 100644 (file)
@@ -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.