Age | Commit message (Collapse) | Author |
|
1) If the pipe to the priv process is closed while waiting for
something to happen in the non-priv dispatch() loop, assume the
priv process issued an error message and exit without additional
verbiage.
2) Ditto if the pipe to the priv process is closed when the flush
of IMSG_CLEANUP is attempted.
3) No need to report when SIOCDIFADDR fails because the address is
already gone.
Start to ensure the priv process always issues a useful message
before exiting by noting when it restarts due to the LLADDR having
changed.
Prodded by deraadt@ to clean this up.
|
|
messages. Prodded by otto@. RTP_NONE's home pointed out by jsg@.
|
|
i.e. did not complain (-q) if 127/8 was unreachabel from $rdomain.
So don't pollute the log with new warnings about being unable to
create the route. Just complain if a truly unexpected error occurs.
Noted by Andreas Bartelt.
|
|
error message to show problematic table id and use clearer
verbiage suggested by sthen@.
Should fix (another!) problem reported by Andreas Bartelt, who
noted that lease renewals did not work in a non-default routing
domain.
ok sthen@
|
|
|
|
ok beck@
|
|
zeroed, rather than some other variable that may be the same type.
|
|
correct field.
|
|
|
|
e.g. with ESRCH.
Ask for default route in correct routing domain.
While here, tweak variable names to be consistant with other
functions using a routing socket.
Likely the cause of the periodic failures reported by Andreas Bartelt
via bugs@.
|
|
result of its LLADDR changing! Check said address and if it differs
from what we think it is, simulate a SIGHUP to restart, getting the
new address and a new lease for it.
Spotted by, fix tested by, and ok beck@
|
|
attempts to send DISCOVER or REQUEST packets. Some DHCP servers might
NAK the DISCOVER, or other nefarious packets arrive, between attempts
and overwrite the packet being sent. Create and use another buffer
for packets being sent.
Problem encountered by fgsch@, who noticed that once the DISCOVER was
NAK'ed our dhclient sent a bunch of NAK's back to the server. Like it
thought they were DISCOVER messages.
ok beck@
|
|
SIGTERM is used to make processes go away during system shutdown and
NFS filesystems may be still be in use when it is received. So removing
routes to the NFS servers is a bad thing.
Problem discovered and fix tested by landry@.
|
|
|
|
Just because CPU_LIDSUSPEND is defined in cpu.h does mean it is
actually supported by the hardware. OK halex@
|
|
an option list if it contains duplicate option names. Just ignore
the duplicates.
|
|
Just because CPU_LIDSUSPEND is defined in cpu.h does mean it is
actually supported by the hardware. OK miod@ kettenis@
|
|
the way, cut back on some of the crazy macros that were mostly around
to appease groff;
whilst there, fix the warnings reported by Jan Stary back in january;
lots of help and ok krw
|
|
other interface types. suggested/tested Mattieu Baptiste, ok dlg@ yasuoka@
giovanni@, ifconfig(8) reminder jmc@
|
|
decode_udp_ip_header() and the useless check of it. Part of original
diff from pelikan about udp length errors.
|
|
the current default route. Much less work for the routing system.
Suggested by claudio@. ok beck@
|
|
bind_lease().
|
|
so it is easy to see which interface generated it.
|
|
should be written. Bad cut 'n paste.
|
|
ok krw@
|
|
ok krw@
|
|
ok krw@
|
|
same variable to determine if cumulative lengths of strings to be
put in buffer are > 0. Otherwise we always think here is something
to put in buffer.
Reported by florian@ and his friend llvm.
|
|
message. Handle an empty resolv.conf.tail without exiting. Don't
leak an fd if fstat() on resolv.conf.tail fails. Make fstat()
failure on successfully opened resolv.conf.tail a fatal error.
From Tim van der Molen. Thanks!
|
|
of the process binding the lease. Re-check the default route whenever
a routing message arrives that might mean the default route has
changed, and write out resolv.conf if appropriate.
Reduces the chances that the name servers in resolv.conf are
unreachable.
Problem most eloquently explained, and solution suggested by beck@.
|
|
lease and reuse as required whenever resolv.conf is written. Use
write_file() rather than a custom message/functions to write out
resolv.conf.
|
|
touch resolv.conf" behaviour.
|
|
application during subsequent resolv.conf building.
|
|
|
|
|
|
|
|
|
|
|
|
Set 'quit' to exit the loop in those situations, allowing more
cleanup() attempts in those error situations.
|
|
the most recent offer and effective leases will be written. Intended
to allow access to dhcp option information that was formerly
passed to dhclient-script.
|
|
configured. Only exempt default routes labelled as being the
property of another dhclient.
|
|
|
|
causing a problem, it was accessing uninitialized pointers.
|
|
|
|
and log messages.
|
|
a pending address addition.
Should fix "routehandler: interface address added" messages and
premature exiting of dhclient seen by henniing@ amoung others.
|
|
into the set block. so make pfctl accept, print and the manpage document
. match set queue foo
instead of
. match queue foo
but keep accepting the old way without the explicit set.
ok bob, man jmc
|
|
process to ask that a file be written by the privileged process.
Not yet used.
|
|
discards bad options. THEN check to see if any required options are
missing and reject both OFFER and ACK packets that lack required
options. Since it is the latter's lease we actual bind.
Move required option check into packet_to_lease() instead of
duplicating it.
|
|
|