GNOME Bugzilla – Bug 434993
Doesnt work with renamed interfaces
Last modified: 2012-11-24 20:29:33 UTC
[ Forwarded from http://bugs.debian.org/355260 ]
"I use nameif to rename my interfaces and get consistant names between sessions.
This is done this way in /etc/network/interfaces:
iface lan inet static
pre-up nameif lan 00:11:2F:C6:5A:38
up route add default gw 192.168.1.1
Then the "lan" interface is seen by the system the normal way:
lan Link encap:Ethernet HWaddr 00:11:2F:C6:5A:38
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
If I start gnome-nettool, this interface appears in the lsit in the "Devices" tab:
Network device: Unknown interface (lan)
If I click [Configure], I get, after a while, a popup with:
The interface does not exist
Check that is is correctly typed and that
it is correcly supported by your system."
This bug belongs to gnome-system-tools.
I tried the following:
iface lan inet static
pre-up nameif lan 00:0F:1F:B1:DD:BF
The MAC address is my Ethernet card usually named as eth0.
I commented the line that defines eth0 and I added the
definition for lan.
$ ifconfig lan
lan Link encap:Ethernet HWaddr 00:0F:1F:B1:DD:BF
inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
The button Configure, spawns gnome-system-tool (network-admin). I just added a g_print before the system tool is called, just to confirm it:
$ sudo src/gnome-nettool
/usr/bin/network-admin --configure lan
And I get the same dialog as you report. So, I'm confirm the bug but it doesn't apply to gnome-nettool.
I'm confirming the bug. I was able to reproduce it using GNOME 2.18 and gnome-nettool trunk.
(In reply to comment #2)
> I'm confirming the bug. I was able to reproduce it using GNOME 2.18 and
> gnome-nettool trunk.
Problem still persists in Network Tools 2.28.0
using Ubuntu 9.10 RC.
Quick question for you folks. When can we expect a fix for this? I just installed the newest version of Ubuntu and this issue is still lingering. I'd expected this would have been on the Top 100 list for usability fixes in any new release. Question for you though, is there a workaround? Something we can do to enable the "configure" button? I noticed the same behavior is present in the Network Tools app from the Administration menu. The only place I can get anywhere is with the Network app and using the Unlock function. That's really not a workaround as you can't do any MTU modifications or any other advanced network admin from there so we're stuck hunting for terminal commands. Looking forward to a speedy closure for EVERYONE. Thanks!
No, I don't expect anybody to work on network-admin in the future. You should really try NetworkManager, and file bugs there if you need fixes. You may have noticed that Ubuntu no longer ships with network-admin for several releases already, NetworkManager is the way to go.
According to its developer(s), gnome-system-tools is not under active development anymore. Functionality has been mostly integrated into GNOME Control Center / "[System] Settings".
It is unlikely that there will be any further active development.
Closing this report as WONTFIX as part of Bugzilla Housekeeping - Please feel
free to reopen this bug report in the future if anyone takes the responsibility
for active development again.