initscripts/network-scripts, branch master

ifup-routes: Revert quotes

2022-01-24T11:24:27+00:00

Quotes were introduced in a71dcfd392cc1022c255208fdd94a0fc6c13ceb0

Resolves: #2044189

ifup-routes: Use `ip replace` only on type `route`

2022-01-21T13:17:50+00:00

Since other types might fail due to `replace` to be undefined.

Related: #2034799

ifup-routes: Log when using `ip $type replace`

2022-01-12T13:34:15+00:00

Follow-up to #401

ifup-routes: Use `ip route repace` to avoid race

2022-01-12T11:28:25+00:00

This should resolve the scenario when the link is brought
up prior to disabling accept_ra.

This only happens when both IPv4 and IPv6 address is on
the interface, because network-scripts does IPv4 first
and brings up the interface.

Then it does IPv6 which disables the RA's, at that point
the node has already learned the route from RA and setting
a default route fails.

Using `ip route replace` we ensure if the above scenario
happens we end-up with the correct default ipv6 route.

Huge thanks to Harald who debugged this issue and prepared a patch!

Related: #2034799

Co-authored-by: hjensas

network scripts: do not use c-style for-loop

2021-11-02T11:08:16+00:00

Busybox's shell does not support c-style for-loop, use seq method to fix it.

Signed-off-by: hanzongcheng

network scripts: replace "<<<" with pipe

2021-11-02T11:08:16+00:00

Busybox's shell does not support "<<<", fix it by using pipe.

Signed-off-by: hanzongcheng

added veth support

2021-06-24T10:11:04+00:00

ifup-eth: add a new PERSISTENT_DHCLIENT_IPV6 option for IPv6 dhclient daemon

2021-06-24T10:07:01+00:00

In 76226a34 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon"),
one PERSISTENT_DHCLIENT option works for both IPv4 and IPv6, so the IPv4
and IPv6 settings are consistent. However, the user settings for IPv4 and IPv6
are limited.

For example, users try to adopt both IPv4 and IPv6 protocol. DHCPv6 servers
may be not stable as DHCP servers, thus the expectation for obtaining IPv6
address is lower than IPv4 address. For users, IPv4 address must be
obtained for the basic communication. So the PERSISTENT_DHCLIENT option is
set to be "yes | 1" for IPv4 address. However, the network service may be
stuck until it fails due to missing DHCPv6 servers, and the remaining devices also
cannot obtain both IPv4 and IPv6 addresses. The problem is very serious for users.

Here, I add a new PERSISTENT_DHCLIENT_IPV6 option only for IPv6 dhclient daemon,
so users can set IPv4 and IPv6 separately.

Fixes: 76226a3 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon")
Signed-off-by: Zhiqiang Liu

ifdown removes veth pair if both peers are down

2021-06-24T10:07:01+00:00

network scripts: Avoid infinite loop of arping

2021-02-12T13:13:40+00:00

Introduced in the bonding driver (commit ae46f184bc1f) now reports transmission failures.
Before that, it silently dropped the packet and replied with success error code.

The arping of iputils retries endlessly when a transmission error occurs.

This patch fix this behavior.