|
Bugzilla – Full Text Bug Listing |
| Summary: | static route add problems | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Andreas Kleen <ak> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | Alpha 1 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | found the log | ||
Created attachment 39910 [details]
found the log
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. Reassigning to the new co-maintainer of yast2-network. second service... What is status here? 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 Fixed in yast2-network 2.16.18 |
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.