dhcpcd.git/dhcpcd.8.in, branch dhcpcd-5.0.1 DHCP / IPv4LL / IPv6RA / DHCPv6 client Add (c) to Copyright 2009-05-01T13:57:45+00:00 Roy Marples roy@marples.name 2009-05-01T13:57:45+00:00 601fb3d500ffb57f5ce6eb584c0c481df7870589 






dhcpcd -V now shows all variables we set, even without an option.
2009-04-24T16:48:35+00:00

Roy Marples
roy@marples.name

2009-04-24T16:48:35+00:00

79262fbb6d6798bea47fd4c64a50cad11e18d3f0












Default point to point interfaces to static if not inform.
2009-03-23T20:10:02+00:00

Roy Marples
roy@marples.name

2009-03-23T20:10:02+00:00

a43ccb9f89972786e75b2140edf109af72bd8467

Only accept inform replies from our destination address.






Only accept inform replies from our destination address.








Clarify reconfigure regarding the configuration file.
2009-03-20T15:33:31+00:00

Roy Marples
roy@marples.name

2009-03-20T15:33:31+00:00

a6a83b8352328a03e20f4b322b8dc0ab7df193b4












Add an option to reconfigure dhcpcd without rebinding.
2009-03-20T10:21:12+00:00

Roy Marples
roy@marples.name

2009-03-20T10:21:12+00:00

373e6ce084d5a03c07ddf11ddfc380b4da34fb1b

This is primarily for interaction with 3rd party link management, such as PPP.
More work on #159.






This is primarily for interaction with 3rd party link management, such as PPP.
More work on #159.








We can now detected primary addresses added or changed in BSD.
2009-03-19T17:52:12+00:00

Roy Marples
roy@marples.name

2009-03-19T17:52:12+00:00

1abffd5ba55b4e4a2a149001a33349ef39139457

As such, we can wait for a 3RDPARTY to configure the interface, such as PPP.
We can then take the destination addess and automatically give it a default
route or any other DHCP option such as DNS servers.
This addresses #159.






As such, we can wait for a 3RDPARTY to configure the interface, such as PPP.
We can then take the destination addess and automatically give it a default
route or any other DHCP option such as DNS servers.
This addresses #159.








mandoc mandates the presence of .Os
2009-03-11T17:57:10+00:00

Roy Marples
roy@marples.name

2009-03-11T17:57:10+00:00

918338f28048ad570ce0fcaf148d05c2bde26ed2












We need to blacklist IP addresses at the packet level
2009-03-10T17:28:18+00:00

Roy Marples
roy@marples.name

2009-03-10T17:28:18+00:00

ce6b39df64069a367cf62fd2bf450613ea54fc1a

so we can ignore NAKs from rogue servers who don't
supply a ServerID, or supply a fake one.




so we can ignore NAKs from rogue servers who don't
supply a ServerID, or supply a fake one.






Blacklist now accepts networks as well as addresses.
2009-02-27T21:18:01+00:00

Roy Marples
roy@marples.name

2009-02-27T21:18:01+00:00

e095a6ebb581216ef8369d1e468a6682332498a7

It also matches on the address offered as well as the server address.





It also matches on the address offered as well as the server address.







Typo
2009-02-26T16:16:57+00:00

Roy Marples
roy@marples.name

2009-02-26T16:16:57+00:00

f68268b72b6372fd3c0ba2be78cbecbe8ceab98c