Posts by Juergen07

  • OMV6 as Access Point

    I have seen that there outputs from dhcpcd: there is a SIGTERM every 90 seconds?!

    Sep 03 14:17:28 [1744]: received SIGTERM, stopping

    Sep 03 14:17:28 [1744]: wlan0: removing interface

    Sep 03 14:17:28 [1744]: dhcpcd exited

    Sep 03 14:17:29 [1841]: dev: loaded udev

    Sep 03 14:17:29 [1841]: wlan0: connected to Access Point `'

    Sep 03 14:17:29 [1841]: DUID 00:01:00:01:29:dd:9b:ce:dc:a6:32:37:35:27

    Sep 03 14:17:29 [1841]: wlan0: IAID 32:f7:3a:fb

    Sep 03 14:17:29 [1841]: wlan0: using static address 192.168.4.1/24

    Sep 03 14:17:29 [1841]: wlan0: adding route to 192.168.4.0/24

    Sep 03 14:17:29 [1841]: wlan0: soliciting an IPv6 router

    Sep 03 14:17:41 [1841]: wlan0: no IPv6 Routers available

  • OMV6 as Access Point

    Quote from Soma

    Try again the installation but bypass the network configuration.

    https://github.com/OpenMediaVa…ipt#to-skip-network-setup

    Hello Soma,


    I have installed wifi AP on a new headless respbian (bullseye) according: https://www.raspberrypi.com/do…ted-wireless-access-point

    The AP worked fine. After installation of OMV6 with skipped network installation the AP is not working properly anymore.

    All the configuration look fine but I had to re-enable hostapd service again. The wifi network is visible and gets an ipv4 address but I am not able to connect to the AP using a mobile device: I do not get a IP address.
    It seems that dhcpcd does not get requests for wifi (eth0 is working well). This is the only message in the log for wifi:
    ... wlan0: no IPv6 Routers available


    tcpdump -i wlan0:

    13:12:15.929866 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 9 group record(s), length 188

    13:12:15.970226 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 306

    13:12:16.781708 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68

    13:12:16.906391 IP6 :: > ff02::1:ff2f:910d: ICMP6, neighbor solicitation, who has xxxx::xxxx:xxxx:xxxx:xxxx, length 32

    13:12:16.969934 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 306

    13:12:17.675545 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88

    13:12:17.677017 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ip6-allrouters: ICMP6, router solicitation, length 16

    13:12:17.681417 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28

    13:12:18.429667 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28

    13:12:18.667104 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88

    13:12:19.001797 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 306

    13:12:20.983154 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 302

    13:12:22.146385 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 302

    13:12:22.146987 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ip6-allrouters: ICMP6, router solicitation, length 16

    13:12:23.961097 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 302

    13:12:27.585999 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from xx:xx:xx:xx:xx:xx (oui Unknown), length 300

    13:12:31.039341 IP6 xxxx::xxxx:xxxx:xxxx:xxxx > ip6-allrouters: ICMP6, router solicitation, length 16


    ifconfig:

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.4.1 netmask 255.255.255.0 broadcast 192.168.4.255

    inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link>

    ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)

    RX packets 111 bytes 20456 (19.9 KiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 38 bytes 4512 (4.4 KiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    Do you have an idea?


    Best regards

    Juergen

  • USB HDD drive unmounts after connecting another USB mass storage

    I use a USB HDD as NAS drive on my pi4 with OMV5 (installed ~4 month ago). The device is mounted correctly after reboot.

    The NAS HDD will be unmounted during runtime when I connect another USB HDD for backups (hot plug-in, both HDDs have additional power supplies).

    There is a change from sda1 to sdb1 or sdc1.

    The NAS HDD will only be mounted automatically when it appears as sda1 even the label DATA is used in fstab (OMV5 entry).

    /dev/disk/by-label/DATA /srv/dev-disk-by-label-DATA ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2


    What could be the issue that a mounted device will be unmounted by adding another USB mass storage device?

    Is this linux behaviour (I have not observed this on other linux systems yet)?


    Docker is mapped to NAS HDD, too, that means that there exists open files during unmount!?


    I use OMV 5.4.7-1 with Kernel 4.19.97 (OMV default).


    BTW: I am able to mount the device with OMV5 UI (e.g. sdb1) -> configuration change. Using apply the drive will only be mounted when it appears with the same name, e.g. sdb1. This is not the case after reboot without the backup HDD. Nevertheless the ACL UI will not work and show error messages that sda1 is not available.