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

    RTSOLD <sendpacket> sendmsg on igb0: Can't assign requested address

    Scheduled Pinned Locked Moved IPv6
    27 Posts 2 Posters 1.9k 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.
    • JKnottJ
      JKnott @andrema2
      last edited by

      @andrema2

      I only see one DHCPv6 packet on the WAN side and it appears to be a solicit. What I'd like to see is the response. Also, what size prefix are you requesting in pfSense?

      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
      • A
        andrema2
        last edited by

        I don't know why just one. I'll leave it capturing for a longer period let's see if something shows up.

        I have WAN set up as showed below

        Screen Shot 2020-05-26 at 14.33.22.png

        The LAN is Tracking WAN.

        Should I use something smaller than 64 ?

        1 Reply Last reply Reply Quote 0
        • A
          andrema2
          last edited by

          This is a capture of 10 minutes.

          Only soliciting, no replies.

          packetcapture wan.cap

          There are IPV6 blocked by the FW at the LAN side

          Screen Shot 2020-05-26 at 14.50.35.png

          It seems a DNS query, not sure if it relates or not to the problem

          1 Reply Last reply Reply Quote 0
          • A
            andrema2
            last edited by

            Some other info from the logs

            Screen Shot 2020-05-26 at 14.58.21.png

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

              @andrema2

              Start Packet Capture, filtering on DHCPv6 on WAN. Then pull the WAN cable and plug it back in. That should cause DHCP to kick in. As I mentioned last week, DHCP only occurs at long intervals, depending on the lease time.

              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
              • A
                andrema2
                last edited by

                Ok. Just did it. I didn't see replies

                maybe I'm wrong

                packetcapture wan.cap

                1 Reply Last reply Reply Quote 0
                • A
                  andrema2
                  last edited by

                  Here's another one. I started the capture, disabled DHCP6 on the wan interface. Applied the change, went back to the dashboard and could see that there was not IPv6. Went back to the interface and enabled DHCP6, applied the change. At the dashboard it has an IPv6.

                  This is the capture of it

                  packetcapture wan.cap

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

                    @andrema2

                    In your WAN captures, I'm only seeing the Solicits from pfSense, but nothing coming back. The ISP should be responding.

                    Here's what a normal 4 step DHCPv6 process looks like. It has solicit, advertise, request and reply steps. You only have the solicit. You should be getting an advertise next.

                    DHCPv6-PD.cap

                    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
                    • A
                      andrema2
                      last edited by

                      I know.

                      It's driving me crazy. I tried again to disable DHCP6.When I went on the dashboard the IPv6 of the WAN continued there.

                      I disabled the interface, enabled it again without enabling DHCP6 and it stayed with an IPv6.

                      The only way to get rid of it was to reboot the pfsense.

                      Any new idea ?

                      I have another problem that this HW is not working as PPOE. I read something about an issue with APIC that causes the PPOE not to work. I'm thinking if there is something related to it too on the IPv6 side.

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

                        @andrema2

                        Not really. All I can suggest is to try reconfiguring pfSense from scratch. After so much, it's hard to say what you might have done. Does your ISP provide any info or support?

                        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
                        • A
                          andrema2
                          last edited by

                          Tks for your support

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