#
726515c9 |
| 11-Nov-2024 |
florian <florian@openbsd.org> |
Prevent completely empty interface blocks.
This is meaningless in dhcpleased(8) and *not* needed to receive leases for an interface. In fact dhcpleased(8) works just fine without any configuration f
Prevent completely empty interface blocks.
This is meaningless in dhcpleased(8) and *not* needed to receive leases for an interface. In fact dhcpleased(8) works just fine without any configuration file at all.
man page diff & OK kn
show more ...
|
#
3a2a6d8f |
| 03-Jun-2024 |
deraadt <deraadt@openbsd.org> |
more sleepy florian knf issues
|
#
6d7478f0 |
| 25-Nov-2023 |
florian <florian@openbsd.org> |
First stab at IPv6-only preferred from RFC8925.
This lets dhcpleased(8) request "IPv6-only preferred". If the server replies with this option dhcpleased stops and does not request a lease and deconf
First stab at IPv6-only preferred from RFC8925.
This lets dhcpleased(8) request "IPv6-only preferred". If the server replies with this option dhcpleased stops and does not request a lease and deconfigures IPv4 on the interface.
For now this is pretty much useless unless one dynamically configures pf(4) to act as a CLAT. gelatod(8) from ports can help with this.
However, this helps me while hacking on a kernel based stateless CLAT by moving dhcpleased out of the way while having an IPv6-mostly network configured to compare behaviour with macOS.
Input jmc OK phessler Input & OK sthen
show more ...
|
#
5b2dcb8f |
| 21-Mar-2022 |
dlg <dlg@openbsd.org> |
default the conffile variable to the default file name instead of NULL.
this avoids having to test for NULL and swap the right name in place in a bunch of places. it also avoids having NULL passed t
default the conffile variable to the default file name instead of NULL.
this avoids having to test for NULL and swap the right name in place in a bunch of places. it also avoids having NULL passed to format strings in the parser.
the only place where it actually matters if we're using the default or not is when we're parsing the config. if you don't specify a config, and the default file doesnt exist, that's ok.
ok florian@
show more ...
|
#
b3441518 |
| 04-Jan-2022 |
florian <florian@openbsd.org> |
Make host name DHCP option configurable. Diff from hagen@sdf.org, tweaks by me. OK phessler testing & OK bket
|
#
08f6ba19 |
| 15-Oct-2021 |
naddy <naddy@openbsd.org> |
Don't declare variables as "unsigned char *" that are passed to functions that take "char *" arguments. Where such chars are assigned to int or passed to ctype functions, explicitly cast them to uns
Don't declare variables as "unsigned char *" that are passed to functions that take "char *" arguments. Where such chars are assigned to int or passed to ctype functions, explicitly cast them to unsigned char.
For OpenBSD's clang, -Wpointer-sign has been disabled by default, but when the parse.y code was built elsewhere, the compiler would complain.
With help from millert@ ok benno@ deraadt@
show more ...
|
#
8a60c40e |
| 20-Sep-2021 |
florian <florian@openbsd.org> |
According to RFC 2132 (9.14. Client identifier) a hardware type of 0 should be used when the client identifier is not a hardware address, for example if it's just a string. It turns out that the majo
According to RFC 2132 (9.14. Client identifier) a hardware type of 0 should be used when the client identifier is not a hardware address, for example if it's just a string. It turns out that the majority of dhcp clients (and possibly servers?) does not do this but rather transmits the client identifier verbatim if a string is configured. The first character becomes the hardware type. Make dhcpleased(8) behave the same. Difference in behavior with dhclient(8) and interoperability issues with dhcp(8) first pointed out by Olivier Cherrier on misc@ OK sthen fine to get it in for 7.0 deraadt
show more ...
|
#
c2bc6c6d |
| 12-Aug-2021 |
florian <florian@openbsd.org> |
Make it possible to ignore routes or nameservers from a lease as well as ignoring servers entirely. Tested by bket Parser looks reasonable to benno man page OK jmc
|
#
4ebb4dc4 |
| 27-Jul-2021 |
deraadt <deraadt@openbsd.org> |
'{' and '}' are fixed parts of the 'interface' decleration', not optional. concern raised by kn. ok florian
|
#
a41cc082 |
| 26-Jul-2021 |
florian <florian@openbsd.org> |
Implement possibility to send vendor class identifier (option 60) and client identifier (option 61). Some dhcp servers expect these options and refuse to hand out a lease without them. Need for vendo
Implement possibility to send vendor class identifier (option 60) and client identifier (option 61). Some dhcp servers expect these options and refuse to hand out a lease without them. Need for vendor class identifier pointed out & tested by bket Need for client identifier pointed out by sthen Input & reads OK sthen (as part of a larger diff) OK kn (as part of a larger diff)
show more ...
|