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

    [solved] RA Subnets

    Scheduled Pinned Locked Moved IPv6
    37 Posts 3 Posters 5.1k 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.
    • Bob.DigB
      Bob.Dig LAYER 8 @JeGr
      last edited by

      @jegr Instantly works, thanks Jens!

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

        @jegr said in [Bug] RA Subnets:

        How about simply giving pfSense an appropriate ULA IP6 via an IP ALIAS as you want it to serve two different prefixes?

        My complaint is the alias doesn't show up anywhere other than with the ifconfig command.

        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...

        Bob.DigB JeGrJ 2 Replies Last reply Reply Quote 0
        • Bob.DigB
          Bob.Dig LAYER 8 @JKnott
          last edited by Bob.Dig

          @jknott said in [solved] RA Subnets:

          My complaint is the alias doesn't show up anywhere other than with the ifconfig command.

          That is true, now I can see this myself.

          1 Reply Last reply Reply Quote 0
          • JeGrJ
            JeGr LAYER 8 Moderator @JKnott
            last edited by

            @jknott said in [solved] RA Subnets:

            My complaint is the alias doesn't show up anywhere other than with the ifconfig command.

            Perhaps I'm tired but I can't follow :) Care to elaborate?

            Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

            If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

            JKnottJ 1 Reply Last reply Reply Quote 0
            • Bob.DigB
              Bob.Dig LAYER 8 @JeGr
              last edited by Bob.Dig

              @jegr said in [solved] RA Subnets:

              Also your firewall rules will not work in "normal" ways anymore as "<lan> network" alias won't magically include the second prefix on that interface, only the one configured via Interface setup. So watch your rules, too!

              Interestingly it worked anyway. I pinged the "lan" interface from the "voip" interface without a problem.

              PS C:\Windows\system32> ping fd28:faaf:f468:1:192:168:1:1
              
              Pinging fd28:faaf:f468:1:192:168:1:1 with 32 bytes of data:
              Reply from fd28:faaf:f468:1:192:168:1:1: time<1ms
              Reply from fd28:faaf:f468:1:192:168:1:1: time<1ms
              Reply from fd28:faaf:f468:1:192:168:1:1: time<1ms
              Reply from fd28:faaf:f468:1:192:168:1:1: time<1ms
              
              Ping statistics for fd28:faaf:f468:1:192:168:1:1:
                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
              Approximate round trip times in milli-seconds:
                  Minimum = 0ms, Maximum = 0ms, Average = 0ms
              


              Capture.JPG

              "voip" was the interface in question all the time. Will have to try from another interface to "voip".

              Bob.DigB 1 Reply Last reply Reply Quote 0
              • Bob.DigB
                Bob.Dig LAYER 8 @Bob.Dig
                last edited by Bob.Dig

                @bob-dig said in [solved] RA Subnets:

                Will have to try from another interface to "voip".

                Even this is working without any modifications @JeGr


                Capture.JPG

                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                
                1 Reply Last reply Reply Quote 0
                • Bob.DigB
                  Bob.Dig LAYER 8
                  last edited by Bob.Dig

                  So I think pfSense knows what "lan_voip net" is because of ifconfig:

                  hn4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
                          description: lan_voip
                          options=48071b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6,LRO,LINKSTATE,TXCSUM_IPV6>
                          ether 00:15:5d:82:4e:3c
                          inet6 fe80::215:5dff:fe82:4e3c%hn4 prefixlen 64 scopeid 0xa
                          inet6 fe80::1:1%hn4 prefixlen 64 scopeid 0xa
                          inet6 fd28:faaf:f468:98:192:168:98:1 prefixlen 64
                          inet6 2003:da:a711:44f0:215:5dff:fe82:4e3c prefixlen 64
                          inet 192.168.98.1 netmask 0xffffff00 broadcast 192.168.98.255
                          media: Ethernet autoselect (10Gbase-T <full-duplex>)
                          status: active
                          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • JKnottJ
                    JKnott @JeGr
                    last edited by

                    @jegr said in [solved] RA Subnets:

                    @jknott said in [solved] RA Subnets:

                    My complaint is the alias doesn't show up anywhere other than with the ifconfig command.

                    Perhaps I'm tired but I can't follow :) Care to elaborate?

                    Create an IP alias and see where it's listed. You won't see it in the web config. You have to go to a command prompt and run ifconfig to see that it's actually configured.

                    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
                    • Bob.DigB
                      Bob.Dig LAYER 8
                      last edited by

                      Some closing thoughts, I think with IPv6 it is normal to have more than one address per interface, so it would be better to have this option right in the interface-tab. Lets say I am giving input in IPv6 Configuration Type it should instantly allow for another IPv6 and so on.
                      Also what makes IPs virtual in the first place, some trickery? Again, shouldn't be needed for more IPv6-addresses.

                      JKnottJ 1 Reply Last reply Reply Quote 0
                      • JKnottJ
                        JKnott @Bob.Dig
                        last edited by

                        @bob-dig

                        I agree it should be easier to find. As for the name alias, that was even the case with IPv4, before there was IPv6. I assume it's because you have more than one address an interface can use, which is not typical. Also, with IPv6, you have not just mulitple addresses, you have multiple prefixes. Even if you don't have an alias, with SLAAC you can have up to 8 addresses, then there's link local too. By the time you've added a 2nd prefix, you're up to 17 addresses on a single interface.

                        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 1
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.