| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
not allowed in domain names. RFC 2132 does not list valid or invalid
characters and the ISC client accepts anything here.
Reported by: ps
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
server options.
Reported by: Max Boyarov <max_b at tut dot by>
Approved by: re (dhclient blanket)
|
|
|
|
|
|
|
|
|
|
|
|
| |
include a space seperated list of domains instead of the domain of the
host. This is supported on too many platforms to break for now so,
remove validation of this option for the moment.
The correct solution longer term is to implement RFC 3397 support and
then treat domain-name options containing space seperated lists of
domains as domain-search options for backwards compatability.
Approved by: re (dhclient blanket)
|
|
|
|
|
|
|
|
| |
have an active one.
Submitted by: sam
Reported by: James Snow <snow at teardrop dot org>
Approved by: re (dhclient blanket)
|
|
|
|
|
|
|
|
| |
talking about time related to leases, it should be OK to cast these to
(int)s rather than using intmax_t.
Submitted by: ru
Pointy hat: brooks
|
|
|
|
|
|
|
|
|
| |
Add a -b option to background immediatly.
Add support for 802.11 routing messages to "instantly" renegotiate
at lease when we associate with a new network.
Submitted by: sam
|
|
OPENBSD_3_7).
|