XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    IPv6 support in XCP-ng for the management interface - feedback wanted

    News
    9
    40
    3533
    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.
    • BenjiReis
      BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ @AtaxyaNetwork last edited by

      @ataxyanetwork you're right. I just wanted to know to reproduce as much as possible your environment. Plus IPv6 only will be easier to debug, dual mode can have some weird magic happening at time!

      I'll take a look ASAP and post here about my findings ๐Ÿ™‚

      AtaxyaNetwork 1 Reply Last reply Reply Quote 0
      • AtaxyaNetwork
        AtaxyaNetwork Ambassador ๐Ÿ“ฃ @BenjiReis last edited by

        @benjireis Great !

        Don't hesitate to ping me if you have questions !

        Cรฉcile ~ AtaxyaNetwork

        BenjiReis 1 Reply Last reply Reply Quote 0
        • LeMatz
          LeMatz last edited by LeMatz

          Hey guys,

          first thing we found during the installation:

          The DNS dialogue doesn't like the shortest possible way to write an IPv6. According to my local nslookup, the IP notation is correct.

          screenshot1.png

          screenshot2.png

          But if I fill the zeroes out, everything works fine:

          screenshot3.png

          Thanks,
          Matthias

          H 1 Reply Last reply Reply Quote 0
          • LeMatz
            LeMatz last edited by

            Hey guys,

            one more thing:

            On the console, we are able to see the network address:

            d408aad8-2668-43bf-b61c-7bf66c9d2cbe-grafik.png

            But on XCP-ng Center, the IP is not shown:
            5d7181fc-78f8-470c-8841-12a20f3602b3-grafik.png

            I'm not sure, if this is merely a problem with the Center, or if XOA has this problem as well. We are not able to install the XOA, as we tried to bind our free IPv4 address to XOA as well and just got an error:

            628951e8-269d-497d-9da0-8635a0812ad2-grafik.png

            Cheers,
            Matthias

            1 Reply Last reply Reply Quote 0
            • olivierlambert
              olivierlambert Vates ๐Ÿช Co-Founder๐Ÿฆธ CEO ๐Ÿง‘โ€๐Ÿ’ผ last edited by

              Thanks for your feedback @LeMatz

              @BenjiReis will take a look.

              1. For the short notation, I think that was simply not taken into account.
              2. What about the repo? It should work out of the box (our repo are IPv6 compatible)
              3. XCP-ng Center is not maintained by us, so we won't solve this anyway. For XO, it should work out of the box. Your issue is with the XO deploy thing, we are aware of it ๐Ÿ™‚
              1 Reply Last reply Reply Quote 0
              • LeMatz
                LeMatz last edited by

                Hey @olivierlambert,

                sure thing, thanks.

                I edited the thing with the repo out of my post, I was just a bit too blind.

                Is there any way on the XCP-ng host to test the DNS resolution? "dig" is not available there. Our host is somehow not able to resolve to mirrors.xcp-ng.org.
                Our chosen DNS server is very well able to resolve your mirror.

                I know that XCP-ng Center is not maintained by your team, but it's currently the only GUI that works for us :).

                Is there a different way to deploy XO instead of the quick install? I'm not sure, if the build from source is worth the effort.

                Thanks again,
                Matthias

                1 Reply Last reply Reply Quote 0
                • H
                  hoerup @LeMatz last edited by

                  @lematz
                  In the first picture of "hostname and dns configuration":
                  It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

                  LeMatz 1 Reply Last reply Reply Quote 1
                  • LeMatz
                    LeMatz @hoerup last edited by

                    @hoerup Jeeez, you are right, thanks a lot.
                    I'm feeling bad now ๐Ÿ˜ง

                    Reminder: do not work past 9 p.m. :D.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambert
                      olivierlambert Vates ๐Ÿช Co-Founder๐Ÿฆธ CEO ๐Ÿง‘โ€๐Ÿ’ผ last edited by

                      haha good catch, so it might support short format ipv6 ๐Ÿ™‚ Can you double check?

                      LeMatz 1 Reply Last reply Reply Quote 0
                      • LeMatz
                        LeMatz @olivierlambert last edited by LeMatz

                        @olivierlambert Well, I'd like to. But the console is giving me a hard time.

                        Our given DNS servers were not recognized:

                        77397c74-347a-4b0e-b03f-aefba0bc04a9-grafik.png

                        I'm not able to change the entries. Hitting "Enter" does not do anything. For all the other entries works "Enter" perfectly.

                        Olivier recommended in https://xcp-ng.org/forum/topic/5412/installation-of-xo-with-just-one-ip/2?_=1642003322780 to use one IPv6 for dom0 and bind the IPv4 to a VM like pfSense. Thanks to MAC-address binding of our provider, that made everything worse. Of cause we can't have the same MAC-address on more than one NIC.

                        I think this IPv6 experiment ends here for us.

                        Thanks for all the answers and help!
                        Matz

                        1 Reply Last reply Reply Quote 0
                        • olivierlambert
                          olivierlambert Vates ๐Ÿช Co-Founder๐Ÿฆธ CEO ๐Ÿง‘โ€๐Ÿ’ผ last edited by

                          Sadly @BenjiReis is really busy ATM working on our next 8.2.1 release ๐Ÿ˜ž But he'll come back here as soon he can!

                          1 Reply Last reply Reply Quote 0
                          • LeMatz
                            LeMatz last edited by

                            It's okay, releases are important ๐Ÿ™‚

                            1 Reply Last reply Reply Quote 0
                            • D
                              Dennis 0 last edited by

                              Short format works fine ๐Ÿ™‚

                              IPv6-only server still running for almost a year now without problems.

                              Not using it for anything mission critical as of yet, as installing updates is a bit "exciting" trying to combine main repo with the experimental ipv6-repo (avoid overwriting ipv6-patched packages on update) but still getting CVE's fixed from kernel etc. Haven't broken anything yet (AFAIK) - just looking forward to see this in a release.

                              (+ There might be a few useful details hiding here: https://github.com/xcp-ng/xcp/issues/437 in case)

                              DennisGlindhart created this issue in xcp-ng/xcp

                              closed IPv6 support on host #437

                              1 Reply Last reply Reply Quote 3
                              • BenjiReis
                                BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ last edited by

                                Hi all! Long time no see ^^

                                I'm glad to say i'm back on IPv6 and will (soon-ish) provide a new IPv6 iso to test XCP-ng with an IPv6 management interface.
                                I've made some fixes to DNS management.

                                Before the new ISO i'd like to support ideally DHCPv6 and autoconf.
                                For now I managed to :

                                • sometimes have an IP with DHCPv6 and sometimes a DNS - no gateway but it's exepected with stateless DHCPv6.
                                • Have an IP with Autoconf - No Gateway & no DNS

                                I'm looking for help as my field of expertise is more ocaml dev than IPv6.
                                I'm thinking especially of @AtaxyaNetwork and @bnerickson that I know have more knowledge than me for IPv6. ๐Ÿ™‚ Any help from a forum users would be greatly appreciated.

                                For DHCPv6 this is the conf of dhclient:

                                interface "xenbr0" {
                                  send fqdn.fqdn = gethostname();
                                  request subnet-mask, broadcast-address, time-offset, host-name, interface-mtu, dhcp6.nis-servers, dhcp6.nisp-servers, nis-domain-name, nisp-domain-name, dhcp6.sntp-servers, dhcp6.fqdn, routers, dhcp6.domain-search, dhcp6.name-servers;
                                }
                                

                                For Autoconf here's what's done:

                                /sbin/sysctl -q -w net.ipv6.conf.xenbr0.autoconf=1
                                /sbin/sysctl -q -w net.ipv6.conf.xenbr0.accept_ra=1
                                

                                Am I missing something obvious? I can provide more info if requested. ๐Ÿ™‚
                                Also I can made available a test iso before the real one but it'd be really a experimental ISO.

                                Thanks!

                                1 Reply Last reply Reply Quote 1
                                • BenjiReis
                                  BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ @AtaxyaNetwork last edited by

                                  @AtaxyaNetwork also, i tried to reproduce you XOA deploy issue buf failed, did you add [] around the IPv6 of your XCP-ng when filling up the deploy form?

                                  Thanks.

                                  AtaxyaNetwork 1 Reply Last reply Reply Quote 0
                                  • AtaxyaNetwork
                                    AtaxyaNetwork Ambassador ๐Ÿ“ฃ @BenjiReis last edited by

                                    @BenjiReis Hello !
                                    I don't remember exactly, but I will try to retest all in the incoming days ๐Ÿ™‚

                                    BenjiReis 1 Reply Last reply Reply Quote 0
                                    • BenjiReis
                                      BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ @AtaxyaNetwork last edited by

                                      @AtaxyaNetwork there are some issues, but on XOA's side.
                                      For now the deploy script specifically wait for an IPv4 to complete succesfully so it won't even though the XOA VM is up and running.
                                      For some reason it seems the XO app is not reachable with the IPv6 address in a web browser. I'm still investigating that.

                                      AtaxyaNetwork 1 Reply Last reply Reply Quote 0
                                      • AtaxyaNetwork
                                        AtaxyaNetwork Ambassador ๐Ÿ“ฃ @BenjiReis last edited by

                                        @BenjiReis Ok !
                                        Don't hesitate to ping me if you need help to debug the XOA side ๐Ÿ™‚

                                        BenjiReis 1 Reply Last reply Reply Quote 1
                                        • BenjiReis
                                          BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ @AtaxyaNetwork last edited by

                                          @AtaxyaNetwork so infact the issue was with our IPv6 lab config (lol) so XOA is reachable in fact with an IPv6 address ahah.
                                          So you can play with it.

                                          Now i'm back on my DHCPv6/Autoconf/SLAAC investigations ๐Ÿ™‚

                                          BenjiReis 1 Reply Last reply Reply Quote 0
                                          • BenjiReis
                                            BenjiReis Vates ๐Ÿช XCP-ng Team ๐Ÿš€ @BenjiReis last edited by BenjiReis

                                            Hi all!

                                            8.2.1 IPv6 ISO available!

                                            Here's a new ISO for IPv6 based on XCP-ng 8.2.1!
                                            The ISO can be used to upgrade an existing server installed with the previous IPv6 test ISO or install a brand new XCP-ng 8.2.1 with IPv6 support on management interface.

                                            A non-IPv6 8.2.0 would remain non-IPv6 after an upgrade as it's not possible to edit the management interface's primary adress type.

                                            An 8.2.0 IPv6 hosts can also be upgraded via yum: yum upgrade --enablerepo=xcp-ng-updates,xcp-ng-ipv6.

                                            What's new

                                            • All 8.2.1 fixes
                                            • Better DNS management in the case of both IPv4 and IPv6 configured on a PIF
                                            • Partial support of IPv6 DHCP and autoconf

                                            What to test

                                            • Your daily uses of XCP-ng but with IPv6
                                            • DHCP and autoconf (I have reached the limits of my knowledge so help from the community with more IPv6 expertise would be very VERY VERY helpful! :D)
                                              The goal of this ISO release is mainly to get help and leads about what's missing in DHCP and Autoconf.

                                            Any issue encountered (and what works fine also) can be reported in this thread.

                                            Usual warning

                                            This a test ISO with an experimental feature still in development.
                                            IPv6 on management interface is not officially supported by XCP-ng yet and so, we do not recommend to use it for a production environment.

                                            Thanks a lot for the help and I hope the ISO will work well for everyone.

                                            AtaxyaNetwork 1 Reply Last reply Reply Quote 2
                                            • First post
                                              Last post