| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The argument is still always unset. We will need it later to set
IFA_F_NOPREFIXROUTE.
|
|
|
|
|
|
|
|
|
|
|
| |
It's useful to handle for IPv4 addresses too.
- we might want to sort IPv4 addresses according to whether they
are permanent or dynamic.
- we want to set IFA_F_NOPREFIXROUTE also for IPv4 addresses. While
the ability to "set" a flag doesn't necessarily require that we
also keep the flags in NMPlatformIP4Address, it is more consistent.
|
|\
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=762626
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On older NM versions the default value for vlan.flags was 0, but then
the actual value set on interfaces was REORDER_HDR. In order to
maintain backwards compatibility in behavior, remove the special
handling of vlan.flags so that a missing key is treated as the default
value REORDER_HDR.
https://bugzilla.gnome.org/show_bug.cgi?id=762626
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On NM 1.0 connections were created by default without the REORDER_HDR
flag, but then due to a bug in platform code (fixed in [1]), the
kernel interface always had the flag set.
Now that the setting is honored, users upgrading to the new version of
NM will see a change from the previous behavior, since interfaces will
not have REORDER_HDR and this will certainly break functionality.
The only solution here seems to be to ignore the REORDER_HDR variable
in ifcfg files (since it never had any effect) and introduce a new
NO_REORDER_HDR option for the VLAN_FLAGS variable which allows to turn
the flag off. The consequence is that the flag will be set for all old
connections.
This change introduces an incompatibility with initscripts, however is
necessary to avoid breaking user functionality upon upgrade.
Connections created through NetworkManager will still be parsed
correctly by initscripts (since we always write the REORDER_HDR
variable).
[1] db62fc9d72fa ("platform: fix adding VLAN flags")
https://bugzilla.gnome.org/show_bug.cgi?id=762626
|
|/ |
|
|
|
|
|
|
| |
There are far too many "flags". Rename the "flags" to "n_ifa_flags"
which reminds to "ifa_flags" in 'struct ifaddrmsg', but with a
distinctive "n_" prefix.
|
|
|
|
|
|
|
| |
Address flags inside 'struct ifaddrmsg' are uint8_t and they are
extended to uint32_t via IFA_FLAGS.
Change it to be guint32.
|
|
|
|
|
| |
- sort the fields to better fill gaps due to alignment.
- use "bool" bitfield instead of gboolean.
|
|
|
|
|
|
| |
There are far too many "flags". Rename the "flags" to "n_ifi_flags"
which reminds to "ifi_flags" in 'struct ifinfomsg', but with a
distinctive "n_" prefix.
|
|
|
|
| |
The type of ifi_flags is unsigned, not uint32_t.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
g_str_hash() can not be called with NULL. Ensure that we don't crash.
Thereby, refactor the hashing algorithm because the chassis-id and
port-id are small numbers and xor-ing can cancel them easily.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
systemd's malloc() must be matched by free() and not g_free().
Thereby, use a cleanup attribute.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
The header files are not compiled directly, but always included while compiling
other source files. We already require every source file to include "nm-sd-adapt.h"
as first, thus we don't need the include in the headers too.
|
|/ |
|
|
|
|
|
|
|
| |
check_adsl_protocol() can free and assign a new string to
@protocol_ask, leaving @protocol dangling. Fix this.
Fixes: 290c1626b9788aa90861ca423c0dffb59fe29876
|
| |
|
|
|
|
| |
Fixes: 6d409653b1bc9116bfb58b074f0c61407aef1038
|
| |
|
|
|
|
| |
https://github.com/NetworkManager/NetworkManager/pull/3
|
|
|
|
| |
It's supposed to be a virtual ethernet.
|
|
|
|
|
|
|
| |
Don't rely on what's already on the device. It could be that the MAC address
set on the device is not meaningful -- the NM crashed while two devices were
teamed together and now they have the same hardware address and now it's
impossible to bond them with mode=5.
|
| |
|
| |
|
|
|
|
| |
The device could just be removed mid-flight.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In dispatcher, we install a log-handler which maps G_LOG_LEVEL_MESSAGE
to syslog priority LOG_NOTICE, which in turn causes journal to highlight
the message. We don't want that so instead use g_info() and g_debug()
which maps to lower syslog levels.
There is only one problem, in debug-mode, we don't use syslog but the
default logging handler from glib. In this case, we have to set
G_MESSAGES_DEBUG otherwise g_info()/g_debug() is suppressed.
|
| |
|
| |
|
|
|
|
|
| |
Previous commit fixed parsing of these connection; let's check that we don't
regress there.
|
|
|
|
| |
We need the other keys, such as may_fail, too.
|
|
|
|
|
| |
Don't let the device progress to check and then in turn to activated unless all
the required IP configuration is in place.
|
|
|
|
|
|
|
| |
This saves 110 bytes (which is 1/29986680757 of the size of the books in the
Library of Congress).
Also, the function is static; not using the nm_device_ prefix is preferred.
|
|
|
|
|
|
|
| |
If a monitor interface is created, NM will grab that interface
and change it to station mode. That's not very nice.
https://mail.gnome.org/archives/networkmanager-list/2016-February/msg00068.html
|
|
|
|
|
|
|
|
|
|
|
| |
The value written to sysctl is usually a short string. It makes sense
to optimize for this case and avoid allocating a temporary string
on the heap.
An alternative would be to use writev(), which effectively does the same
and also creates a temporary buffer (preferably stack allocated).
https://mail.gnome.org/archives/networkmanager-list/2016-February/msg00070.html
|
|\
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=762538
|
| |
| |
| |
| | |
Based-on-patch-by: Jiří Klimeš <jklimes@redhat.com>
|
|/ |
|
|\
| |
| |
| |
| | |
Resurrect old branch by Jirka, rebase it and
merge some parts.
|
| |
| |
| |
| |
| |
| |
| | |
Althoug we don't fully backport the new device types, at least
add the types to the NMDeviceType enum.
Based-on-patch-by: Jiří Klimeš <jklimes@redhat.com>
|
| |
| |
| |
| | |
Based-on-patch-by: Jiří Klimeš <jklimes@redhat.com>
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
This fixes the issue where all Ad-Hoc networks try to connect one after one on
NM startup instead of the managed network that has AP available.
Fixes: e2637760f160f8d790438f3ca26df1b888de7909
|