Age | Commit message (Collapse) | Author |
|
them shorter and eliminate implications about what the function
does. No functional change.
|
|
refactoring. i.e. use specified value if server has provided no
data.
|
|
doesn't send any data for the affected option. This was broken when
the supersede/append/prepend/ignore logic was refactored.
Reported by and fix tested by johnw via misc@
|
|
|
|
'in_addr'. Remove many double conversions and other perversions.
piaddr() replaced with inet_ntoa(). dhclient is extremely unlikely
to support anything but ipv4/dhcp without a complete rewrite.
Joint work with chris@.
Positive feedback from deraadt@ zinke@ phessler@.
|
|
'egress' as a special interface name.
|
|
Spotted by zinke@.
|
|
|
|
will be always be aligned. Don't pass around pointers into option
data - use variable that has the memcpy()'d data.
|
|
|
|
|
|
|
|
Also fix a bug where the return value of if_exists() was not checked
correctly if the interface disappears while pflogd is running.
ok beck henning
|
|
|
|
host route, a.k.a. 'route add w.x.y.z 127.0.0.1'. Since dhclient-script
ignored the failure, ignore it here too until it can be explained
or we stop creating these routes.
|
|
rather than setting all flags to zero. ok krw deraadt
|
|
|
|
|
|
|
|
1) Don't leak a file descriptor if there are no contents for
resolv.conf.
2) Allow for only resolv.conf.tail to go into resolv.conf.
3) Don't need to pass around interface name when creating resolv.conf.
4) Don't leave 0 length resolv.conf lying around if there are no
contents.
|
|
to *add* an address, here (building an ifaliasreq to delete an
address) it worked fine. But change it to the bcopy() dance that
works in the adding case just to be consistant until a sparc64/gcc
guru is cornered in a bar with a full keg of guiness.
|
|
in_addr_t values into s_addr's rather than assigning them.
Possibly not the ideal solution, but at least dhclient will work
again on sparc64.
|
|
question is the empty string.
Spotted by Joerg Zinke.
|
|
process. So when the child dies, the parent exits immediately.
|
|
|
|
|
|
that a macro (which I called MAXRESOLVCONSIZE) would make things
easier to read and reduce such typos. Make it so.
|
|
binding a lease to that interface. This fixes issues sthen@ found
with unexpectedly persistant addresses and failures of dhclient
when switching an interface repeatedly between different networks.
This crude but predictable behaviour may be toned down once it
is figured out what we want to do with mixed static/dynamic
configurations on an interface.
ok sthen@
|
|
interface and route configuration via ioctl's and routing sockets.
This will break configurations using local enhancements of
dhclient-script, which will now require alternate arrangements.
Committing early to allow time to identify and develop required
alternatives.
Several proddings by deraadt@.
|
|
maninpulations. Inspired by similar files in bgpd, dvmrpd, ldpd, etc.
Necessary for imminent nuking of dhclient-script.
Not linked into build at the moment.
|
|
report from Thomas Proell/Siemens ProductCERT; fix from hshoexer; ok mikeb
|
|
|
|
rather than list of option declarations. e.g. 'ignore routers;'
instead of 'ignore routers 1.2.3.4;' The value in the declaration
was being ignored anyway.
While there clean up the related code a bit.
|
|
|
|
of generating them with genmap from ikev2.h. They're only really
needed in parse.y and this diff also allows to simplify genmap.sh.
|
|
released) portable version a bit. No functional changes.
|
|
Makefile. No functional change.
|
|
compiler warning.
|
|
|
|
side. Also add a new command line option -t to optionally enforce
NAT-T with UDP encapsulation on port 4500.
Tested by mikeb@ and me
ok mikeb@
|
|
reorder rules incorrectly, i. e.:
pass rtable 2
pass from 10/16 rtable 0
pass from 10.1/16 rtable 1
so with this ruleset a packet from 10/16 will end up in rtable 0.
now let's see what pfctl makes out of it, with default optimization:
<brahe@tachi> pfctl $ pfctl -nvf t.conf
pass inet from 10.0.0.0/16 to any flags S/SA rtable 0
pass inet from 10.1.0.0/16 to any flags S/SA rtable 1
pass all flags S/SA rtable 2
OUPS! a packet from 10/16 will end up in rtable 2 now.
found by phessler, fix by your's truly, from EuroBSDcon
ok beck phessler benno mikeb sthen
|
|
route-to with any other scheduling algorithms than round-robin or
least-states. Before this change, pfctl accepted and loaded invalid
address pools, eg. "rdr-to <table> source-hash", but it is not
supported by the kernel and was silently ignored in operation.
Also clarify the manpage a bit by mentioning that tables are only
valid with round-robin or least-states.
ok zinke@
|
|
|
|
- pull in machine/cpu.h so we can actually see CPU_LIDSUSPEND if it's there
- fix the resulting compilation errors now that the code is actually used
"Just go for it" deraadt@
|
|
called "pubkeys" not "pubkey".
Found by Michael Cardell "MC" Widerkrantz
|
|
the dispatch loop again; in the case where two RTM_IFINFO link changes occur
immediately after each other (as in the case with trunk and probably vlan)
dhclient missed the state change of the second interface.
ok krw@, who points out that dhcp packets received between the two
RTM_IFINFO messages would be lost, however the window is small (<0.4ms on
my laptop) and this is better than not noticing the link change.
|
|
interface's routes when the interface is down.
Prevents floods of RTM_MISS messages on 'ifconfig down'. And might
fix the vpn related failures pirofti@ is seeing.
|
|
machine." This has been broken when the subjectAltName certificate
check was introduced some time ago. Fix it by obtaining the hostname
source Id in the certificate request code as well.
ok mikeb@
|
|
ok jmc
|
|
ok sthen@ mikeb@
|