Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. azure
    Log in to post

    • All categories
    • S

      Azure pfSense Plus 23.09 VM backup failed

      Watching Ignoring Scheduled Pinned Locked Moved Virtualization azure backup waagent 23.09
      21
      1
      0 Votes
      21 Posts
      6k Views
      stephenw10S
      In the mean time you can still always make backups with it stopped. That has always worked. Though obviously it's far more inconvenient. We are digging...
    • D

      Routed IPsec to Azure

      Watching Ignoring Scheduled Pinned Locked Moved IPsec ipsec azure vti phase 1 phase 2
      1
      0 Votes
      1 Posts
      741 Views
      No one has replied
    • D

      Dynamic DNS - Azure (22.01-RELEASE (arm))

      Watching Ignoring Scheduled Pinned Locked Moved DHCP and DNS 22.01 azure ddns netgate-sg-3100
      5
      0 Votes
      5 Posts
      1k Views
      M
      @cemyl95 Funnily enough, I came to the same conclusion just this weekend :)
    • K

      Azure Dynamic DNS Fail - LocationRequired

      Watching Ignoring Scheduled Pinned Locked Moved DHCP and DNS dynamic dns azure
      2
      0 Votes
      2 Posts
      1k Views
      K
      @kilburnflyer Solved: subscriptions/[YOURSUBSCRIPTIONID/resourceGroups/north-europe-default/providers/Microsoft.Network/dnsZones/[YOURDOMAIN] do not put api version in there. in hostname only put value before i.e. RECORD i.e. RECORD.[YOURDOMAIN] Relevant link in source code helped debug
    • P

      pfSense in Azure

      Watching Ignoring Scheduled Pinned Locked Moved Firewalling azure
      2
      0 Votes
      2 Posts
      1k Views
      T
      How about multiple public ips?
    • T

      Very slow connection using pfsense to azure vm

      Watching Ignoring Scheduled Pinned Locked Moved General pfSense Questions azure vpn ipsec slow throughput
      3
      0 Votes
      3 Posts
      2k Views
      T
      After contact with microsoft helpdesk I found the solution for me. For future reference: I had to turn on mss clamping and set it to 1350. This is also in the advanced IPSec settings Maybe this settings was defaulted after an update? I wasn't the one who configured it in the first place, so I wouldn't know for sure. I made sure to match my settings to this document https://docs.microsoft.com/nl-nl/azure/vpn-gateway/vpn-gateway-about-vpn-devices @stephenw10 Thanks for the reply, I had this disabled already, but the pointer was appreciated