Is it not time for full IPv6 support?

phillxnet · July 26, 2021, 8:16pm

@rudi Welcome to the Rockstor community.

Re addition of IPv6. We recently intentionally disabled this so that our Web-UI would reflect, and be able to configure, only what was enabled. If you fancy re-enabling and doing you own IPv6 config via nmcli for example all should be OK. But of course there is then a far wider disparity between the systems state and what our Web-UI is able to reflect/configure.

We disable simply via a grub administered kernel command line addition. See:

github.com

rockstor/rockstor-installer/blob/master/rockstor.kiwi#L77


      
                      <volume name="var" copy_on_write="false"/>
                  </systemdisk>
                  <oemconfig>
                      <oem-swap>true</oem-swap>
                      <oem-swapsize>2048</oem-swapsize>
                      <oem-device-filter>/dev/ram</oem-device-filter>
                      <oem-multipath-scan>false</oem-multipath-scan>
                      <oem-skip-verify>true</oem-skip-verify>
                  </oemconfig>
              </type>
          </preferences>
          <preferences profiles="Leap15.5.RaspberryPi4,Leap15.6.RaspberryPi4,Tumbleweed.RaspberryPi4">
              <version>5.0.15-0</version>
              <packagemanager>zypper</packagemanager>
              <locale>en_GB</locale>
              <keytable>gb</keytable>
              <timezone>Europe/London</timezone>
              <rpm-excludedocs>true</rpm-excludedocs>
              <rpm-check-signatures>false</rpm-check-signatures>
              <bootsplash-theme>upstream</bootsplash-theme>
              <bootloader-theme>starfield</bootloader-theme>

for the x86_64 profiles. You can build your own installer with this removed and should then have full IPv6 capabilities. Although you will be on your own for IPv6 configuration via the command line. Note also that we have slightly modified the postfix config to accomodate for no IPv6. See the following issue for what was done if you need to undo this for your purposes:

github.com/rockstor/rockstor-core

[openSUSE] fix postfix config re ipv4, tlsmgr, & CA file settings. Fixes #2132

rockstor:master ← phillxnet:2132_2133_openSUSE_fix_config_settings_for_postfix

opened 09:36PM - 19 Feb 20 UTC

phillxnet

+805 -553

Thanks to @tyukh for initial reporting and initial diagnosis of the root causes.… Due to differing defaults from our prior CentOS base, email notification configuration failed. Adjust configuration mechanism as below. Fixes #2132 Fixes #2133 Fixes #2035 # Includes: - Un-remark tlsmgr line in master.cf when on openSUSE. - Disable on-by-default mail sysconfig in openSUSE (see issue #2035) - Update /etc files postfix/master.cf & sysconfig/mail only if required. - Adapt Certificate Authority file bundle path to openSUSE contextually. - Enforce "inet_protocols = ipv4" in postfix if a prior 'all' setting is found. This avoids postfix service failure on ipv4 only systems. - Move to string.format in email_client.py. - Black format email_client.py. - Black format system/osi.py (large file) - in separate commit. - Fix buggy use of os.chmod. - Abstract "/root/.forward" for clarity. - Abstract "/etc/postfix/generic" for clarity. - Improve code comments. - Add comments to existing system/osi inplace_replace() function. - Add general purpose replace_line_if_found() facility to system/osi.py. - Establish simple system/osi replace_line_if_found() mechanism. - Avoid postfix log warnings by removing to-be duplicate config options. - Ensure postfix service is enabled after each config save. The vendor default is 'disabled'. Additional unrelated trivial fix without associated issue: - A trivial debug log var refactor omission relating to pr #2039 # Testing No new unit tests were written. However functional testing was performed on all three target dirtos of "rockstor" (CentOS), and our two openSUSE targets: Leap15.1, and Tumbleweed. From a clean source build, post postfix removal and install (fresh config files & to establish systemd vendor default status) the Rockstor Web-UI was able to successfully test email notification config entry, prior to submitting it, and successfully submit that config there after and subsequently perform the test email send. All associated config files were inspected pre and post automated editing and the resulting file access rights were confirmed to be as intended. All 3 platforms, post email notification configuration, were also confirmed to successfully forward self-sent root-directed email using the following procedure: ``` # cli mail client already installed on our CentOS variants zypper in mailx echo "Body text of email alert" | mail -s "Alert Email" root ``` @FroggyFlox Ready for review. I was unfortunately unable to separate the black formatting in the case of the smaller file edited in this pr, but the much larger system/osi.py file does have it's black formatting in a separate commit to ease review.

When we get a contribution to our network subsystems re the capability to configure, via the Web-UI, an IPv4/IPv6 system. See the networking docs section:

https://rockstor.com/docs/network.html

Also note that any changes will have to be accompanied by appropriate tests to prove the function of this rather critical component. All part of the difficulty of covering such a broad range of capabilities in a modern appliance. So in short contributions are welcome and we have the following doc section to help get folks started:

https://rockstor.com/docs/contribute_section.html

Note that we never used to disable IPv6 in our CentOS variant. And had few reports of issues. But in an effort to tighten our Web-UI capability to our underling capability we simply turned IPv6 off. Do please report your findings on turning this back on. And if you intend to make any changes for submission please keep in mind our rock-net capability. Not entirely sure this will be affected actually. That would be a question for @Flox when he is next available.

Thanks for your feedback and note that Rockstor is currently envisaged as being primarily deployed on a private network with only certain ports / services forwarded to the internet if need be.

Hope that helps, and thanks for the info re IPv6 update.