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

    Azure Portal not working with IPv6

    Scheduled Pinned Locked Moved IPv6
    12 Posts 3 Posters 2.2k Views 3 Watching
    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.
    • M Offline
      mewsense @FollyDude 0
      last edited by

      @FollyDude-0

      I just double checked, you're right it's a /48. Thanks for checking Azure Portal for me.

      Must be something in my pfSense configuration then? Where would I look to fix that.

      F 1 Reply Last reply Reply Quote 0
      • F Offline
        FollyDude 0 @mewsense
        last edited by

        @mewsense

        Can you check ping from your client machine to portal.azure.com? Make sure you are pinging the IPv6 address, I don't know what client machine you are using, but something like ping -6 portal.azure.com or ping6 portal.azure.com.

        Can you access other sites via IPv6, or is this just a problem with azure? Also check connectivity with one of the many IPv6 test sites.

        Hope this helps.

        F

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mewsense @FollyDude 0
          last edited by

          @FollyDude-0 Thanks it's weird. I'm going to try and connect a different router tomorrow and try to rule out pfSense.

          https://test-ipv6.com/

          shows:
          ed89cc2d-571d-4c23-8a87-00a505b9b90e-image.png

          All other IPv6 sites work fine.

          ping -6 portal.azure.com
          
          Pinging s-part-0046.p-0010.p-msedge.net [2603:1061:11::46] with 32 bytes of data:
          Reply from 2603:1061:11::46: time=8ms
          Reply from 2603:1061:11::46: time=7ms
          Reply from 2603:1061:11::46: time=8ms
          Reply from 2603:1061:11::46: time=8ms
          
          Ping statistics for 2603:1061:11::46:
              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
          Approximate round trip times in milli-seconds:
              Minimum = 7ms, Maximum = 8ms, Average = 7ms
          
          M 1 Reply Last reply Reply Quote 0
          • M Offline
            mewsense @mewsense
            last edited by

            I dug out my old Netgate SG-1000 router, and factory reset it, reconfigured it to use IPv6, and I see the exact same behaviour!

            Maybe I will contact Azure Support to see if they can figure it out. At least I know it's not my pfSense configuration.

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              FollyDude 0 @mewsense
              last edited by

              @mewsense

              Hi, you could still have a config problem with your router. Do you have the Router that zen supplied you? Could you try that?

              F

              M 2 Replies Last reply Reply Quote 0
              • M Offline
                mewsense @FollyDude 0
                last edited by mewsense

                @FollyDude-0

                This is true, however I don't have the router that was supplied from Zen anymore. Maybe I should buy a cheap one off eBay as a test? Can you suggest something? Maybe the TP-Link Archer C50 or C6 as a test?

                1 Reply Last reply Reply Quote 0
                • M Offline
                  mewsense @FollyDude 0
                  last edited by

                  @FollyDude-0 I have connected a tp-link Archer C6 router and configured it for IPv6 and everything is working fine.

                  So there is something in the pfsense configuration using factory defaults for the SG-1000 and my current configuration on my Protectli router that has pfsense CE that is causing the Azure Portal and some other MSFT services to not work.

                  At least I know it's pfsense that is causing the problem. I will see if I can figure it out but if you have any ideas let me know! :)

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    mewsense
                    last edited by

                    I SOLVED IT! I SOLVED IT! I SOLVED IT!

                    In Interfaces → WAN → MSS: 1420

                    F 1 Reply Last reply Reply Quote 0
                    • F Offline
                      FollyDude 0 @mewsense
                      last edited by

                      @mewsense

                      That is good news, I would never have guessed that would fix it.

                      F

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        pulsecity
                        last edited by pulsecity

                        MSS 1420 fixed the same issue on OPNsense, so I assume this is something common to both maybe a FreeBSD quirk. I remembered to set the MTU to 1508 at the same time,

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