networking – Why ping localhost from root IPv6 elected?

Linux zika.gattaca.net 5.8.0-48-generic #54-Ubuntu SMP Fri Mar 19 14:25:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I just noticed that only when I ping from the root IPv6 is elected:

root@#########:/etc/samba# ping localhost

PING localhost(localhost (::1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.226 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.204 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.177 ms
64 bytes from localhost (::1): icmp_seq=4 ttl=64 time=0.187 ms
64 bytes from localhost (::1): icmp_seq=5 ttl=64 time=0.142 ms
64 bytes from localhost (::1): icmp_seq=6 ttl=64 time=0.142 ms
64 bytes from localhost (::1): icmp_seq=7 ttl=64 time=0.213 ms
^C
--- localhost ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 137ms
rtt min/avg/max/mdev = 0.142/0.184/0.226/0.033 ms

brad@#########:~$ ping localhost

PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.194 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.131 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.130 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.133 ms
^C
--- localhost ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 80ms
rtt min/avg/max/mdev = 0.130/0.147/0.194/0.027 ms

/etc/hosts:

127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

if I ping 127.0.0.1 IPv4 is used, OK
if I ping ::1 IPv6 is used, OK

google cloud platform – Can not ping compute engine VM

In the compute engine page GCP prompted me to save $12/month by reducing the size of my VM. After selecting this option and reducing the size of my VM, I am unable to ping the external ip of the VM from external addresses. Also no web traffic. traceroute ends, does not reach the server…

Firewall rules are correct and in place to allow icmp/https/http. Also when I test various networking scenario from the compute engine is says they should work and should pass firewall rules (Ie, it says a ping from my home pc should work, but it does not)…. I am able to ping/traceroute to external ip addresses from the compute engine VM.

I’ve tried several reboots.

Any suggestions welcome. Thanks,
_Gary

networking – How can I ping a VM on a hypervisor from outside the host?

I have a CentOS 7 hypervisor running. The hypervisor IP is 192.168.195.10, and I created a VM with the IP address of 192.168.122.136 and the gateway of 192.168.122.1.

I can ping from hypervisor to the VM.

When I try to connect other computers to the network I can ping from it to the hypervisor, but I cannot get to the VM and not to the gateway of the VM.

  • Host to VM: Good
  • Outside to Host: Good
  • Outside to VM: No Good

Can someone give me direction to solve this issue?

networking – failed to ping a guest VM on virtualbox from another Linux machine

to put it simple, here are two machines in my local intranet.

One is Ubuntu based Pop!-OS computer, the other is a Windows 10 DELL desktop. Both computers are wirelessly connected to a local home network.

Now on my Windows 10 destop I installed virtualbox 6.0.1, on which I installed ubuntu based Linux distro, Kali.

For my own reason i need to set a static IP for the Kali VM, basically I followed this article for the setup. To recap, here are the specs:

  1. from the host network manager of Virtual box, the ipv4 setting is:
    192.168.56.1, DHCP disabled.
  2. For the network setting for Kali, on adapter 1 tab, the network mode
    is: NAT, on adapter2 tab, attached to host-only network configured in
    step1.

On the Kali VM, the file /etc/network/interfaces:

#The host-only network interface
auto eth1
iface eth1 inet static
address 192.168.56.101
netmask 255.255.255.0
network 192.168.56.1
broadcast 192.168.56.255

This setting was effective and verified through the command “ifconfig”

here is what I observed:

From the virtual box host (Windows 10), I can ping the guest OS (Kali):

ping 192.168.56.101

However I can’t do the same from my other computer (pop!-OS), when I ping Kali using the above same command, it returned:

(base) jon@pop-os:~$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
From 67.59.236.253 icmp_seq=1 Packet filtered

Here are a few notes worthy mentioning:

  • The gateway of the local network is: 192.168.86.1 ( I don’t know why
    the default host network on virtualbox was set to 192.168.56.1, does
    it make the virtual box and its VMs a subnet?)
  • I switch the network mode on Kali from NAT to bridged, it remained
    the same: I can’t ping from a separate computer other than the host
    DELL desktop (Window 10).
  • I don’t know where the ip 67.59.236.253 came from. It’s not the ip
    that my ISP provider assigned to me.

My goal is to be able to connect to Kali from any computer in my intranet therefore I can use its services such as database server.

Anyone please help me make things right?

network – Can Ping Google DNS from Firewall, but not from VM behind Firewall

I have the following network setup https://i.ibb.co/wwPLH2H/Network.png

All traffic from 10.0.64.0 / 27 behind FirewallB (firewallsm) reaches 192.168.28.0 / 27 network via the LAN interface of FirewallA (firewallwm), and the same traffic also reaches internet in the same way, as follows:

10.0.64.42 (VM) > FirewallB (LAN) > FirewallA (LAN) > FirewallA (WAN) > Laptop’s Wireless NIC > Wifi Router

Strangely FirewallB (firewallsm) can ping Google DNS but the VM 10.0.64.42 for some reason cannot ping Google DNS. I have set all protocols, ports as allowed on FirewallB (firewallsm) to reach FirewallA (firewallwm).

FirewallA (firewallwm)

Gateway – https://i.ibb.co/bRC8P8G/Firewall-A-GW.png

LAN Interface Rule – https://i.ibb.co/XWSnLRd/Firewall-A-1-dell-Rule.png

WAN Interface Rule – https://i.ibb.co/zZwcnjJ/Firewall-A-2-WAN-Rule.png

FirewallA (firewallsm) logs show 10.0.64.42 traffic is allowed through its WAN

Log – https://i.ibb.co/9cqPSW7/Firewall-A-Packet-log.png

Log – https://i.ibb.co/kVTX31B/Firewall-A-Packet-log-2.png

FirewallB (firewallsm)

Gateway – https://i.ibb.co/pPQC1p8/Firewall-B-GW.png

LAN Rule – https://i.ibb.co/VY9vFVL/Firewall-B-1-dell-Rule.png

tcpdump for 10.0.64.42 VM on FirewallB LAN (em0)

root@firewallsm:~ # tcpdump -i vmx0 host 10.0.64.42 and host 8.8.8.8 and icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmx0, link-type EN10MB (Ethernet), capture size 262144 bytes
06:17:09.324409 IP 10.0.64.42 > dns.google: ICMP echo request, id 1, seq 1, length 40
06:17:13.853917 IP 10.0.64.42 > dns.google: ICMP echo request, id 1, seq 2, length 40
06:17:18.858484 IP 10.0.64.42 > dns.google: ICMP echo request, id 1, seq 3, length 40

tcpdump for 10.0.64.42 VM on FirewallA LAN (em0)

root@firewallwm:~ # tcpdump -i em0 host 8.8.8.8 and icmp -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em0, link-type EN10MB (Ethernet), capture size 262144 bytes
06:17:09.335331 IP 10.0.64.42 > 8.8.8.8: ICMP echo request, id 1, seq 1, length 40
06:17:13.865408 IP 10.0.64.42 > 8.8.8.8: ICMP echo request, id 1, seq 2, length 40
06:17:23.870819 IP 10.0.64.42 > 8.8.8.8: ICMP echo request, id 1, seq 4, length 40

tcpdump for 10.0.64.42 VM on FirewallA WAN (em1)

root@firewallwm:~ # tcpdump -i em1 host 8.8.8.8 and icmp -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em1, link-type EN10MB (Ethernet), capture size 262144 bytes

Ping from FirewallB successful in pinging Google DNS

root@firewallsm:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=127 time=13.196 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=127 time=12.625 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=127 time=12.609 ms
^C
--- 8.8.8.8 ping statistics ---
16 packets transmitted, 16 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.705/13.026/15.910/1.111 ms

tcpdump of FirewallA LAN (em0)

root@firewallwm:~ # tcpdump -i em0 host 8.8.8.8 and icmp -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em0, link-type EN10MB (Ethernet), capture size 262144 bytes
06:22:21.816908 IP 192.168.10.7 > 8.8.8.8: ICMP echo request, id 23594, seq 0, length 64
06:22:21.827095 IP 8.8.8.8 > 192.168.10.7: ICMP echo reply, id 23594, seq 0, length 64
06:22:22.876598 IP 192.168.10.7 > 8.8.8.8: ICMP echo request, id 23594, seq 1, length 64
06:22:22.886317 IP 8.8.8.8 > 192.168.10.7: ICMP echo reply, id 23594, seq 1, length 64
06:22:23.948947 IP 192.168.10.7 > 8.8.8.8: ICMP echo request, id 23594, seq 2, length 64
06:22:23.957978 IP 8.8.8.8 > 192.168.10.7: ICMP echo reply, id 23594, seq 2, length 64

tcpdump of FirewallA WAN (em1)

root@firewallwm:~ # tcpdump -i em1 host 8.8.8.8 and icmp -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em1, link-type EN10MB (Ethernet), capture size 262144 bytes
06:22:21.817029 IP 192.168.47.132 > 8.8.8.8: ICMP echo request, id 24689, seq 0, length 64
06:22:21.826993 IP 8.8.8.8 > 192.168.47.132: ICMP echo reply, id 24689, seq 0, length 64
06:22:22.876700 IP 192.168.47.132 > 8.8.8.8: ICMP echo request, id 24689, seq 1, length 64
06:22:22.886219 IP 8.8.8.8 > 192.168.47.132: ICMP echo reply, id 24689, seq 1, length 64
06:22:23.949057 IP 192.168.47.132 > 8.8.8.8: ICMP echo request, id 24689, seq 2, length 64
06:22:23.957845 IP 8.8.8.8 > 192.168.47.132: ICMP echo reply, id 24689, seq 2, length 64

network – why ping registry-1.docker.io returns Request timeout for icmp_seq even when I can nslookup or dig?

I used google and cloudflare and can dig with both set as DNS server on my mac.

$ dig registry-1.docker.io

; <<>> DiG 9.10.6 <<>> registry-1.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16322
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;registry-1.docker.io.      IN  A

;; ANSWER SECTION:
registry-1.docker.io.   5   IN  A   107.23.149.57
registry-1.docker.io.   5   IN  A   34.195.246.183
registry-1.docker.io.   5   IN  A   23.22.155.84
registry-1.docker.io.   5   IN  A   34.238.187.50
registry-1.docker.io.   5   IN  A   52.1.121.53
registry-1.docker.io.   5   IN  A   52.5.11.128
registry-1.docker.io.   5   IN  A   18.213.137.78
registry-1.docker.io.   5   IN  A   54.236.165.68

;; Query time: 62 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Feb 20 23:32:34 GMT 2021
;; MSG SIZE  rcvd: 177

worked with cloudlfare too

$ dig registry-1.docker.io

; <<>> DiG 9.10.6 <<>> registry-1.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64168
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;registry-1.docker.io.      IN  A

;; ANSWER SECTION:
registry-1.docker.io.   29  IN  A   54.236.165.68
registry-1.docker.io.   29  IN  A   52.1.121.53
registry-1.docker.io.   29  IN  A   54.85.56.253
registry-1.docker.io.   29  IN  A   34.238.187.50
registry-1.docker.io.   29  IN  A   34.195.246.183
registry-1.docker.io.   29  IN  A   54.236.131.166
registry-1.docker.io.   29  IN  A   18.232.227.119
registry-1.docker.io.   29  IN  A   52.54.232.21

;; Query time: 60 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Feb 20 23:30:34 GMT 2021
;; MSG SIZE  rcvd: 177

using nslookup too gives result:
$ nslookup registry-1.docker.io
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: registry-1.docker.io
Address: 54.236.165.68
Name: registry-1.docker.io
Address: 54.85.56.253
Name: registry-1.docker.io
Address: 3.211.199.249
Name: registry-1.docker.io
Address: 34.195.246.183
Name: registry-1.docker.io
Address: 52.55.168.20
Name: registry-1.docker.io
Address: 34.238.187.50
Name: registry-1.docker.io
Address: 18.232.227.119
Name: registry-1.docker.io
Address: 54.236.131.166

but when I try to ping this is what I am getting:

$ ping registry-1.docker.io     
PING registry-1.docker.io (54.236.165.68): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4

I was trying to build a pod when I discovered this issue ! and I am getting ImagePullBackOff while trying

kubectl run redis --image=redis:alpine

terminal – when ping (or ssh) a ip or a domain on macOS, always timeout

Problem:

When I tried to ping google.com or my own server on macOS terminal, it always timeout.

PING www.google.com (172.217.2.196): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

Similar thing also happened when I tried to ssh to my server:

<username> at <computer-name> in ~
↪ ssh <server-ip>

ssh: connect to host <server-ip> port 22: Operation timed out

I’m sure that my network is working, because I am posting this question on the Mac that has the problem.

I tried:

  1. Restart my computer
  2. Turn off the firewall
  3. Connect to a VPN

But the problem still exist.

Ping Specific Site Problem

I have a post on my website; mywebsite/info/guestpost/ within that post there is a link to; guestpostsite/articles/info I want to ping the guest posts site using my site as the referrer.
When I do a Browser Ping I get the following message “Failed 200”
When I take the tick box off Browser Ping I get “Error”
My aim is to make it look like mywebsite/info/guestpost/ is referring some traffic to guestpostsite/articles/info
What am I doing wrong?