October 10, 2026
How firewall rules changed my Google Cloud ping tests
I tested which traffic could reach two virtual machines, then used a load balancer to distribute requests across three web servers.
Testing firewall behavior and distributing requests across three web servers.
A cloud network needs deliberate rules for which machines can communicate, while a public web endpoint needs a way to spread traffic across multiple servers.
Cross-region communication inside one VPC.
Ping results changed as ingress rules were removed.
One public endpoint returned responses from each backend.
Created a VPC and VMs in us-central1 and us-east1, then verified 3 of 3 ping responses to the second VM's internal and external addresses.
Deleted the ICMP allow rule; the external ping lost all three packets while the internal ping still worked.
Deleted the internal custom allow rule; the internal ping then lost all three packets.
Created three Apache VMs, a health check, target pool, reserved IP, and forwarding rule; repeated curl requests returned www1, www2, and www3.
Removed the temporary load balancer, servers, firewall rules, VMs, and VPC after testing.
The screenshots document the changed network behavior and the three backend responses. The lab infrastructure was temporary and removed after testing.
October 10, 2026
I tested which traffic could reach two virtual machines, then used a load balancer to distribute requests across three web servers.
Continue exploring
Back to all projects