Bug 93996 - static route add problems
Summary: static route add problems
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 2
Hardware: Other All
: P5 - None : Normal (vote)
Target Milestone: Alpha 1
Assignee: Katarina Machalkova
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-24 22:27 UTC by Andreas Kleen
Modified: 2008-01-07 15:00 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
found the log (197.24 KB, application/octet-stream)
2005-06-24 22:32 UTC, Andreas Kleen 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kleen 2005-06-24 22:27:59 UTC 
I tried to add a static route using yast2 to an ethernet interface.

Problems:

- It listed the interface list claiming it was optional. But there was no
"none" or "any" entry so it was impossible to declare a route without
interface for a gateway. 

- The interface list lists MAC addresses, which is very user unfriendly.
It should list the verbose names of the interfaces ("FooNIC 1 etc.")

No y2logs, but should be easy to reproduce using the description.
Comment 1 Andreas Kleen 2005-06-24 22:32:02 UTC 
Created attachment 39910 [details]
found the log
Comment 2 Martin Vidner 2005-06-27 11:47:08 UTC 
Yes, both are good points.  
You can just delete the interface string to make a route without an interface.  
  
In addition, when editing such a route, an arbitrary interface is wrongly  
selected in the dialog.
Comment 3 Martin Vidner 2006-08-28 11:58:41 UTC 
Reassigning to the new co-maintainer of yast2-network.
Comment 4 Martin Vidner 2006-08-28 12:01:01 UTC 
second service...
Comment 5 Stanislav Visnovsky 2007-11-23 08:35:48 UTC 
What is status here?
Comment 6 Katarina Machalkova 2007-11-28 09:01:33 UTC 
Point b) is not valid any more - short device names (eth1, wlan0,...) are being used in 10.3 instead of beasts such as eth-id-00-00-de-ad-be-ef 

Point a) and comment #2 are both valid and trivial to fix. I'll do the fix for Stable
Comment 7 Katarina Machalkova 2008-01-07 15:00:12 UTC 
Fixed in yast2-network 2.16.18