Spoke-to-spoke fails through a new hub
vm-spoke1 can't reach vm-spoke2 on 443 through fw-hub.
- Get vm-spoke1 reaching vm-spoke2 on 443
- Send that traffic through fw-hub
- Don't peer the spokes directlybroken
Background
A new vnet-hub, with the appliance fw-hub at 10.0.2.4, was peered to both spokes last week, and the spoke route tables send spoke-to-spoke traffic to fw-hub. Each spoke can talk to the hub itself, but vm-spoke1 (10.1.1.4) can't reach vm-spoke2 (10.2.1.4) on 443 through fw-hub. Working means that traffic flows through fw-hub, without peering the spokes to each other.
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMsssh vm-spoke1What's this?
Opens a shell on vm-spoke1, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
nc -zv 10.2.1.4 443What's this?
netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
-zonly check whether the port answers. Send no data-vprint the result in words10.2.1.4where to connect443the port to try
Ticks off when the test runs on vm-spoke1.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
- 5Explain it
?
- Resource group, the outer dashed frame
- Virtual network, with its address space top right
- Subnet, with range and usable IPs (5 reserved)
- Network security group. A small shield on a VM's NIC means the NIC has one too
- Route table on the subnet
- VM Appliance Private endpoint
- Peering Connected Initiated or access off
- Goal working Goal broken, X marks where it stops
- Private DNS zone, dotted lines go to linked VNets
- Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.
vm-spoke1 → vm-spoke2:443should work: not working