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 723048 - 'network-access' test can fail to guess interface index
'network-access' test can fail to guess interface index
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
2.39.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-01-26 20:09 UTC by Ludovic Courtès
Modified: 2014-02-01 12:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ludovic Courtès 2014-01-26 20:09:03 UTC 
In gio/tests/network-address.c, the ‘find_ifname_and_index’ fails to determine an interface index when that interface has an index > 255.

In our experience, that can happen when setting up separate network name spaces with CLONE_NEWNET: each time a new process is started, the "lo" interface (for example) would get an index incremented by one.

This has caused occasional build failures with GNU Guix, which runs build processes in Linux containers with separate name spaces:

  https://lists.gnu.org/archive/html/guix-devel/2013-10/msg00173.html

We work around it by specifically looking for "lo", and allowing indices greater than 255:

  http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/glib-tests-newnet.patch

Ludo'.
Comment 1 Dan Winship 2014-02-01 12:43:15 UTC 
You can't *just* look for "lo", because that will fail on Windows (and some old unixes had "lo0" rather than "lo" too, though I'm not sure if any current ones do...). Anyway, I fixed it to try "lo" first, and then fall back to probing up to 1024 if that fails.