👀 Views: 0 💬 Answers: 1 📅 Created: 2025-06-12

gcp vpc networking bash

I'm currently working with an scenario with GCP VPC peering between two projects where the traffic is not being routed correctly. I've set up the peering between Project A (containing VPC-A) and Project B (containing VPC-B), but when I try to ping an instance in VPC-B from an instance in VPC-A, I receive a 'Destination Host Unreachable' behavior. Here are the steps I've taken: 1. Created a VPC in each project and ensured there are no overlapping CIDR ranges. VPC-A is using `10.0.0.0/16` and VPC-B is using `10.1.0.0/16`. 2. Established the VPC peering using the GCP Console and confirmed that the peering status is 'ACTIVE'. 3. Updated the firewall rules in both projects to allow ICMP traffic: ```bash gcloud compute firewall-rules create allow-icmp --allow icmp --network vpc-a gcloud compute firewall-rules create allow-icmp --allow icmp --network vpc-b ``` 4. Checked routing tables to ensure they include the respective peering routes. Despite all this, the instances want to communicate. I've verified that there are no IAM permission issues set on the projects, and I can access the instances from the respective VPCs independently. I've also attempted to use the `gcloud compute ssh` command to connect to the instances and run traceroute, but it consistently fails at the first hop when addressing the external IP of the other project. Is there a missing configuration or a common pitfall that I might have overlooked? Any insights or suggestions would be greatly appreciated! I'm coming from a different tech stack and learning Bash. What's the correct way to implement this?