Summary: | network interfaces does not show gateway ip address | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | illumilore <illumilore> |
Component: | Plasma Widget | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lamarque, maarten.bezemer, rajeeshknambiar, wstephenson |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | a051905b894ee5a3c1becfc9dc78f763df10bb8e | Version Fixed In: | master branch |
Sentry Crash Report: | |||
Attachments: | Display Gateway, Netmask, DNS details in inteface details tab |
Description
illumilore
2012-01-05 00:05:23 UTC
*** Bug 296619 has been marked as a duplicate of this bug. *** Besides the gateway information, it would also be nice to see other information about my currently connected network, like information about IP address, DNS servers, netmask, etc. Created attachment 70281 [details]
Display Gateway, Netmask, DNS details in inteface details tab
Here's a patch implementing the requested feature, showing default gateway, broadcast address, subnet mask and primary/secondary/ternary DNS details.
I dislike this implementation for the reason that the height of Plasma NM applet is now way too much (visit the interface details tab, and click on 'Back' button to come back and observe the height increase).
Lamarque, I see that you have planned to add GSM details in another tab. Should we go that way - what do yo suggest?
I prefer to create a dialog to select which details to show like the one that existed for knetworkmanager. I started to implement such a dialog but has never finished it. Commit http://commits.kde.org/networkmanagement/a051905b894ee5a3c1becfc9dc78f763df10bb8e implements the details editor and allows you to select to show the default gateway. Just a warning that at least NetworkManager 0.9.2.0 and 0.9.4.0 do not report the default gateway IPv4 address if the interface is using static configuration. I have tested it using qdbusviewer so this is an upstream bug. |