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

    Sendmsg: No route to host

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    14 Posts 3 Posters 2.3k 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.
    • M Offline
      maverick_slo
      last edited by

      Hmmm, but my ipv6 is working just fine
      static ones and slaac androids as well…

      1 Reply Last reply Reply Quote 0
      • B Offline
        bimmerdriver
        last edited by

        I'm still getting the same RADVD messages in the log.

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

          And your ipv6 is dead?
          I too have log entries but my ipv6 is ok.

          1 Reply Last reply Reply Quote 0
          • B Offline
            bimmerdriver
            last edited by

            It's dead. nslookup will return ipv4 and ipv6 addresses, but can only ping ipv4 addresses. ipv6-test.com and test-ipv6.com both report no ipv6.

            Aside from the above, and the radvd messages in the log, everything looks normal.

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

              Huh thats weird.
              I have same messages but ipv6 is ok.
              I have pppoe dhcpv6 isp config…

              1 Reply Last reply Reply Quote 0
              • B Offline
                bimmerdriver
                last edited by

                My ISP does not use PPPoE, but rather RFC 1483 via DHCP. Both gateways are up, DHCPv4 and DHCPv6 are up. I have a separate pfsense 2.3.4 system that is working fine. This ipv6 problem seems to be within the latest snapshots of pfsense 2.4.2.

                1 Reply Last reply Reply Quote 0
                • B Offline
                  bimmerdriver
                  last edited by

                  Looking at the list of snapshots, I think the one where it broke is either the first or send of these:

                  https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.4.2-DEVELOPMENT-amd64-20171110-0646.iso.gz

                  https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.4.2-DEVELOPMENT-amd64-20171110-1033.iso.gz

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    bimmerdriver
                    last edited by

                    This seems to be a likely culprit: https://redmine.pfsense.org/issues/8022#note-15

                    1 Reply Last reply Reply Quote 0
                    • L Offline
                      loos Netgate
                      last edited by

                      Fixed.

                      The build is still running, please wait until the next snapshot to check.

                      Thanks for reporting.

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        bimmerdriver
                        last edited by

                        @loos:

                        Fixed.

                        The build is still running, please wait until the next snapshot to check.

                        Thanks for reporting.

                        Updated, looks good.

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

                          +1
                          But strange that I had no issues…

                          1 Reply Last reply Reply Quote 0
                          • B Offline
                            bimmerdriver
                            last edited by

                            @maverick_slo:

                            +1
                            But strange that I had no issues…

                            Maybe if the log messages weren't so vague, it would shed light on why the effects of this problem were different for different users.

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