How do I enable IPv6 support on OMV 6? Maybe this is a dumb question but I haven't found a straight forward answer neither in the documentation nor in the forum.
How to enable IPv6 support on OMV6?
-
- OMV 6.x
- backslash
-
Network -> Interfaces -> select the interface then on the menu click edit (pencil icon)
-
Network -> Interfaces -> select the interface then on the menu click edit (pencil icon)
From my understanding this only enables/toggles IPv6 for a given network interface but not IPv6 support in general though I could be completely wrong.
-
From my understanding this only enables/toggles IPv6 for a given network interface
AFAIK that's the only way to do it, on a per interface
-
ipv6 is enabled by default at the OS level. Some services managed by OMV will disable ipv6 support if ipv6 is not detected. If your network interface has an ipv6 address, it should just work. I used it for a long time until my ISP dropped support.
-
Is this looking correct if my router is acting as a DHCP server?
-
Yep
-
I'm running into a similar issue. I cannot enable IPv6. When I attempt to switch and apply, I get the following error message and I am forced to undo the action. IPV6 is supported by my ISP. Maybe I'm missing something super obvious.
Code
Alles anzeigenFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color hosts 2>&1' with exit code '1': debian: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context [CRITICAL] Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color hosts 2>&1' with exit code '1': debian: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context [CRITICAL] Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context in /usr/share/php/openmediavault/system/process.inc:220 Stack trace: #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute() #1 /usr/share/openmediavault/engined/rpc/config.inc(174): OMV\Engine\Module\ServiceAbstract->deploy() #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusnh...', '/tmp/bgoutputhY...') #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #7 /usr/share/openmediavault/engined/rpc/config.inc(195): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array) #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array) #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array) #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1) #12 {main} -
ryecoaaron The omv.deploy.hosts.20domains Salt state is not part of OMV core or any core plugin. Is this file installed by an omv-extra.org plugin?
-
Is this file installed by an omv-extra.org plugin?
Nope.
-
-
I would like to see what 20domains looks like if it exists.
-
I don't know at all what 20domains is. My main issue is that I was getting IPV6 related connection issues. The OMV network page showing IPV6 disabled turned out to be a bit of a red herring. It turns out that I failed to create an AAAA IPV6 entry in my host record for my domains pointing to my local server. I created the records last night for all domains and it tested perfect this morning.
However, attempting to enable IPV6 in the OMV gui still results in the error. My server is working with IPV6 now. Guess I'll ignore the error.
¯\_(ツ)_/¯ -
I don't know at all what 20domains is.
What is the output of:
ls -al /srv/salt/omv/deploy/hosts/cat /srv/salt/omv/deploy/hosts/20domains.sls
-
Interesting. I investigated the entry in this file and noted that it is trying to append some custom hosts in a second hosts file in /etc. The /etc/hosts2 file exists but is empty. I removed the 20domains.sls file and tried once more to enable DHCP for IPV6 in the OMV dashboard. This time it succeeded! Though I wonder where this came from.
The contents of the 20domains.sls file:
Code{% set hosts = salt['cmd.shell']('cat /etc/hosts2') %} append_custom_hosts: file.append: - name: "/etc/hosts" - text: "{{ hosts }}"Output of ls -al /srv/salt/omv/deploy/hosts/
Coderoot@microverse:/srv/salt/omv/deploy/hosts# ls -al /srv/salt/omv/deploy/hosts/ total 24K drwxr-xr-x 2 root root 4.0K May 25 09:47 . drwxr-xr-x 46 root root 4.0K May 18 11:29 .. -rw-r--r-- 1 root root 3.2K Apr 25 12:03 10default.sls -rw-r--r-- 1 root root 133 Apr 21 22:10 20domains.sls -rw-r--r-- 1 root root 1.1K Feb 24 05:54 default.sls -rw-r--r-- 1 root root 909 Feb 24 05:54 init.sls -rw-r--r-- 1 root root 1.1K Feb 24 05:54 default.sls -rw-r--r-- 1 root root 909 Feb 24 05:54 init.sls -
This jogged my memory. A long while back I recall learning and dealing with some issues pertaining to the inability to edit /etc/hosts in OMV as it is controlled by OMV. I ran across this blog where a user claimed to have crafted a workaround. Apparently it didn't work or no longer works or something. I was a little careless on this and didn't document what I did for future me to know what the heck past me did.
-
That explains more. I would delete that file.
-
-
You know my opinion about adding any input fields to give users any tuning options. Those are only added if they make sense for all users, they fit into the OMV concept and do not complicate the administration & configuration experience.
With openmediavault 6.4.0 i hope that many networking issues will be fixed because some things were misconfigured in older versions. With the fixes done in 6.4.0 systemd-resolved is correctly used. -
For reference, here's what my system shows (IPv6 enabled and working)
Bashroot@nas:~# ls -al /srv/salt/omv/deploy/hosts/ total 20 drwxr-xr-x 2 root root 4096 May 21 11:47 . drwxr-xr-x 48 root root 4096 May 21 11:47 .. -rw-r--r-- 1 root root 3231 Apr 25 19:03 10default.sls -rw-r--r-- 1 root root 1085 Feb 24 12:54 default.sls -rw-r--r-- 1 root root 909 Feb 24 12:54 init.sls root@nas:~# cat /srv/salt/omv/deploy/hosts/20domains.sls cat: /srv/salt/omv/deploy/hosts/20domains.sls: No such file or directory root@nas:~#With openmediavault 6.4.0 i hope that many networking issues will be fixed because some things were misconfigured in older versions.
These improvements are always appreciated, thanks!
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!