After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695572 - ifcfg-rh: problem handling IPv6 static routes
ifcfg-rh: problem handling IPv6 static routes
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: Distro-specific
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-03-10 15:29 UTC by Gene Czarcinski
Modified: 2020-11-12 14:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
syslog + cat /etc/sysconfig/network-scripts/route6-eth2 (1.17 KB, text/plain)
2013-03-12 14:56 UTC, Gene Czarcinski
Details

Description Gene Czarcinski 2013-03-10 15:29:45 UTC
Description of problem:
I first noticed this problem because things do work OK on Fedora 17 with NetworkManager 0.9.6.4-3 (both are x86_64 systems).

If you define an IPv6 static route (using either the gnome editor or nm-connection-editor), when you save the update, error messages appear in syslog from ifcfg-rh that there is a parsing error and, although the route file is created, the routes are not applied.  On F17 it works.

Version-Release number of selected component (if applicable):
Fedora 18, NetworkManager 0.9.8.0

How reproducible:
everytime

Steps to Reproduce:
1.add IPv6 static routes
2.save
3.look in syslog
4.do ip -6 route
  
Actual results:
did not work

Expected results:
works with no error messages

Note:  using keyfile plugin results in no error messages.

Note:  This has been around for a while as it occurs on Fedora 17, NM 0.9.6.4
Comment 1 Jiri Klimes 2013-03-12 12:42:55 UTC
Would you be more specific on what is the route value and the error messages?

Regarding ifcfg-rh, I just see
ifcfg-rh:     error: Couldn't parse file '/etc/sysconfig/network-scripts/ifcfg-aaa.6C3NTW', which is not problem (it is a temporary file). Though, we should suppress the message.

What is the problem is
Mar 12 13:38:49 localhost NetworkManager[691]: <error> [1363091929.654872] [nm-system.c:692] nm_system_apply_ip6_config(): (eth0): failed to set IPv6 route: Object not found

And I see the error both on F17 (NetworkManager-0.9.6.4-3.fc17.x86_64) and F18 (NetworkManager-0.9.8.0-1.fc18.x86_64).

Maybe libnl issue?

Note:
I fixed reading "Gateway" (next_hop) in nm-connection-editor:
d48ab8376000cd7d56571bced4c95c722ae4fcd5
Comment 2 Jiri Klimes 2013-03-12 12:46:49 UTC
Just want to add there were no changes in
nm_system_apply_ip6_config(), nm_system_set_ip6_route() recently.
Comment 3 Pavel Simerda 2013-03-12 12:58:08 UTC
(In reply to comment #0)
> Note:  using keyfile plugin results in no error messages.

Does it mean it is specific to ifcfg-rh?
Comment 4 Gene Czarcinski 2013-03-12 14:55:16 UTC
1. Yes, this problem appears to be specific to the ifcfg-rh plugin since changing to the keyfile plugin eliminates the error messages.

2.  For both the keyfile plugin and the ifcfg-rh plugin, the route info appears to be saved and works properly.

3. There is a separate problem with IPv6 static routes when they are NOT applied to a libvirt bridge but no error is issued (Red Hat bugzilla 919875).

4. Although the problem was identified on Fedora 18 dealing with and involving libvirt bridges, this attached file is from a Fedora 17 system (NetworkManager and NetworkManager-gnome 0.9.6.4-3.fc17
Comment 5 Gene Czarcinski 2013-03-12 14:56:59 UTC
Created attachment 238699 [details]
syslog + cat /etc/sysconfig/network-scripts/route6-eth2

As far as I can tell, these error do not mean much.
Comment 6 Dan Winship 2013-05-02 15:55:06 UTC
NM bugzilla reorganization... sorry for the bug spam.
Comment 7 André Klapper 2020-11-12 14:25:27 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).