Verifique se o nome da interface está presente em sua máquina. Verifique fazendo os comandos ifconfig
ou ip addr show
ou ip link show
.
Você também pode fazer alguma solução de problemas usando os comandos ip route show
e traceroute -i
.
Está funcionando como mostrado abaixo:
[iahmad@ijaz-cms ~]$ ping -I enp0s25 www.google.com
PING www.google.com (172.217.18.100) from 137.138.52.207 enp0s25: 56(84) bytes of data.
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=1 ttl=54 time=4.88 ms
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=2 ttl=54 time=4.97 ms
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=3 ttl=54 time=5.01 ms
^C
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 4.885/4.958/5.019/0.055 ms
[iahmad@ijaz-cms ~]$ ping -I 137.138.52.207 www.google.com
PING www.google.com (172.217.18.100) from 137.138.52.207 : 56(84) bytes of data.
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=1 ttl=54 time=4.98 ms
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=2 ttl=54 time=4.93 ms
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=3 ttl=54 time=4.96 ms
64 bytes from zrh04s05-in-f4.1e100.net (172.217.18.100): icmp_seq=4 ttl=54 time=4.98 ms
^C
--- www.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 4.939/4.966/4.983/0.017 ms