Posts by Gummibaer9710

    I installed default installation of armbian image with 4.9er kernel and installing omv 5.0 with armbian softy tool. Then I installed docker via omv webpage. On default the new iptables nft is used which breaks using "docker network create ..." because it seems iptable nft is still not supported using docker.


    After changing iptables usage it worked:


    Switching to the legacy version:


    # update-alternatives --set iptables /usr/sbin/iptables-legacy

    # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

    # update-alternatives --set arptables /usr/sbin/arptables-legacy

    # update-alternatives --set ebtables /usr/sbin/ebtables-legacy


    Would be nice if the omv installation skript would be do these things automatically to avoid searching why "docker network create" is not working with strange error messages.

    I found the reason on asking in omv bugtracker and it was the new default usage of iptable nft usage. After switching back to legacy it worked as nft seems not to be supported until now:


    Switching to the legacy version:


    # update-alternatives --set iptables /usr/sbin/iptables-legacy

    # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

    # update-alternatives --set arptables /usr/sbin/arptables-legacy

    # update-alternatives --set ebtables /usr/sbin/ebtables-legacy

    Hi there, I have just do a fresh install of armbian (Armbian_20.02.5_Odroidn2_buster_legacy_4.9.216) on odroid n2 and installed omv 5 via armbian softy tool.


    Docker was installed via omv gui - omv extras - docker / portainer. When I now try to setup a separate network in docker / bridged mode I get the following error:


    docker network create --driver=bridge --subnet=192.168.151.0/24 --gateway=192.168.151.1 home

    Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-7a5194cdef64 -j DOCKER: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain FORWARD

    (exit status 4)


    Searching google doesn't find a possible solution. Anyone here that have a hint for this?

    The Master: vielleicht kurz auf deutsch :-) ich kann nur über ip v6 vom internet aus auf omv zugreifen, andere chance habe ich nicht. der raspi mit omv steht nicht bei mir zu hause, sondern bei jemand anders und dort möchte ich nicht immer einen pc zu administration nutzen, sondern direkt die oberfläche von omv bzw. ssh.


    Wenn offiziell im nginx ip v6 konfiguriert wird, damit es nach einer änderung nicht wieder gelöscht wird, ist das schon ein anfang. und es könnte mit ip v6 getestet werden. komisch, alle bei "Deutsche Glasfaser" kommen remote nur per ipv6 auf ihre heimgeräte. oder komplizierter über zusatzdienste.


    von daher, irgendwer muss ja anfangen mit ip v6 :-)

    Here is the setup:


    - OMV is used for private at a remote location (internet access via "Deutsche Glasfaser in Germany")
    - there is a avm fritzbox behind a isp router (bridged mode) so that the avm fritzbox gets a ip v6 network for using, but no ip v4 anymore (internal 100.xxx adress), so IP v4 NAT will not work with the isp router and the fritz box behind it (dual stack lite)
    - so I can only access the OVM homepage for configuring via IP v6 from remote
    - for FTP/SFTP and ssh this is no problem, they are configured for using ip v6 and this is working well
    - only the webpage (nginx) is not configured for ip v6


    - I see at the moment that there is a running "rc.local" process which seems to have a problem (permament cpu usage after disabling ip v4)
    - another problem is the "lets encrypt" modul, because it is only working if there is no ip v4 address (it is using ip v4 first and the testconnection then fails)
    - maybe other services are also not running properly

    Hello out there, I am using OMV 3.0.80 originally installed from the rasperry pi image and then upgraded to the latest version. My provider network is IP v6 only so I have to use it for all OMV services. I disabled for now IP v4 within the network config and looked after the nginx config.


    Still now the nginx config for OMV is not configured for IP v6 support so I enabled it with


    listen [::]:80;
    listen [::]:443 ssl deferred;


    and removed "listen 80;" and "listen 443 ...".


    It is not working very well when I access the OMV webpage after logging in. The log in process hangs somewhere around, after reloading it comes up. But not all homepage areas seems to be working only with IP v6. The update function gots errors and some more pages comes with unknown errors.


    Is OMV 3.0.80 really working within an IP v6 network without IP v4 support? And why is the nginx not configured for IP v6?


    If I enable IP v4 again the config process will override my IP v6 settings.