DHCPv6 pool range incorrect



  • Hello,
    I have a problem setting up my DHCPv6 Server. I configured the interface with a static IPv6 address [::ffff:10.1.0.1/120]. I expect this to translate into [::ffff:a01:1/120]. When I try to configure a DHCPv6 server range the subnet is displayed as [::1:ffff:101/120] and the available range is from [::1:ffff:101] to [::1ff:ff01:1ff]. I would expect the range to be from [::ffff:a01:1] to [::ffff:a01:fe].
    Can you please help me understand how pfSense ends up with this subnet?
    Thanks


  • Galactic Empire

    ::ffff:10.1.0.1/120 isn't that an IPv4 in IPv6 address ?

    What happens if you put 0:0:0:0:0:ffff:a01:1 in as the router address ?



  • I understand the last sentence here: https://en.wikipedia.org/wiki/IPv6_address#Representation that I'm allowed to do this.

    Wikipedia:
    During the transition of the Internet from IPv4 to IPv6, it is typical to operate in a mixed addressing environment. For such use cases, a special notation has been introduced, which expresses IPv4-mapped and IPv4-compatible IPv6 addresses by writing the least-significant 32 bits of an address in the familiar IPv4 dot-decimal notation, whereas all preceding ones are written in IPv6 format. For example, the IPv4-mapped IPv6 address ::ffff:c000:0280 is written as ::ffff:192.0.2.128, thus expressing clearly the original IPv4 address that was mapped to IPv6.

    And I guess pfSense wouldn't allow me to save it, if it wasn't a correct IPv6 address.

    When I put in ::ffff:a01:1/120 it works perfectly. The point of the IPv4 notation is simple legibility. I was hoping i could simplify my IPv6 adresses this way.


Log in to reply