initscripts/network-scripts/ifup-eth, branch 10.07

network: add option to keep the link down

2020-12-03T13:33:07+00:00

Some interfaces like Open vSwitch bridges using the userspace datapath,
needs the link to be kept down to avoid issues.
Add a LINKSTATUS=[down|up] ifcfg parameter to add this functionality.
If not specified, the link will default to up as before.

Patch provided by Matteo Croce

Add optional 'dev' keyword

2020-07-24T11:44:37+00:00

Fix the problem when the device name could be interpreted as an iproute2 keyword.
For example, for a bridge slave named "a" the iproute2 would treat the name
as a prefix of keyword "address" and the network-scripts would fail to set
the bridge master.

Related: rhbz #1859785

Repalace hardcoded tests for yes and no with testing functions

2019-09-12T10:32:36+00:00

Resolve issue: #42

ifup-eth: Fix bridge setting stp option

2019-08-21T08:54:30+00:00

Fixes https://bugzilla.redhat.com/1743522

An uninitialized variable was copied from a closed PR [1]
to submitted PR [2].

[1] https://github.com/fedora-sysv/initscripts/pull/212
[2] https://github.com/fedora-sysv/initscripts/pull/213

Signed-off-by: Bell Levin

ifup-eth: Check that device name is set

2019-08-19T10:01:11+00:00

ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon

2019-02-12T13:14:24+00:00

IPv6 dhclient daemon only tries one time to obtain a IPv6 address
from a DHCPv6 server regardless of the setting of PERSISTENT_DHCLIENT.
PERSISTENT_DHCLIENT option is only used for IPv4 dhclient daemon.

With the popularization of IPv6 protocol, some users prefer setting
IPv6 like IPv4. I think there are two solutions as follows,
1. adopt PERSISTENT_DHCLIENT option to both IPv4 and IPv6.
2. create a new option, such as PERSISTENT_DHCLIENT_IPV6 option,
just for IPv6.

The first solution does not introduce addition options, and the IPv4
and IPv6 settings are consistent. So I perfer choosing the first
solution.

Fixes: bf00a0048 ("Replace /var/run with /run everywhere")
Signed-off-by: Zhiqiang Liu

ifup-eth: use 'bc' instead of 'expr' when computing $forward_delay

2018-08-03T10:57:38+00:00

  Because the return value of 'convert2sec()' function can sometimes be
  decimal, the follow up 'expr' call can fail, since 'expr' does not
  support floating point calculations. This can sometimes lead to error:

  """
  expr: non-integer argument
  /etc/sysconfig/network-scripts/ifup-eth: line 91: [: 0: unary operator
  expected
  """

  To solve this bug, we switch to 'bc' utility, which supports floating
  point computations. We also have to change the comparison condition of
  $LINKDELAY and $forward_delay to use 'bc' as well.

network-scripts: Add previously dropped error checking

2018-06-14T14:27:36+00:00

When converting from brctl to ip-link, the call to exit in case bridge
adding failed was dropped by accident.

network-scripts: Replace brctl with ip-link

2018-06-14T14:27:36+00:00

Since ip-link has full support for Linux bridges (and slave ports), use
that instead of the deprecated brctl from bridge-utils.

network-scripts: setting of firewall ZONE fixed

2018-06-07T12:04:50+00:00

  For currently unknown reason the dbus-send calls will fail to set the
  firewall zone for the given interface if we omit the --print-reply
  option...

  This looks like some kind of race-condition in dbus-send, since the
  --print-reply makes the call synchronous and slower.

  Hopefully this is only a temporary workaround until DBus is fixed.

  Resolves: #1586284