Bug 1870059
| Summary: | [RFE] show gateway instead of 0.0.0.0/0 in nmcli output | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Vladimir Benes <vbenes> |
| Component: | NetworkManager | Assignee: | Vojtěch Bůbela <vbubela> |
| Status: | CLOSED ERRATA | QA Contact: | David Jaša <djasa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 8.3 | CC: | acardace, bgalvani, fge, lrintel, rkhan, sukulkar, thaller, till |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.34.0-0.1.el8 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 14:54:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hi Vladimir, This is decorative and controversial. Can we close till this cause real problem(for me, 0.0.0.0/0 and ::/0 works well)? (In reply to Gris Ge from comment #3) > Hi Vladimir, > This is decorative and controversial. > > Can we close till this cause real problem(for me, 0.0.0.0/0 and ::/0 works > well)? This bug was about the nmcli command not saying what the gateway is. We can see it via the ip r command but one cannot easily guess it from the nmcli output, that's it. in kernel, routes can have many attributes (beside the gateway). Most (not all) of these attributes are also part of what identifies the route. That is their "primary key" which identifies them. for example, we can add two routes that are identical except a different "window". On D-Bus API and in nmcli, we only expose a subset of these attributes. Hence, such two routes would look indentical on nmcli/D-Bus, while they differ in yet another attribute that is invisible. That is a bit odd. Eventually we should expose "all" attributes (which is a never ending task as new attributes get added). For starters, it's of course good and right to show the gateway!! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:1985 |
Description of problem: checking default gateway is not possible for a human via one command in nmcli. First you need to check which profile is connected via nmcli or nmcli con and then nmcli con show $profile |grep GATEWAY (or scroll down). I think nmcli command should show something like ip a s; ip r; ip -6 r. Now it just shows incomplete info. We should fix it. wlp2s0: connected to legacy "Intel 8265 / 8275" wifi (iwlwifi), 48:A4:72:0B:E7:F3, hw, mtu 1500 ip4 default inet4 192.168.1.40/24 route4 0.0.0.0/0 route4 213.175.37.11/32 route4 192.168.1.1/32 route4 192.168.1.0/24 route4 192.168.1.40/32 inet6 fe80::5868:6f91:2ff:e341/64 route6 fe80::/64 route6 fe80::5868:6f91:2ff:e341/128 route6 ff00::/8 we know driver, profile, ip4/6 address but we cannot easily see default route now. I think we should have gateway4 or something like that. Version-Release number of selected component (if applicable): 1.26.0-6 How reproducible: always Steps to Reproduce: 1. run nmcli Actual results: no gateway Expected results: gateway should be shown different way than other routes Additional info: my actual ip 4 output: $ ip r default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 10.0.0.0/8 via 10.40.192.1 dev tun0 proto static metric 50 10.40.192.0/20 dev tun0 proto kernel scope link src 10.40.194.112 metric 50 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.40 metric 600 192.168.1.1 dev wlp2s0 proto static scope link metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 213.175.37.11 via 192.168.1.1 dev wlp2s0 proto static metric 600