| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
correct test to -ge 5. Without this change an RFC3442 encoded default
route would be ignored.
Reported by: Cedric Jonas <cedric at decemplex dot net>
|
|
|
|
|
|
|
|
|
|
|
| |
The original DHCP specification includes a route option but it supports
only class-based routes. RFC3442 adds support for specifying the netmask
width for each static route. A variable length encoding is used to minimize
the size of this option.
PR: bin/99534
Submitted by: Andrey V. Elsukov <bu7cher@yandex.ru>
Reviewed by: brooks
|
|
|
|
| |
file isn't actually installed; the one in src/etc is.
|
|
|
|
|
|
| |
were removing the invalid option, but still rejecting the lease.
Reported by: Yoshihiko Sarumaru <mistral at imasy dot or dot jp>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
length != BPF_WORDALIGN(length)
This meeans that it is possible for this to be true:
interface->rbuf_offset > interface->rbuf_len
Handle this case in the test for running out of packets. While
OpenBSD's solution of setting interface->rbuf_len to
BPF_WORDALIGN(length) is safe due to the size of the buffer, I think
this solution results in less hidden assumptions.
This should fix the problem of dhclient running away and consuming 100%
CPU.
PR: bin/102226
Submitted by: Joost Bekkers <joost at jodocus.org>
MFC after: 3 days
|
|
|
|
|
|
|
| |
on an interface without carrier. devd should be used instead to handle
link up/down events.
Put on the right path by: brooks, sam
|
|
|
|
| |
Suggested by: ru
|
| |
|
|
|
|
|
|
|
|
|
|
| |
despite the interface link status.
Add dhclient_flags_iface and background_dhclient_iface rc.conf options.
(where iface is a specific interface). These can be used to give
interface specific flags to dhclient.
Reviewed by: brooks@
|
|
|
|
|
|
|
|
|
| |
with NACK if I don't set it. Setting 'option dhcp-client-identifier' is
alternative but it is inconvenient because I have to keep the list of
all MAC addresses. As bin/94743 pointed out, it is always sent from
Windows clients and I found Mac OS X does the same.
OK'd by: brooks
|
|
|
|
|
|
| |
parsed, so it winds up at usage anyway.
Add 'b' to the usage summary. Noticed by Ben Mesander.
|
|
|
|
|
|
|
|
|
| |
option if none is given in the config file. Also add #ifdefd out
support for sending a client ID based on our MAC address.
PR: bin/94743, bin/76401
Submitted by: Frank Behrens <frank at pinky dot sax dot de>
X-MFC after: 6.1-RELEASE
|
|
|
|
|
|
|
| |
PR: docs/92629
Submitted by: Daniel Gerzo <danger@rulez.sk>
Noticed by: Michal F. Hanula <f@7f000001.org>
Approved by: trhodes (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/tmp may not be writeable yet when dhclient is first run via
/etc/rc.d/netif so using it may not work. Also, writing to a
predictable file in /tmp as root is a really bad idea since a malicious
user may be able to win a race and insert a symlink which will allow
them to cause any file to be overwritten. To solve these problems,
create the tempory file in /var/run which will exist this early and is
writable only by root.
Security: Local risk if users can cause dhclient to run on demand
(such as by unplugging and replugging the network cable).
|
|
|
|
|
|
|
|
| |
OpenBSD -w # when invoking ping.
PR: bin/92187
Submitted by: "Shin'ya Kumabuchi" <kumabu at t3 dot rim dot or dot jp>
MFC After: 6 days
|
|
|
|
|
|
| |
PR: 90518
Submitted by: John E. Hein <jhein@timing.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
entries from the interface rather than using ifconfig's delete command.
This preserves non-dhclient configured addresses (though they are wiped
out when dhclient is restarted).
MFC after: 1 week
|
|
|
|
|
| |
PR: bin/87465 (different solution used)
MFC after: 1 week
|
|
|
|
|
|
|
| |
refusing the lease. This allow obtaining leases on misadministered
networks that use host names with underscores in them.
MFC After: 3 days
|
|
|
|
| |
Submitted by: ume
|
|
|
|
|
|
|
|
|
| |
renewal, or we lose link, be more forceful about clearing interface
state so another interface that connects to the same network has a
chance of working. This doesn't address attemping to connect to both at
once, but appears to allow unplugging from a wired interface and then
inserting a wireless card that associates with an AP bridged to the same
LAN.
|
|
|
|
|
|
| |
file. This is what the ISC client does.
Submitted by: Rostislav Krasny <rosti dot bsd at gmail dot com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
check the domain-name parameter according to the rules for "search"
strings as documented in resolv.conf(5). Specifically, the string must
be no more than 256 bytes long and contain no more than six valid domain
names separated by white space.
The previous unchecked values could result in a mangled resolv.conf
file which could effectively deny access to local sites. This is not
a security issue as rogue dhcp servers could already do this without
sending invalid strings.
Reviewed by: cperciva
MFC After: 3 days
|
|
|
|
|
|
|
| |
for example). Follow the example of the ISC script and wrap ifconfig
calls using $medium in eval "..." so this works.
Reported by: iedowse
|
|
|
|
|
|
| |
the output index instead of keeping what ever trash was in the buffer.
Reported by: iedowse
|
|
|
|
|
|
| |
default route.
Submitted by: Rostislav Krasny <rosti dot bsd at gmail dot com>
|
|
|
|
|
|
|
| |
serves no apparent purpose (we commented this out ages ago in the ISC
scripts) and cases problems with some ADSL setups.
Reported by: Rostislav Krasny <rosti dot bsd at gmail dot com>
|
|
|
|
|
|
|
| |
lines that are exactly 81 characters in length.
Obtained from: OpenBSD
MFC After: 3 days
|
|
|
|
| |
versions when dealing with user problems.
|
| |
|
|
|
|
|
|
| |
is properly aligned when we move to the next packet.
Obtained from: ISC dhclient via krw at OpenBSD
|
|
|
|
|
|
|
| |
not allowed in domain names. RFC 2132 does not list valid or invalid
characters and the ISC client accepts anything here.
Reported by: ps
|
|
|
|
|
|
|
|
| |
capture. Zero length captures caused an infinte loop and short captures
probably caused memory corruption and a crash.
Reported by: many
MFC After: 3 days
|
|
|
|
| |
We may now handle route updates better.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
accept NUL-terminated strings as required by RFC 2132.
This solution is not perfect as it removes the ability to send
NUL-terminated host-name options which may be required by some broken
servers. Given the current lack of an existance proof of such servers
and the fact that servers that send NUL-terminated domain names do
exist, this seems like an acceptable compromise. A discussion of these
issues can be found at:
http://marc.theaimsgroup.com/?l=dhcp-client&m=96837107208382&w=2
PR: bin/83468
Reported by: Sean Winn <sean at gothic dot net dot au>
MFC-after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Reminded by: ru
|
|
|
|
|
| |
Reviewed by: ru
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)
|
|
|
|
|
| |
Timeout from: brooks
Approved by: re (blanket manpages)
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
have an active one.
Submitted by: sam
Reported by: James Snow <snow at teardrop dot org>
Approved by: re (dhclient blanket)
|
| |
|
|
|
|
| |
Tested by: Max Boyarov <max_b at tut dot by>
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
- Remove redundant and harmful -Wall from CFLAGS.
|
| |
|
|
|
|
| |
Submitted by: sam
|