openslx-ng/ipxe.git/src/net/udp, branch master

[tftp] Prevent potential division by zero

2018-03-18T15:43:11+00:00

Signed-off-by: Michael Brown

[dns] Ensure DNS names are NUL-terminated when used as diagnostic strings

2017-09-07T11:19:35+00:00

Signed-off-by: Michael Brown

[dns] Report current DNS query as job progress status message

2017-09-06T10:46:13+00:00

Signed-off-by: Michael Brown

[slam] Avoid NULL pointer dereference in slam_pull_value()

2017-03-21T12:57:36+00:00

Signed-off-by: Michael Brown

[slam] Fix resource leak on error path

2017-03-21T12:53:13+00:00

Signed-off-by: Michael Brown

[dhcp] Allow vendor class to be changed in DHCP requests

2017-03-20T11:58:59+00:00

Allow the DHCPv4 vendor class to be specified via the "vendor-class" setting. Signed-off-by: Michael Brown

[netdevice] Allow MTU to be changed at runtime

2017-01-23T17:47:28+00:00

Provide a settings applicator to modify netdev->max_pkt_len in response to changes to the "mtu" setting (DHCP option 26). Note that as with MAC address changes, drivers are permitted to completely ignore any changes in the MTU value. The net result will be that iPXE effectively uses the smaller of either the hardware default MTU or the software configured MTU. Signed-off-by: Michael Brown

[ipv6] Create routing table based on IPv6 settings

2016-07-20T12:02:44+00:00

Use the IPv6 settings to construct the routing table, in a matter analogous to the construction of the IPv4 routing table. This allows for manual assignment of IPv6 addresses via e.g. set net0/ip6 2001:ba8:0:1d4::6950:5845 set net0/len6 64 set net0/gateway6 fe80::226:bff:fedd:d3c0 The prefix length ("len6") may be omitted, in which case a default prefix length of 64 will be assumed. Multiple IPv6 addresses may be assigned manually by implicitly creating child settings blocks. For example: set net0/ip6 2001:ba8:0:1d4::6950:5845 set net0.ula/ip6 fda4:2496:e992::6950:5845 Signed-off-by: Michael Brown

[ipv6] Match user expectations for IPv6 settings priorities

2016-07-19T16:07:53+00:00

A reasonable user expectation is that ${net0/ip6} should show the "highest-priority" of the IPv6 addresses, even when multiple IPv6 addresses are active. The expected order of priority is likely to be manually-assigned addresses first, then stateful DHCPv6 addresses, then SLAAC addresses, and lastly link-local addresses. Using ${priority} to enforce an ordering is undesirable since that would affect the priority assigned to each of the net blocks as a whole, so use the sibling ordering capability instead. Signed-off-by: Michael Brown

[dhcpv6] Expose IPv6 address setting acquired through DHCPv6

2016-07-19T00:20:34+00:00

Originally-implemented-by: Hannes Reinecke Originally-implemented-by: Marin Hannache Signed-off-by: Michael Brown