Posts by haschmi71

Sorry, then I also don't have an idea. Maybe this page has a solution: 10 Tech-Savvy Ways to Fix Network Error Code 0x80070035

Did you recently update your Windows 11 PC to 24H2? In case you're accessing your SMB shares in guest mode this won't work anymore with the default settings.
You have to start the group policy app with gpedit.msc and enable insecure guest logons via "Computer Configuration > Administrative Templates> Network > Lanman Workstation"

Maybe I can help with the experiences I made til I got this "beast" running:

Target: Using pihole and unbound each in a separate docker container to avoid any port conflict. Using macvlan

Start: Setting up MACVLAN

Go to "Services -> Compose -> Networks" and add a new network.

- Name: Choose unique name, like "myvlan"

- Driver: macvlan

- Parent network: Select adapter, where your vlan should be linked to

- Subnet: E.g. "192.168.1.0/24", your IP network

- Gateway: Usually your router, e.g. "192.168.1.1"

- IP range: You can reserve a certain amount of IP addresses to be used with docker. Very late I learned, that this is only optional. So if you manage your IP addresses outside DHCP on your own, just leave this blank to save a lot of trouble with potential misconfigurations

Save

Next: Setting up pihole

Go to "Services -> Compose -> Files" and add a new file

- Enter name and description

- Add this text to the file section and change all values to your network needs:

version: "3"

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole #Choose your hostname
    dns:
     - "192.168.1.X" #DNS1: Should be the address of your unbound system
     - "9.9.9.9"     #DNS2: Quad9 as an example, optional
    networks:
      myvlan:    #the network name you specified in the first step
        ipv4_address: 192.168.1.Y    #The IP address you want to assign to your pihole. Make sure this address is available to be used in your network
    # For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp"
    environment:
      TZ: 'Europe/London' #Choose your region
      WEBPASSWORD: 'secret' #Assign a password to login to your pihole
    # Volumes store your data between container upgrades
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped
networks:
  myvlan:  #the network name you specified in the first step
    external: true

Next: Setting up Unbound

Go to "Services -> Compose -> Files" and add a new file (I choose a separate file for Unbound to be more flexible, some guides put all in one file)

- Enter name and description

- Add this text to the file section and change all values to your network needs:

version: "3"

services:
  unbound:
    container_name: unbound
    image: mvance/unbound:latest
    hostname: unbound
    networks:
      myvlan: #the network name you specified in the first step
        ipv4_address: 192.168.1.X #The IP address you want to assign to Unbound. Make sure this address is available to be used in your network
    ports:
      - "53:53/tcp"
      - "53:53/udp"
    #volumes:    #It's important to comment out these two lines if you don't want to use your own unbound configuration! An own configuration can be tricky as you have to provide several config files manually.
    #  - './etc-unbound:/opt/unbound/etc/unbound'
    restart: unless-stopped
networks:
  myvlan:  #the network name you specified in the first step
    external: true

Final: Start both containers

In the Files section use the "Up" button to start both containers.

Oh, I see! So with a netmask of 29 you can reserve six IP adresses, but not exactly where you want to! You cannot have the range from .70 to .75, but either go from .65 to .70 or from .73 to .78. This system definitively was not invented for normal people!
Anyway, thanks a lot for your help!

I'm not very famliar with this macvlan and subnet topics. I just read in the omv-extras wiki:

"In the IP range field write 192.168.1.240/29 Adapt it to your network.

This network range is equivalent to the IP addresses between 192.168.1.241 to 192.168.1.246"

This should then also be wrong in the wiki, right?

Since todays update I'm facing a strange error message regarding compose - macvlan.
To run pihole and unbound on my OMV I'm using macvlan. I created a macvlan network in the compose plugin with the IP range 192.168.1.70/29 to have addresses available from 192.168.1.71 to 192.168.1.76. Pihole is assigned to .71 and unbound runs on .72. This setup was perfectly fine until todays update.
After the update the pihole container was OK, but unbound was stopped and didn't want to start anymore. So I decided to delete the macvlan network and set it up again with the same values. Unfortunately I received the error message "invalid ip-range 192.168.1.70/29: it should be 192.168.1.64/29".
Has anybody an idea where this could come from and what to do? In the omv-extras wiki there is no hint what could be wrong.