Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,809 questions
Local Network Gateway Address Spaces
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 7.000000000000001%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Muzi Mkhize
1
Reputation point
Good day Community,
In recent weeks i have been experiencing issues with address spaces on the local network gateway in that i am only able to communicate with on-premise devices that are on a /24 subnet, inputting any other subnet i.e. /22 or /23 yields to no communication.
Have any of you come across this issue?
Kind Regards;
Muzi
Azure VPN Gateway
{count} votes
-
KapilAnanth-MSFT 49,626 Reputation points Microsoft Employee Moderator2022-11-30T06:50:35.377+00:00 Hi @Muzi Mkhize ,
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are facing issues with LNG address space not able to use /22 or /23 ranges.Ideally, this should not be the case.
When you change the address space,
- Is the tunnel still showing as Connected or it becomes Not Connected?
- Can you check the VPN gateway logs for IKEdiagnostics, and see what is the traffic selector that got negotiated?
- Does your Onprem address range has a /22 or /23 address range?
- Make sure the Traffic selector configured at the OnPrem device matches the one you are specifying in the LNG.
Cheers,
Kapil
Sign in to comment
Sign in to answer