Beiträge von opennas

please
Debian GNU/Linux non viene fornita con ASSOLUTAMENTE ALCUNA GARANZIA, nella misura
consentita dalla legge applicabile.
Ultimo accesso: Fri Jan 26 10:57:16 2024 da 192.168.2.221
root@nas:~# sudo systemctl status smbd.service● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service
; enabled; vendor preset: enabled
) Active: attivo (in esecuzione) dal Fri 2024-01-26 11:09:52 CET; 1min 44s fa
Documenti: man:smbd(8) man:samba(7) man:smb.conf(5) Processo: 1037 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) PID principale: 1053 (smbd) Stato: "smbd: connessioni pronte per servire..."
Attività: 4 (limite: 9258)





Memoria: 105.4M
CGroup: /system.slice/smbd.service
├─1053 /usr/sbin/smbd --foreground -- no-process-group ├─1304 /usr/sbin/smbd --foreground --no-process-group ├─1305 /usr/sbin/smbd --foreground --no-process-group └─3231 /usr/sbin/smbd --foreground --no-process-group

Jan 26 11:09:46 nas systemd[1]: Avvio di Samba SMB Daemon ...
26 gen 11:09:52 nas systemd[1]: Avviato Samba SMB Daemon.
Jan 26 11:09:52 nas smbd[1053]: [2024/01/26 11:09:52.195555, 0] .. /.. /lib/util/become_daemon.c:135(daemon_ready)
Jan 26 11:09:52 nas smbd[1053]: daemon_ready: demone 'smbd' ha terminato l'avvio ed è pronto per servire le connessioni
root@nas:~# systemctl status smbd● smbd.service - Demone
SMB Samba Loaded: caricato (/lib/systemd/system/smbd.service
; abilitato; vendor preset: abilitato) Attivo: attivo (in esecuzione)
dal Fri 2024-01-26 11:09:52 CET; 2min 11s fa
Documenti: man:smbd(8) man:samba(7) man:smb.conf(5) Processo: 1037 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) PID principale: 1053 (smbd) Stato: "smbd: connessioni pronte per servire..."
Attività: 4 (limite: 9258)





Memoria: 105.4M
CGroup: /system.slice/smbd.service
├─1053 /usr/sbin/smbd --primo piano -- no-process-group ├─1304 /usr/sbin/smbd --foreground --no-process-group ├─1305 /usr/sbin/smbd --foreground --no-process-group └─3231 /usr/sbin/smbd --foreground --no-process-group

Jan 26 11:09:46 nas systemd[1]: Avvio di Samba SMB Daemon ...
26 gen 11:09:52 nas systemd[1]: Avviato Samba SMB Daemon.
Jan 26 11:09:52 nas smbd[1053]: [2024/01/26 11:09:52.195555, 0] .. /.. /lib/util/become_daemon.c:135(daemon_ready)
Jan 26 11:09:52 nas smbd[1053]: daemon_ready: demone 'smbd' ha terminato l'avvio ed è pronto per servire le connessioni
root@nas:~# systemctl status smbd● smbd.service - Demone
SMB Samba Loaded: caricato (/lib/systemd/system/smbd.service
; abilitato; vendor preset: abilitato) Attivo: attivo (in esecuzione)
dal Fri 2024-01-26 11:09:52 CET; 2min 19s fa
Documenti: man:smbd(8) man:samba(7) man:smb.conf(5) Processo: 1037 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) PID principale: 1053 (smbd) Stato: "smbd: connessioni pronte per servire..."
Attività: 4 (limite: 9258)





Memoria: 105.4M
CGroup: /system.slice/smbd.service
├─1053 /usr/sbin/smbd --primo piano -- no-process-group ├─1304 /usr/sbin/smbd --foreground --no-process-group ├─1305 /usr/sbin/smbd --foreground --no-process-group └─3231 /usr/sbin/smbd --foreground --no-process-group

Jan 26 11:09:46 nas systemd[1]: Avvio di Samba SMB Daemon ...
26 gen 11:09:52 nas systemd[1]: Avviato Samba SMB Daemon.
Jan 26 11:09:52 nas smbd[1053]: [2024/01/26 11:09:52.195555, 0] .. /.. /lib/util/become_daemon.c:135(daemon_ready)
Jan 26 11:09:52 nas smbd[1053]: daemon_ready: demone 'smbd' ha terminato l'avvio ed è pronto per servire le connessioni
root@nas:~# systemctl status nmbd.service● nmbd.service - Demone
Samba NMB Loaded: caricato (/lib/systemd/system/nmbd.service
; disabilitato; preset fornitore: abilitato) Attivo: inattivo (morto)
Documenti: man:nmbd(8) man:samba(7) man:smb.conf(5)

Segue

I don't understand why I have problems accessing my NAS folders on Windows 11. I attach photos of the smb status... can anyone help me??

Zitat von raulfg3

no, è necessario configurare il server DHCP per servire l'IP pihole come un server DNS.

PD: Non puoi avere 2 server dhcp, quindi devi decidere se usare il tuo router o pihole come server dhcp.

e ricorda che OMV non può avere PIHOLE IP come DNS perché è un servizio in OMV, quindi puoi usare 8.8.8.8 su OMV e PIHOLE IP su altre macchine.

Ok

Zitat von raulfg3

other fail:

volumes:

- /srv/dev-disk-by-label-DATA/config/pihole:/etc/pihole

- /srv/dev-disk-by-label-DATA/appdata/pihole/dnsmasq.d:/etc/dnsmasq.d

is not a real / good mount point.

you need to first create a shared folder on your DATA disk to store your dockers config and use it here.

use absolute path in global.env

a good documentation is here: https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv

Alles anzeigen

thank you very much now after your precious help everything works... now the only thing I want to do is that all the clients of the local network pass through pihole... do I have to set something on pihole??

Ecco il MacVLAN

Here you are

Zitat von raulfg3

post your pihole.yml file, only delete password

and post to see that you have created previosl¡y a macVLAN on webGUI named MyMacVlan , on this screenshot is not created: https://forum.openmediavault.o…t/34168-screenshot-2-png/

I took inspiration from yours and I'll also attach the macvlan

Zitat von raulfg3

si prega di creare prima il macvlan su compose webGUI e poi utilizzare il mio pihole.yml come riferimento

si chiama MyMacVlan nel mio esempio.

Impossibile eseguire il comando 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; esportazione LANG=C.UTF-8; esportazione LANGUAGE=; docker compose --file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml' --env-file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.env' --env-file '/srv/dev-disk-by-label-DATA/Docker/global.env' up -d 2>&1': parsing /srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml: yaml: riga 12: impossibile trovare ':' previsto

OMV\ExecException: Impossibile eseguire il comando 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; esportazione LANG=C.UTF-8; esportazione LANGUAGE=; docker compose --file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml' --env-file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.env' --env-file '/srv/dev-disk-by-label-DATA/Docker/global.env' up -d 2>&1': parsing /srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml: yaml: riga 12: impossibile trovare ':' previsto in /usr/share/openmediavault/engined/rpc/compose.inc:693
Traccia dello stack:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMVRpcServiceCompose->{closure}('/tmp/bgstatusAg...', '/tmp/bgoutputIF...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(696): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [funzione interna]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {principale}

Ciao a tutti, ho bisogno di aiuto, non riesco a installare Pihole sul mio OMV tramite Docker compose ... Sto chiedendo aiuto, per favore allega i miei errori..

Zitat von jml79

Ho provato a eseguire pihole senza un MacVLan o un bridge (in una VM) e non si legava alla porta 53, quindi non funzionava. Non ho esaminato il problema fino a fondo, ho solo eseguito un MacVLan con docker e un bridge con una VM. Lo svantaggio di un MacVLan è che la macchina che esegue il docker non può connettersi a pihole. C'è un modo per configurarlo in modo che possa collegarsi al foro MacVLan per DNS, l'ho configurato una volta ma da allora non l'ho più fatto. Se si esegue pihole in una macchina virtuale con un bridge (br0), l'host può usarlo. In realtà preferisco eseguirlo in una piccola VM, Debian 12 e installato direttamente (non in docker), lo trovo più resiliente alle disconnessioni di rete. La macchina virtuale si adatta a un'immagine da 3 GB e utilizza meno di 300 MB di RAM durante l'esecuzione senza quasi alcun impatto sull'utilizzo della CPU.

Ok

Zitat von mischka

Under Services/Compose/Network you create a macVLAN and map it in the compose file of pihole. Here's an example of a pihole yml using a macvlan network called "pinet".

Code

version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    # For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "80:80/tcp"
    hostname: pihole
    environment:
      TZ: 'Europe/Berlin'
      WEBPASSWORD: 'xxx' # Passwort fuer pihole Web-Interface
    # Volumes store your data between container upgrades
    volumes:
      - '/appdata/pihole/etc-pihole:/etc/pihole' # Ordner etc-pihole unter /appdata/pihole erstellen
      - '/appdata/pihole/etc-dnsmasq.d:/etc/dnsmasq.d' # Ordner etc-dnsmasq.d unter /appdata/pihole erstellen
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped
    networks:
      pinet:
        ipv4_address: 192.168.178.81 # lokale IP4 Adresse des macVLAN Network eintragen
networks:
  pinet: # hier Name des erstellten macVLAN eintragen Beispiel hier pinet
    external: true

Alles anzeigen

How to set up a vlan interface is described here (below): https://wiki.omv-extras.org/do…v6_plugins:docker_compose

thanks... I'll try it and see what happens

Zitat von mischka

I've given up using Pihole on Docker in OMV. Because of my solar system, I wanted to have internet available at all times. But the NAS doesn't. Due to power consumption, OMV should only be available when it is needed. Nobody needs that at night. In the summer, there are also many periods when no one accesses the NAS. I outsourced Pihole/Unbound to a Dell Wyse 3040, consuming about 24 Wh per day (about 9kWh per year). The consumption is more than sufficiently compensated by the autoshutdown of the OMV server or you save electricity. If you use a Pi Zero 2 instead of a Dell Wyse 3040, the power consumption is even lower. So I'm satisfied. Pihole does not affect the local network.

so it's fine... thanks... but do I have to create a virtual network in the compose file to avoid having problems?? also because I use qbittorent a lot and then I have a Wireguard VPN that I use with OMV

being on topic... I would also like to install pihole with docker compose... but I have doubts!!

1 I have a router inside my house that connects to a manager modem

2 I have services on my Nas Omv in my home network such as Qbitorrent Jellyfin etc...

3 I want all the devices connected to my local network to have no connection problems... on the contrary

4 I also have home assistants in my network who manage my home automation..

Could someone help me get pihole without making my life impossible on the internet?? sorry I'm inexperienced

Zitat von Soma

Inizia controllando il PERCORSO che mostra:

ls -al /var/run/fail2ban/

Code

pi@panela:~ $ ls -al /var/run/fail2ban/
total 4
drwxr-xr-x  2 root root   80 Dec  9 10:05 .
drwxr-xr-x 35 root root 1160 Dec 17 11:00 ..
-rw-------  1 root root    7 Dec  9 10:05 fail2ban.pid
srwx------  1 root root    0 Dec  9 10:05 fail2ban.sock

Se non mostra nulla:

Code

pi@panela:~ $ ls -al /var/run/
total 52
drwxr-xr-x 35 root     root     1160 Dec 17 11:00 .
drwxr-xr-x 20 root     root     4096 Sep 23 12:07 ..
drwxr-xr-x  3 root     root       60 Jun 18 15:55 NetworkManager
-rw-------  1 root     root        0 Nov 16 16:06 agetty.reload
drwxr-xr-x  2 avahi    avahi      80 Nov 16 16:06 avahi-daemon
drwxr-xr-x  2 root     root       80 Dec  9 09:06 blkid
-rw-r--r--  1 root     root        4 Nov 16 16:06 blkmapd.pid
drwxr-x---  2 _chrony  _chrony    80 Nov 16 16:06 chrony
drwxr-xr-x  2 root     root       80 Nov 16 16:06 console-setup
drwx--x--x  5 root     root      140 Dec 12 09:20 containerd
drwxr-xr-x  2 root     root       40 Jun 18 15:55 credentials
-rw-r--r--  1 root     root        5 Nov 16 16:06 crond.pid
----------  1 root     root        0 Nov 16 16:06 crond.reboot
drwxr-xr-x  2 root     root       60 Nov 16 16:06 dbus
prw-------  1 root     root        0 Jun 18 15:55 dmeventd-client
prw-------  1 root     root        0 Jun 18 15:55 dmeventd-server
drwx------  8 root     root      180 Nov 16 16:07 docker
-rw-r--r--  1 root     root        4 Nov 16 16:07 docker.pid
srw-rw----  1 root     docker      0 Nov 16 16:06 docker.sock
drwxr-xr-x  2 root     root       80 Dec  9 10:05 fail2ban
drwxr-xr-x  2 root     root       60 Nov 16 16:08 faillock
drwxr-xr-x  2 root     root       80 Nov 16 16:06 fsck
prw-------  1 root     root        0 Jun 18 15:55 initctl
drwx------  2 root     root       80 Jan  1  1970 initramfs
drwxrwxrwt  4 root     root      240 Nov 16 16:06 lock
drwxr-xr-x  3 root     root       60 Nov 16 16:06 log
drwx------  2 root     root       80 Nov 16 16:06 lvm
-rw-r--r--  1 root     root        5 Nov 16 16:06 monit.pid
srwxr-xr-x  1 root     root        0 Nov 16 16:08 monit.sock
-rw-r--r--  1 root     root       79 Dec 17 11:00 motd.dynamic
drwxr-xr-x  2 root     root       40 Jun 18 15:55 mount
drwxr-xr-x  2 root     root      100 Nov 16 16:06 network
-rw-r--r--  1 root     root        5 Nov 16 16:06 nginx.pid
drwxrwx---  2 root     nut       120 Nov 16 16:06 nut
-rw-r--r--  1 root     root        7 Dec 14 11:12 omv-engined.pid
drwxr-xr-x  2 www-data www-data  120 Nov 16 16:06 php
drwxr-xr-x  2 root     root       40 Nov 16 16:06 proftpd
-rw-r--r--  1 root     root        5 Nov 16 16:06 rngd.pid
-rw-r--r--  1 statd    nogroup     4 Nov 16 16:06 rpc.statd.pid
dr-xr-xr-x 11 root     root        0 Jun 18 15:55 rpc_pipefs
drwxr-xr-x  2 _rpc     root       40 Nov 16 16:06 rpcbind
-r--r--r--  1 root     root        0 Nov 16 16:06 rpcbind.lock
srw-rw-rw-  1 root     root        0 Jun 18 15:55 rpcbind.sock
drwxr-xr-x  2 root     root       40 Nov 16 16:06 samba
drwxrwxrwt  2 root     utmp       40 Nov 16 16:06 screen
drwxr-xr-x  2 root     root       40 Nov 16 16:06 sendsigs.omit.d
lrwxrwxrwx  1 root     root        8 Nov 16 16:06 shm -> /dev/shm
-rw-------  1 root     root        5 Nov 16 16:06 sm-notify.pid
drwxr-xr-x  2 root     root       40 Nov 16 16:06 sshd
-rw-r--r--  1 root     root        5 Nov 16 16:06 sshd.pid
drwx--x--x  3 root     root       60 Nov 16 16:06 sudo
drwxr-xr-x  2 root     root       60 Nov 16 16:06 sysconfig
drwxr-xr-x 22 root     root      540 Dec 14 11:11 systemd
srw-rw-rw-  1 root     root        0 Nov 16 16:06 thd.socket
drwxr-xr-x  2 root     root       60 Nov 16 16:06 tmpfiles.d
drwxr-xr-x  7 root     root      160 Dec 16 08:21 udev
drwxr-xr-x  3 root     root       60 Dec 17 11:00 user
-rw-rw-r--  1 root     utmp     2000 Dec 17 11:00 utmp

Alles anzeigen

Prova a disabilitare il servizio, disinstalla il plug-in, installa di nuovo.

Prima di abilitarlo, inizia abilitando prima le Jail, accettando lo Stendardo Giallo quando viene visualizzato.

Solo dopo aver abilitato le jail, abilitare il servizio nella pagina delle impostazioni.

Se si verifica un errore, pubblica informazioni, screenshot o le impostazioni che stai applicando.

Inoltre, gli output di:

sudo fail2ban-client -x start

sudo fail2ban-stato del client

sudo systemctl status fail2ban.service

Alles anzeigen

scusate per la mia ignoranza. Ma a cosa serve Fail2Ban?

Ok

Zitat von Soma

Elenchi di repository che non dovrebbero essere presenti.

C'è un modo per vedere se ci sono altri repository che non dovrebbero esserci??

Zitat von Soma

Problem solved

yes thank you very much... but what was the cause?