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

    Some sites inaccessible with IPv6 with 23.05

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 719 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.
    • E
      ebcdic
      last edited by ebcdic

      After updating to 23.05 (on an SG-1100), the Signal app on my Mac was unable to connect. There had been occasional disconnections before, but after the update it wouldn't connect at all. Disabling IPv6 on the Mac fixes it.

      I saw a suggestion elsewhere of using "curl k https://textsecure-service.whispersystems.org/" to test Signal connectivity. This returns 404 (as expected) if I use "curl -4", but hangs indefinitely with "curl -6".

      Most other sites such as google.com work perfectly well with IPv6, but at least one other site has the same problem (https://cemantle.certitudes.org/).

      And running the curl commands on the router itself works fine for both IPv4 and IPv6. Which suggests the problem is on the LAN side, but why then would it work for other sites? It's all very mysterious.

      E 1 Reply Last reply Reply Quote 0
      • E
        ebcdic @ebcdic
        last edited by

        I have found that reducing the MTU on my Mac to 1492 fixes the problem - though only on that Mac of course. Does this suggest an IPv6 MTU discovery problem?

        JKnottJ 1 Reply Last reply Reply Quote 1
        • JKnottJ
          JKnott @ebcdic
          last edited by

          @ebcdic

          If so, only with the Mac, as PMTUD is only performed by the end device, not any router.. Are you on ADSL? That's where you normally use the smaller MTU. What's happening with IPv4? Is it using PMTUD or fragmenting? You can use packet capture or Wireshark to capture some packets and examine the do not fragment flag.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          • E
            ebcdic
            last edited by

            It now seems likely that this wasn't related to the 23.05, but to a change in the Signal app around the same time which causes it to start preferring IPv6 over IPv4. There's a thread about it at https://github.com/signalapp/Signal-Desktop/issues/6393

            It's still mysterious what the actual problem is.

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