Age | Commit message (Collapse) | Author |
|
|
|
Signed-off-by: Erik G <erik.geiser@netaachen.de>
|
|
|
|
u-root -> dhcp -> u-root is the circular dependency. Which is fine,
except we messed up modules in u-root big time. We need to break the
circular dep for now.
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
|
|
* Add dhcp Opt 124(vivc) parsing to ztp
Signed-off-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
|
|
Signed-off-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
Co-authored-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
|
|
* Adding xe interface format for Juniper qfx to list of circuit regexes
Signed-off-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
* Consolidating regexes for et and xe into one entry
Signed-off-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
Co-authored-by: Hariharakumar Narasimhakumar <hhkumar@fb.com>
|
|
TravisCI not supported anymore.
Signed-off-by: Andrea Barberio <insomniac@slackware.it>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Ensure server identifier matches the offer server identifier when
looking for ACKs or NAKs.
This protects against rogue DHCP servers NAKing requests the shouldn't.
Signed-off-by: Moritz Fischer <moritzf@google.com>
Co-authored-by: Moritz Fischer <moritzf@google.com>
|
|
Signed-off-by: Eugene Burkov <e.burkov@adguard.com>
|
|
Signed-off-by: Marcel Moolenaar <mmoolena@amazon.com>
|
|
RFC 2131 gives two examples of padding in section 4.1. For both the
examples, the 'end' option preceeds the padding with the 'pad' option.
These examples relate to overloading pre-defined fields for options,
not padding the packet for a minimal size.
Older versions of the U-Boot firmware support DHCP, but do not expect
the 'pad' option. The firmware logs the following warning for each
occurence:
*** Unhandled DHCP Option in OFFER/ACK: 0
This warning disappears when the 'end' option preceeds the 'pad'
option.
Signed-off-by: Marcel Moolenaar <mmoolena@amazon.com>
|
|
Signed-off-by: yaocw2020 <yaocanwu@gmail.com>
|
|
Signed-off-by: Pablo Mazzini <pmazzini@gmail.com>
|
|
fix some debug output issues
|
|
to raiSubOptionCode
- a few minor changes to address latest feedback
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
|
|
For any users to write their own Discover or Request methods, they need
access to the ifaceHWAddr and serverAddr.
Discovered while trying to move pinterest/bender to nclients.
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Adds the additional architecture types as defined by IANA
http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture.
Note, RFC4578 errata, https://www.rfc-editor.org/errata_search.php?rfc=4578
"The values for EFI BC and EFI x86-64 should be swapped. UEFI implementations use value 7 to report EFI x86-64, not value 9."
IANA's list also agrees with this swap. Thus I've swapped these values here to match.
I took some liberty with the new architecture's mnemonic names compared to the descriptions from IANA. This was an attempt to standardize wording, capitalization, and match the existing style.
Signed-off-by: Benjamin S. Allen <bsallen@alcf.anl.gov>
|
|
- add raiValue in option_relay_agent_information.go to implement fmt.Stringer
- change test cases accordingly
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
- add a space in OptionGeneric.String()
- move the indenting "\n" from OptionHumanizer.Stringify to RelayOptions.String()
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
|
|
Option: Information Refresh Time https://tools.ietf.org/html/rfc8415
|
|
OptInformationRefreshTime (32) https://tools.ietf.org/html/rfc8415#section-21.23
Signed-off-by: Tom McPhail <tom.mcphail@icloud.com>
|
|
ExtractMAC: use option 79
|
|
- update OptionHumanizer.Stringify so it include an additional newline for option82
- update OptionGeneric.String so it include a string output in addition to existing byte slice output
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
|
|
This creates support for IA_TA options, based on and reusing the blocks
from IA_NA, to which it is extremely similar
Signed-off-by: Anatole Denis <natolumin@unverle.fr>
|
|
add lease&release support for nclient4
|
|
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
- add NewReleaseFromLease and update Client.Release() accordingly
- update lease_test.go accordingly
- remove example_lease_test.go
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
- fix a data race in lease_test.go
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
dhcpv4_release
|
|
- update lease_test.go make sure server side error is caught
- some minor fixes based on PR discussion
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
|
|
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
- change Client.Request so it now only return Lease
- change test case and example accordingly
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|
|
dhcpv4_release
|
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009
"Note that the dhcpv6 protocol doesn't have an option for a netmask. So
it is always /128 and routing is left to icmpv6 router advertisements."
RFC 5942 is a good read here as well:
An address could be acquired through the DHCPv6 identity association
for non- temporary addresses (IA_NA) option from [RFC3315] (which
does not include a prefix length), or through manual configuration
(if no prefix length is specified). The host incorrectly assumes an
invented prefix is on-link. This invented prefix typically is a /64
that was written by the developer of the operating system network
module API to any IPv6 application as a "default" prefix length when
a length isn't specified.
As DHCP developers, we *HAVE* to assume that no prefix is on-link. The
correct way to do that is to specify the netmask as /128.
The kernel will RA/RS their way around to figure out what prefixes are
indeed on-link.
Signed-off-by: Chris Koch <chrisko@google.com>
|
|
Signed-off-by: Hu Jun <hujun.work@gmail.com>
|