GCC compiler complained:
../../../../src/core/ipv6/nd6.c:861:16: error: request for implicit conversion from ‘void *’ to ‘struct lladdr_option *’ not permitted in C++ [-Werror=c++-compat]
861 | lladdr_opt = nd6_find_option(p, sizeof(*redir_hdr), ND6_OPTION_TYPE_TARGET_LLADDR);
| ^
cc1: all warnings being treated as errors
When parsing Neighbor Solicitation, Neighbor Advertisement and Redirect
messages, options will be searched through for the expected link-layer
address type instead of just using the first option.
see patch #10133
So that can do:
void my_loop() {
long timeout;
while (1) {
timeout = sys_check_timeouts();
if (timeout == SYS_TIMEOUTS_SLEEPTIME_INFINITE)
timeout = 100;
WaitForEvent(timeout);
}
}
Signed-off-by: Simon Goldschmidt <goldsimon@gmx.de>
... especially the TCP control ones (SYNACK, RST, etc).
This change makes the system useless as a zombie machine in idle-scan
attempts.
This approach is inspired by what is done in other network stack (such
as the linux kernel one).
This approach is a low-cost CPU solution, compared to generating a
random IP ID value for every single IP packet.
See patch #10270
Signed-off-by: Samuel Martin <samuel.martin@netatmo.com>
Signed-off-by: Simon Goldschmidt <goldsimon@gmx.de>
Current parsing code is building reverse-order integer, and then calls htonl()
to assign right value to "ts_recent" field of pcb.
This works correctly on little-endian machines, where htonl() reverses bytes.
However, on big-endian machines, htonl() is no-op, so bytes stay reversed.
This patch fixes it by building non-reversed integer.
AutoIP now selects a new address after rate limit timeout,
AutoIP tries a new address by incrementing the tried_llipaddr counter
in the ACD_DECLINE case of the callback.
In lwIP pre-2.2.0, address conflict detection was handled within autoip.c, and
the incrementing happened in autoip_restart() (line 150). When ACD was
extracted into a separate module in 2.2.0, this increment was missing for the
rate-limiting path.
Without this change, devices continuously retry the same IP address after rate
limiting, causing them to fail Bonjour Conformance Tests.
The TFTP app should not bind to the TFTP server port when configured as
a client. Instead, the local port should be chosen from the dynamic
range (49152 ~ 65535) so that if the application is stopped and started
again, the remote server will not consider the new packets as part of
the same context (which would cause an error since a new RRQ would be
unexpected).
Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
FreeBSD support is basically just very small changes related to
some different includes and one define to not hide non-standard defines
like B115200.
Signed-off-by: Arne Schwabe <arne@rfc2549.org>
