- 25 Oct, 2018 4 commits
-
-
Antonin Décimo authored
Reported by cppcheck. (portability) '(void*)((char*)current_attribute)' is of type 'void *'. When using void pointers in calculations, the behaviour is undefined.
-
Antonin Décimo authored
-
Antonin Décimo authored
-
Antonin Décimo authored
-
- 23 Oct, 2018 25 commits
-
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Matthieu Boutier authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
We can no longer call send_multihop_request with a NULL argument.
-
Weronika Kolodziejak authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
This removes duplication between unicast and multicast variants of message formatting.
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
This is no longer useful and complicates the code.
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
-
- 26 Sep, 2018 1 commit
-
-
Juliusz Chroboczek authored
-
- 24 Sep, 2018 1 commit
-
-
Juliusz Chroboczek authored
-
- 18 Sep, 2018 3 commits
-
-
Juliusz Chroboczek authored
-
Juliusz Chroboczek authored
Thanks to Christof Schulze for noticing the problem.
-
Christof Schulze authored
-
- 16 Sep, 2018 1 commit
-
-
Christof Schulze authored
When adding unreachable routes and setting the RTNH_F_ONLINK flag, a device is required to be specified. In Linux kernel 4.16 support for this flag was added. Until now it was ignored. If RTNH_F_ONLINK is specified while the device is missing, newer kernels will respond with No such device. The result is: * spam in the log file * missing routes for both ipv4 and ipv6
-
- 29 Jun, 2018 1 commit
-
-
Juliusz Chroboczek authored
The check for a TLV going beyond the end of the packet was off by two. A malformed packet could possibly cause babeld to read two octets beyond the end of the read buffer. While technically a buffer overflow, this is most probably not exploitable, since it is a read-only overflow. At worst, it would cause two octets of garbage to be parsed and treated as valid data.
-
- 12 May, 2018 1 commit
-
-
Juliusz Chroboczek authored
-
- 11 May, 2018 1 commit
-
-
Juliusz Chroboczek authored
This fixes a bug that was introduced in commit 4f4e3cba, and prevented non-source-specific IPv4 routes from being redistributed. Thanks to Niklas Yann Wettengel for the detective work.
-
- 07 Apr, 2018 1 commit
-
-
Juliusz Chroboczek authored
-
- 23 Feb, 2018 1 commit
-
-
Matthieu Boutier authored
-