IPv6 was working yesterday, "transmit failed: Can't assign requested address"
-
I made a post on reddit about my experience setting up IPv6 prefix delegation and the fact that it stopped working after a day with an error message that doesn't bring much up when searching online. This forum has no post containing the message in the format that I see it. Asked around on the pfSense Slack but didn't get a response as of yet. Here's the post from reddit, copied verbatim:
Hello! I gave IPv6 a whirl yesterday knowing my ISP supports it. I have their modem solely running VoIP in my LAN.
Things went well at first, I requested only a prefix and no address - not sure if this is a normal step. I saw under WAN interface an IPv6 address suffixed by %vtnet0.3 which is my VLAN interface for the transport to LAN subnet. Not sure what that means. No prefix length shown, not sure what delegation I got but I checked dhcp6c logs and saw I was getting a /64 when requesting a /60 on the WAN interface with hint enabled. As I have two LANs, and only a /64 delegation, I only tracked the WAN interface on the main LAN that serves the household as opposed to my server machines. Thinking about bridging those networks in future as I have another LAN just for pfSync which I'm not using yet. I was able to get an IPv6 address on my device, but when I went to use ipv6-test.com a little later, I found that I had no IPv6 connectivity. On checking pfSense, my IPv6 address on WAN had disappeared, reverting back to IPv4 only (had both IPv4 and IPv6 before). LAN subnet also lost its WAN address in the interface list. I've tried changing Do not wait for RA, Request only an IPv6 prefix, DHCPv6 Prefix Delegation size is set to /64 as dhcp6c complained in the log about 64 + 4 + 64 being too large.
Upon checking the logs, I see a message I haven't seen before when I restart the WAN interface (transmit failed):
Jan 4 12:19:06 dhcp6c 88242 reset a timer on vtnet0.10, state=SOLICIT, timeo=2, retrans=3982 Jan 4 12:19:10 dhcp6c 88242 Sending Solicit Jan 4 12:19:10 dhcp6c 88242 set client ID (len 14) Jan 4 12:19:10 dhcp6c 88242 set elapsed time (len 2) Jan 4 12:19:10 dhcp6c 88242 set option request (len 4) Jan 4 12:19:10 dhcp6c 88242 set IA_PD prefix Jan 4 12:19:10 dhcp6c 88242 set IA_PD Jan 4 12:19:10 dhcp6c 88242 transmit failed: Can't assign requested address Jan 4 12:19:10 dhcp6c 88242 reset a timer on vtnet0.10, state=SOLICIT, timeo=3, retrans=8065I have yet to restart pfSense as I have several flatmates who are home, some of which stay up all night. Any ideas why this might be happening? It happened after I tried disabling Request only an IPv6 prefix, perhaps this affected something on my ISP's end? Would they block my connectivity if I restarted my WAN interface too frequently? I'm with Orcon, New Zealand. Technical support showed no understanding of IPv6 when I called yesterday to disable port filtering.
I've had a little bit of a search for similar posts about the message, "transmit failed: Can't assign requested address" but nothing interesting comes up. I read somewhere that there was a bug related to this issue that was fixed in 2.4.4 or similar, but I'm running 2.5.2-RELEASE. In other threads, not enough information was known to help. I haven't installed any packages. Not very sure what's going on.
Cheers :)
Any suggestions for diagnostic information I should be collecting and some next steps to take would be very much appreciated. Thanks :)
~ Oasis -
What happens if you request an address? While strictly speaking you don't need a WAN IPv6 address, there may be something about your ISP that needs it.
-
@jknott The log looks exactly the same regardless of whether I request only a prefix, or an address. No IPv6 address is assigned.
-
It might be a problem from your ISP. I had a problem with mine a few years ago. I used Wireshark to capture DHCPv6-PD and was able to identify the failing system at my ISP's head end by host name. Here's some of the text from the packet capture:
Status code
Option: Status code (13)
Length: 56
Value: 00064e6f2070726566697820617661696c61626c65206f6e...
Status Code: NoPrefixAvail (6)
Status Message: No prefix available on Link 'CMTS89.WLFDLE-BNDL1-GRP3'What happens if you do a packet capture? To do a capture, shut down pfsense and disconnect the WAN cable. Then reboot and start Packet Capture and then reconnect the cable. See what you have after a minute or twon.
-
@jknott I'll try this out when I can find a time my flatmates are all asleep (not often!). Going on a long drive today, but thanks for the tip :)
