👀 Views: 90 💬 Answers: 1 📅 Created: 2025-06-11

gcp vpc networking bash

I'm trying to set up VPC peering between two different GCP projects so that they can communicate with each other. I've configured the necessary IAM roles for both projects and created the peering connection, but I'm working with a 'Route Not Found' behavior when attempting to ping an instance in the second project. Here are the steps I’ve taken: 1. In the first project (let's call it Project A), I created a VPC network named 'vpc-a' with a CIDR block of 10.0.0.0/16. 2. In the second project (Project B), I created a VPC network named 'vpc-b' with a CIDR block of 10.1.0.0/16. 3. I initiated the peering request from Project A to Project B, and it seemed to succeed without issues. 4. On the VPC networks page, I can see that the peering status is 'ACTIVE' for both networks. 5. I've also added routes in both projects to allow traffic to the other's CIDR blocks. 6. I ensured that the firewall rules allow ICMP protocol to test connectivity. Here is the command I used to create the peering from Project A: ```bash gcloud compute networks peerings create vpc-a-to-vpc-b \ --network=vpc-a \ --peer-network=projects/PROJECT_B_ID/global/networks/vpc-b \ --project=PROJECT_A_ID ``` And I verified the peering with: ```bash gcloud compute networks peerings describe vpc-a-to-vpc-b --network=vpc-a --project=PROJECT_A_ID ``` When I try to ping an instance in Project B from an instance in Project A, I get the following behavior: `ping: sendmsg: Network is unreachable`. I could use some guidance on what I might be missing or if there are additional configurations needed to ensure that the routing works correctly between these two projects.