<feed xmlns='http://www.w3.org/2005/Atom'>
<title>initscripts/network-scripts, branch 10.12</title>
<subtitle>Mageia fork of Fedora's Init Scripts</subtitle>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/'/>
<entry>
<title>added veth support</title>
<updated>2021-06-24T10:11:04+00:00</updated>
<author>
<name>Geiger</name>
<email>geigereitan@gmail.com</email>
</author>
<published>2017-03-05T12:26:15+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=2e8de416fe609b04f2af3995890d9be8276c5e7b'/>
<id>2e8de416fe609b04f2af3995890d9be8276c5e7b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>ifup-eth: add a new PERSISTENT_DHCLIENT_IPV6 option for IPv6 dhclient daemon</title>
<updated>2021-06-24T10:07:01+00:00</updated>
<author>
<name>Zhiqiang Liu</name>
<email>liuzhiqiang26@huawei.com</email>
</author>
<published>2019-03-05T20:25:00+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=a8212c1b232a902938d0e5ea6a82bd6ae52e861c'/>
<id>a8212c1b232a902938d0e5ea6a82bd6ae52e861c</id>
<content type='text'>
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 &lt;liuzhiqiang26@huawei.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;liuzhiqiang26@huawei.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ifdown removes veth pair if both peers are down</title>
<updated>2021-06-24T10:07:01+00:00</updated>
<author>
<name>Geiger</name>
<email>geigereitan@gmail.com</email>
</author>
<published>2017-03-07T15:23:08+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=81b7893dd1627c43464064e670583803aca2d5ff'/>
<id>81b7893dd1627c43464064e670583803aca2d5ff</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>network scripts: Avoid infinite loop of arping</title>
<updated>2021-02-12T13:13:40+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2021-02-12T09:15:21+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=6c9689c792ac7771159794ee24ab99bd746318d9'/>
<id>6c9689c792ac7771159794ee24ab99bd746318d9</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>network: fix condition in set_link_up()</title>
<updated>2021-02-04T13:33:23+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2021-02-04T13:33:23+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=b1626389507a3d9e4d7e7805939c3a589954bb46'/>
<id>b1626389507a3d9e4d7e7805939c3a589954bb46</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>network: fix set_link_up()</title>
<updated>2020-12-17T07:31:14+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2020-12-17T07:31:14+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=4c3b3af678e353b54fa270663d7fc2fbe5681b48'/>
<id>4c3b3af678e353b54fa270663d7fc2fbe5681b48</id>
<content type='text'>
This patch fixes issue, when interface wasn't
bring up.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch fixes issue, when interface wasn't
bring up.</pre>
</div>
</content>
</entry>
<entry>
<title>network: add option to keep the link down</title>
<updated>2020-12-03T13:33:07+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2020-12-03T13:33:07+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=0ac0949b03cdfc2c06ba997e9b3b890a5ca17b1f'/>
<id>0ac0949b03cdfc2c06ba997e9b3b890a5ca17b1f</id>
<content type='text'>
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 &lt;mcroce@redhat.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;mcroce@redhat.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>network-scripts: Use net_log() instead of logger</title>
<updated>2020-11-05T13:51:33+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2020-11-05T13:51:33+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=7d876f7ac28151d754aafbe5d008c9a4b574e211'/>
<id>7d876f7ac28151d754aafbe5d008c9a4b574e211</id>
<content type='text'>
Use internal network-scripts function net_log() instead of
/usr/bin/logger if possible to make code more consistent and cleaner.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Use internal network-scripts function net_log() instead of
/usr/bin/logger if possible to make code more consistent and cleaner.</pre>
</div>
</content>
</entry>
<entry>
<title>Add warning to warn user when ETHTOOL_OPTS is set and ethtool binary is missing - Olav Vitters</title>
<updated>2020-08-12T11:51:22+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2020-08-12T11:51:22+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=1ec2149386beca68792496b600a5cf71f4a36709'/>
<id>1ec2149386beca68792496b600a5cf71f4a36709</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add optional 'dev' keyword</title>
<updated>2020-07-24T11:44:37+00:00</updated>
<author>
<name>Jan Macku</name>
<email>jamacku@redhat.com</email>
</author>
<published>2020-07-24T11:44:37+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=299efd663b4614f4698cf2bc9b9ba8e72df9387e'/>
<id>299efd663b4614f4698cf2bc9b9ba8e72df9387e</id>
<content type='text'>
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</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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</pre>
</div>
</content>
</entry>
</feed>
