On 2020-08-04 06:48, ToddAndMargo via users wrote:

>
> I see you have two gateways.  Would you mind posting your
> `netstat -n`?

I think you want "netstat -rn".  And, yes, I've already said, at least twice, 
that I have 2 "default gateways"
I already said it is for the case where one path is down.

[egreshko@meimei ~]$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 enp2s0
0.0.0.0         192.168.2.5     0.0.0.0         UG        0 0          0 wlp4s0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 enp2s0
192.168.2.0     0.0.0.0         255.255.255.0   U         0 0          0 wlp4s0
192.168.56.6    192.168.2.116   255.255.255.255 UGH       0 0          0 wlp4s0
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 virbr0

This gives insufficient information about the usages of the "default gateways".

[egreshko@meimei ~]$ ip -4 route
default via 192.168.1.1 dev enp2s0 proto static metric 100
default via 192.168.2.5 dev wlp4s0 proto dhcp metric 600
192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.18 metric 100
192.168.2.0/24 dev wlp4s0 proto kernel scope link src 192.168.2.127 metric 600
192.168.56.6 via 192.168.2.116 dev wlp4s0 proto static metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

is better for that since it shows the metric.  Not that it would always be of 
interest but with ip
you know if the route was configured via dhcp, is a static route, or was added 
by the kernel.

>
>
>>> So, I do believe you are connect.  "nmcli" can not
>>> tell me who is Red and who is Black.  "route" or
>>> "netstat" are what is initially called for.
>>
>> I *didn't* say that at all.  In another message I said nmcli can't tell you 
>> if the gateway is UP.  
>
> not looking for that kind of "up"

I do not know what kind of "up" you mean then.

>
>> And, neither
>> can netstat or route.  And, that I thought was your goal to verify the 
>> gateway being up.
>>
>> For that, you normally use ping.
>
> Again, I am looking for the configuration, not whether it
> works or not.

OK, but you kept saying....  "I only want to know if the device is connected to 
the
gateway and the gateway is up."  and even Samuel replied with "The only way to 
tell if the gateway is up is to ping it or connect to it in some way."

So, I don't know what your "up" means.


-- 
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Reply via email to