Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Azure VPN up, but only one way

    Scheduled Pinned Locked Moved IPsec
    2 Posts 1 Posters 449 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      larrycore
      last edited by

      I recently switched from a SonicWall to a Netgate. The Azure VPN was working fine on the SonicWall, allowing both directions.

      On the Netgate I set it up using the same IP and key info and it's up and running. I can access my Azure servers from my LAN with no problem.

      But, my Azure Windows servers need to access some devices on my LAN (like printers and a NAS) every now and again. This is not working. I can't even ping anything on my LAN from the Azure Windows servers.

      The child SA entry shows the correct local and remote subnets and is connected.

      I shouldn't need to add any Rules or make any NAT changes, right? The IPsec VPN takes care of all of that?

      L 1 Reply Last reply Reply Quote 0
      • L
        larrycore @larrycore
        last edited by

        Well, for anyone else that may run into this... the problem was that a Firewall Rule is needed. I was wrong to think that the VPN creation took care of that.
        Firewall Rules, IPsec is where it had to be created.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.