Score:0

Azure Virtual Gateway gets "Not connected" when peering a vnet

mx flag

0

I have an Azure Virtual Gateway connection from 10.29.64.128/26 to another Local Gateway that works fine.

I need some additional address space in order to outbound connections and I decide to pair another Vnet to the existing one.

As soon as I add a Vnet paired network for example to 10.29.64.0/26 to the previous one Virtual Gateway connection changes from "Connected" to "Not Connected".

Both address spaces do not overlap. What could be the cause?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.