- A virtual network exists
- Within a specific subscription
- Within a specific region
- spans multiple AZs in that region
- It cannot span subscriptions nor regions
- A virtual network consists of one or more IP ranges
- IP address type:
- Allocation can be static or dynamic
- Typically from RFC 1918 but not exclusively
- The address space is broken up into subnets with the smallest subnet possible being a /29 which will give 3 usable IP addresses
- From every subnet we lose 5 IPs
- .0 - NW
- .1 - GW
- .2-.3 - DNS
- .255 - broadcast
- Can be ipv6 as well/ but not only ipv6
- Subnets are regional and span Availability Zones
- Ingress is free, Egress costs money
Supported types of traffic
- Standard IP-based protocols supported including:
- TCP
- UDP
- ICMP (Ping)
- Multicast, broadcast, IP-in-IP encapsulated packets and Generic Routing Encapsulation (GRE) blocked
- Can not deploy DHCP server
- You cannot ping the Azure gateway or use tools such as tracert
- Traditional Layer 2 VLANs are not supported
Commands
202407141408 Create VNet in Azure
az network vnet create --name vnet-1 --resource-group test-rg --address-prefix 10.0.0.0/16 --subnet-name subnet-1 --subnet-prefixes 10.0.0.0/24
references:
Paths into this note
19 notes lead here
-
No access to peered VNets
-
log traffic flowing through VNet
-
If any VNet changes, for example new VNet Peering etc, need to reinstall VPN client with new config downloaded from Azure
-
Gateway transit makes it so, that I don't have to setup a Azure VPN Gateway in the peer VNet
-
A VNet in the resource group
-
Create VNet in Azure
-
provides different VNet integration options
-
Apps deployed in the same environment are deployed to same VNet and write logs to the same log analytics workspace.
-
VNet can use Azure DNS or custom/private DNS
-
When an externally facing Azure PaaS service is accessed from a resource in a VNet the traffic stays on the Azure network
-
To segment and control traffic within a VNet, between networks and/or external a number of approaches can be utilised
-
VNet Peering enables VNets to be connected via the Microsoft backbone in the same or different regions (global peering)
-
Each NIC can be in same or different virtual subnet but always in same VNet