Amazing video. one of the best, shortest, for profession by profession videos... Most videos on this topic, insist on walking you over "what is a VNET". This get's to the point fast!
Thank you so much for this video. This was one question during my interview few days ago. Also I didn’t understand what exactly is ‘hop’ which makes sense now from this video. Thank you Sir..
Great video, I did not know one could use a VPN Gateway as a router. Having said that, regarding what you said about being complicated by the need to create a route table per vnet, if you are using a third party NVA in the Hub network, you can create only one route table with the default route pointing to NVA ip address. Then this could make things much simpler. Of course you need the proper configuration on the NVA itself.
Thank you so much for putting this together. I have been trying to figure out my vnet to s2s vnet routing for hours and could only find resources talking about azure vnet to vnet, but you talking about route table made it all click! Duh! Why didn't I think, "I wonder if there is a route table"
Very helpful video, thank you! Is there any way that allows automatic route adding in the route tables? That would make the process much simpler for large scale solutions.
hi Travis, Excellent explanation. I have created a similar setup with 2 Spoke and 1 Hub networks in Azure. I have couple of queries, 1. I created RouteTable1 and assigned it to Spoke-1. Added a route to access Spoke-2 network via Hub VNET. Ideally, I should be able to ping the VM-2 from VM-1 since there is a route established from Spoke-1 and Spoke-2 network. But, I am unable to achieve. Unless I add RT-2 assigned to Spoke-2 VNET and add a route to access Spoke-1 VNET, then, I am able to access both VMs (ping each other). Why is it so? 2. After performing step (1), I went to Spoke-1 Peering (wtih Hub) and Disable the option "Allow 'vnet-1' to receive forwarded traffic from 'vnet-hub'". Ideally, this will stop traffic flow from Spoke-2 to Spoke-1 (VMs). But, I see the VM-2 is still able to reach to VM-1. Why? Thanks.
Great video as always. Just wanted to ask, I'm confused with the setup we have in our vpn gateway. Someone set up a vpn gateway with vnet1 (no subnets except for gateway subnet) with peering to vnet2 (all production subnets). Basically, instead of connection to the actual vnet. He added a peering so traffic will flow to another vnet. I was surprised it is working but I could not find any benefits, there are no devices in the vnet1. Should I remove the peering?
That sounds like a hub and spoke design and is fairly common. In that configuration, more VNets could be added and all of them use the same gateway. that's cheaper and easier then deploying a gateway on each vnet.
@@Ciraltos Thank you for the clarification. I'd like to ask another question. I have a Meraki vmx setup for S2S in Azure to connect on-premise networks. Do you know if I can use the hub vNet for this? So it will P2S and S2S on the same hub vNet.
Thanks for the video , is there a difference between configuring the peering from the HUB ? otherwise why you choose to create the peering from Spoke to peering ?
Hi Travis, I want to use a point-to-site vpn tunnel with vpn gateway to connect to four different azure subscriptions. What would be my best approach. Also I don't want these resources to share any data or connectivity with other subscriptions like dev and prod.
Hi Travis, what about this scenario ? hub and spoke1 have own vnet gateway. how to set the route table ? i tried set it next hop to virtual network gateway, it's not connected.
Short and lot of details. Thanks a lot. I have an issue. I have hub and spoke model. i have a vm in hub and a vm in spoke. i use point to site. The issue is, i am able to RDP the vm on Hub but not able to control/RDP the vm on Spoke. Both the vnet's are peered. What could be the issue?
Morning Travis! can I ask why you dont recommend this for production? in terms of using the Gateway for the transitive routing as I use a similar set up in my production environment thank in advance
Hub and spoke is the preferred way to connect multiple VNets. The caution is about using a VNet gateway as the router. VNet gateways are made to encrypt traffic and although they will work, Microsoft recommends against it. learn.microsoft.com/en-us/azure/architecture/networking/spoke-to-spoke-networking?WT.mc_id=AZ-MVP-5004159#pattern-2-spokes-communicating-over-a-network-appliance
@@Ciraltos Thanks for your responsem what about in a site to site context using the virtual network gateway transit setting in the VNETs peered to the HUB is that considered ok for production?
Wouldn't this cause delay because the traffic goes from the virtual network to other virtual network through the hub each time ? And this would get worst with any additional virtual network added to the system?
![Twenty One Pilots - “The Line” (from Arcane Season 2) [Official Music Video]](http://i.ytimg.com/vi/E2Rj2gQAyPA/mqdefault.jpg)
Amazing video. one of the best, shortest, for profession by profession videos... Most videos on this topic, insist on walking you over "what is a VNET". This get's to the point fast!
Glad you liked it!
Thank you so much for this video. This was one question during my interview few days ago. Also I didn’t understand what exactly is ‘hop’ which makes sense now from this video. Thank you Sir..
Great video, I did not know one could use a VPN Gateway as a router. Having said that, regarding what you said about being complicated by the need to create a route table per vnet, if you are using a third party NVA in the Hub network, you can create only one route table with the default route pointing to NVA ip address. Then this could make things much simpler. Of course you need the proper configuration on the NVA itself.
as always, brilliant and to the point introduction. Thanks
Thank you so much for putting this together. I have been trying to figure out my vnet to s2s vnet routing for hours and could only find resources talking about azure vnet to vnet, but you talking about route table made it all click! Duh! Why didn't I think, "I wonder if there is a route table"
Awesome ! You make everything look so simple. That is Great !!! 🙂 Thank you May God bless you.
liked the video right from the first few seconds of introduction ,great
Great video, thanks. Now, the same video but a Azure Firewall, please.
clear and complete, thank you!
Great Videos man 🙌🙌🙌🙌🙌 continue doing the Lord's work.... Can you do something on Azure Landing Zone?
great video, the explication is ease
Very helpful video, thank you! Is there any way that allows automatic route adding in the route tables? That would make the process much simpler for large scale solutions.
Awesome & easy
Agradecer por el contenido!!!
Great video. Is it possible to connect spoke1 to spoke2 without UDR or direct peering?
hi Travis, Excellent explanation. I have created a similar setup with 2 Spoke and 1 Hub networks in Azure. I have couple of queries,
1. I created RouteTable1 and assigned it to Spoke-1. Added a route to access Spoke-2 network via Hub VNET. Ideally, I should be able to ping the VM-2 from VM-1 since there is a route established from Spoke-1 and Spoke-2 network. But, I am unable to achieve. Unless I add RT-2 assigned to Spoke-2 VNET and add a route to access Spoke-1 VNET, then, I am able to access both VMs (ping each other). Why is it so?
2. After performing step (1), I went to Spoke-1 Peering (wtih Hub) and Disable the option "Allow 'vnet-1' to receive forwarded traffic from 'vnet-hub'". Ideally, this will stop traffic flow from Spoke-2 to Spoke-1 (VMs). But, I see the VM-2 is still able to reach to VM-1. Why?
Thanks.
Great video as always.
Just wanted to ask, I'm confused with the setup we have in our vpn gateway. Someone set up a vpn gateway with vnet1 (no subnets except for gateway subnet) with peering to vnet2 (all production subnets). Basically, instead of connection to the actual vnet. He added a peering so traffic will flow to another vnet. I was surprised it is working but I could not find any benefits, there are no devices in the vnet1. Should I remove the peering?
That sounds like a hub and spoke design and is fairly common. In that configuration, more VNets could be added and all of them use the same gateway. that's cheaper and easier then deploying a gateway on each vnet.
@@Ciraltos Thank you for the clarification. I'd like to ask another question.
I have a Meraki vmx setup for S2S in Azure to connect on-premise networks. Do you know if I can use the hub vNet for this? So it will P2S and S2S on the same hub vNet.
Thanks for the video , is there a difference between configuring the peering from the HUB ? otherwise why you choose to create the peering from Spoke to peering ?
Are you using VPN gateway as cost effective example for VWAN over S2S or ER?
Hi Travis, I want to use a point-to-site vpn tunnel with vpn gateway to connect to four different azure subscriptions. What would be my best approach. Also I don't want these resources to share any data or connectivity with other subscriptions like dev and prod.
Hi Travis, what about this scenario ? hub and spoke1 have own vnet gateway. how to set the route table ? i tried set it next hop to virtual network gateway, it's not connected.
Short and lot of details. Thanks a lot. I have an issue. I have hub and spoke model. i have a vm in hub and a vm in spoke. i use point to site. The issue is, i am able to RDP the vm on Hub but not able to control/RDP the vm on Spoke. Both the vnet's are peered. What could be the issue?
what virtual machine are you using sir?
Morning Travis! can I ask why you dont recommend this for production? in terms of using the Gateway for the transitive routing as I use a similar set up in my production environment thank in advance
Hub and spoke is the preferred way to connect multiple VNets. The caution is about using a VNet gateway as the router. VNet gateways are made to encrypt traffic and although they will work, Microsoft recommends against it. learn.microsoft.com/en-us/azure/architecture/networking/spoke-to-spoke-networking?WT.mc_id=AZ-MVP-5004159#pattern-2-spokes-communicating-over-a-network-appliance
@@Ciraltos Thanks for your responsem what about in a site to site context using the virtual network gateway transit setting in the VNETs peered to the HUB is that considered ok for production?
Wouldn't this cause delay because the traffic goes from the virtual network to other virtual network through the hub each time ? And this would get worst with any additional virtual network added to the system?
HELP