Best way to get OMV and pi-hole to play nice?

Skyhi · Sep 12th 2023

I'm still at it trying to configure my pi, with OMV installed on it (for my NAS) to play nice with pi-hole running on a docker container. I read that they don't like each other because of port 80 (any other issues?). Sometimes the more I read my old brain gets more confused. Some say the best way is to change the port that OMV uses using omv-firstaid (is that the best way or can it be done in the GUI?). Others say to use macvlan and then run the pi-hole on that network created in docker. Is any method better then the other or do they both work essentially the same.?

Any other things I should be wary about?

I am really trying to be careful this time, as last time I tried this I broke everything for 2 weeks, before I could figure out how to fix things. I might be slow, but I am slowly learning.

claydoh · Sep 12th 2023

You can change OMV's port(s) via the GUI: System >>> Workbench

I have no idea if it is mandatory to use a macvlan, but that's what I did for it to work on my NAS, using OMV's Compose plugin, after I changed the Dashboard's ports.

drakula · Sep 12th 2023

suggest to:

1. not change any OMV ports and leave them default, because OMV is the NAS and controls the Docker containers via compose

2. change only the pi-hole ports in Docker compose that are overlapping with OMV or other containers

example based on https://hub.docker.com/r/pihole/pihole:

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
      - "81:80/tcp" # to access pi-hole via <IP-address>:81, and avoid conflicts with OMV GUI at port 80

Display More

in this example due to line 12 port setting you should be able to access in a browser:

OMV via <IP-address>:80
ip-hole via <ip-address>:81

raulfg3 · Sep 12th 2023

in host mode yo can have problem with ports ( 80, 53 etc..), so easy way is to use macVlan. That is like if you install it on a separate machine with his own IP.

you cant test both ways and decide what is the best for your trequeriments.

You have a guide on my signature

chente · Sep 12th 2023

Quote from Skyhi

I'm still at it trying to configure my pi, with OMV installed on it (for my NAS) to play nice with pi-hole running on a docker container. I read that they don't like each other because of port 80 (any other issues?). Sometimes the more I read my old brain gets more confused. Some say the best way is to change the port that OMV uses using omv-firstaid (is that the best way or can it be done in the GUI?). Others say to use macvlan and then run the pi-hole on that network created in docker. Is any method better then the other or do they both work essentially the same.?

There are two different port conflicts with pihole and OMV. They both need port 80 and port 53.

Port 80. It would be easy to change this port on either OMV or pihole, but this problem solves itself and is no longer relevant after solving the port 53 problem. So you can forget about it.

Port 53. You cannot change this port on either. The only way to resolve the port 53 conflict is to change the pihole container's IP to something different from the one OMV uses. In this way, the container's IP will have all free ports, including port 80 and port 53. To do this you must use a vlan, you can follow this procedure. https://wiki.omv-extras.org/do…_the_same_lan_as_the_host

Skyhi · Sep 12th 2023

Thanks for all the information!

I am running through the instructions on the omv-extras, and noticed i have to figure out my default gateway, and my ip range.

I have figured out my default gateway, but i am not sure how exactly I find out my ip range number. What is the best way to find it, to know for certain? (I just don't want to make another mistake to set me back days again)

chente · Sep 12th 2023

Quote from Skyhi

I have figured out my default gateway, but i am not sure how exactly I find out my ip range number. What is the best way to find it, to know for certain? (I just don't want to make another mistake to set me back days again)

The gateway is generally the IP of the router. What is it in your case?

Skyhi · Sep 12th 2023

I have figured out my gateway it is 192.168.0.1.

I don't however know what to put down for the subnet field ( the ip range)

p.s. I am using linux

chente · Sep 12th 2023

Quote from Skyhi

I have figured out my gateway it is 192.168.0.1.

In that case do this:

Subnet = 192.168.0.0/24

Gateway = 192.168.0.1

IP Range = 192.168.0.240/29

In the pi-hole container, configure any IP between 192.168.0.241 and 192.168.0.246 For example: 192.168.0.245 It would look like this:

Code

services:
  pi-hole:
    container_name: "pi-hole"
    .
    .
    networks:
      mynet:
        ipv4_address: 192.168.0.245
networks:
  mynet:
    external: true

Display More

Once the above is configured, it would be convenient to modify the DHCP network range on your router. Right now it is (surely, some routers restrict it more):

From 192.168.0.2

up to 192.168.0.254

Then you should configure it for example to this:

From 192.168.0.2

up to 192.168.0.239

This way, when the router assigns an IP to any device on your network that requests it, it will never match the IP you gave to pi-hole. You will avoid possible conflicts.

Skyhi · Sep 12th 2023

Thanks for the information and taking time to help.

couple questions...

How exactly did you figure out the proper ip range? (going from my 192.198.0.1 to the output of 192.168.0.0/24) I only ask to learn, so I don't have to ask in the future.

Second with your examples you have them surrounded by and , What is the reason for that? Is that just something that happens when you quote or copy? (ie no meaning to them?)

Thanks once again.

chente · Sep 12th 2023

Quote from Skyhi

How exactly did you figure out the proper ip range? (going from my 192.198.0.1 to the output of 192.168.0.0/24) I only ask to learn, so I don't have to ask in the future.

The full IP range is from 0 to 254 for each of the four octets. In total there are 255 values per octet. You will see the network range defined many times in this way 255.255.255.0 That means that the last octet is undefined (it is zero) therefore it can take any value between 0 and 254. Defining /24 is the same as 255.255.255.0 is say 255 possible values. You can play on this website and you will understand it better. https://jodies.de/ipcalc

Quote from Skyhi

Second with your examples you have them surrounded by and , What is the reason for that? Is that just something that happens when you quote or copy? (ie no meaning to them?)

mmm I think that's because I copied and pasted from the wiki and strange characters appeared in the first post... It's already corrected. Or do you mean something else?

Skyhi · Sep 12th 2023

No, that is good.

Thank you so much for helping! (and explaining)

Hopefully today I can finally get pi-hole up and running. (and slowly teaching this old dog new tricks) lol

chente · Sep 12th 2023

Quote from Skyhi

Thank you so much for helping! (and explaining)

You are welcome.

chente · Sep 12th 2023

By the way, this is all for the IPv4 protocol. The IPv6 protocol is another parallel world that may one day arrive (hopefully)

Skyhi · Sep 12th 2023

Hey Chente, can I ask one more question for knowledge sake?

Lets say I needed more ip's in my range? So I refer from using /29 that I get 5 ip's? (192.168.0.241 to 192.168.0.246) is that correct?

(also for learning sake: I saw a graph that says /29 gives 8 ip's, yet above your example only shows 5. Am I reading something wrong?)

So lets say I wanted (needed) more, and if I read it right, that as the "/#" goes lower then the amount of ip's go up by double, correct?

So say I wanted /28 or even /27? How would that change how I block off things in the router?

Am I to infer that say /28 gives me double the ip's as 29, so if it now goes from 5 ip's to 10 would I modify the DHCP range so instead of :

From 192.168.0.2

up to 192.168.0.239

It was double I would do:

192.168.0.2

192.168.0.234 (254-10)

Am I understanding this correctly?

Also would there be a advantage of moving my docker and all containers to a macvlan network different then OMV or would best practice be to just move on a need to basis for conflicts?

chente · Sep 12th 2023

If you need more IPs for other containers, you can expand the number available by varying the range. Calculators will help you with that.

When I wrote that procedure I set that range small thinking that someone might need some additional IP for another container or two. But this is not usual.

I also brought it closer to 254 as much as I could so as not to interfere too much with DHCP on the router.

You can customize all of this as you see fit.

Just think one thing. Using a vlan for a container has a disadvantage. All ports in that container are open on your network. This is not a problem if you know it. But you lose docker's advantage of controlling those ports as you wish.

So, if you need a vlan for a container, then do it. But if there is no reason there is no point in doing all this.

Skyhi · Sep 13th 2023

My apologies, I have another question before deploying pihole as a container (got busy yesterday). Reading through the OMV instructions after the configuration section for setting up a macvlan network it speaks to section on how to configure if I want a macvlan container(s) to be able to talk to the host.

Does pihole need or require this? should I set that up as well?

pros/cons?

chente · Sep 13th 2023

Quote from Skyhi

Does pihole need or require this? should I set that up as well?

Pihole doesn't need this. If you are faithful to the KISS principle, don't do it.

fbeye · Sep 13th 2023

I simply created a KVM VM and installed PiHole on it and use it... 192.168.5.0 is Network, 192.168.5.1 is GW and 192.168.5.119 is PiHole and using 192.168.5.1 redirects me to 192.168.5.119.

Badda Bing, Badda Boom.

Skyhi · Sep 15th 2023

Sadly, I failed again, not sure what I did wrong...

I created a macvlan network and called it "my-macvlan" . The output of that docker network inspect i as follows:

[ { "Name": "my-macvlan", "Id": "1fd9109c6e48ff4ab5e804c83b827b999bb3a2a67046d27860da890a8152eaa7", "Created": "2023-09-13T17:04:09.362587608-04:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.0.0/24", "IPRange": "192.168.0.240/29", "Gateway": "192.168.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "eth0" }, "Labels": {} }
]

END OF LINE

█

I then worked on a docker compose with my information found out a few messages above. (wasn't sure if I was supposed to allow pihole to be my dhcp server so i #'ed it out.)

version: "3"

# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/

services:

pihole:

hostname: pihole

networks:

my-macvlan: # name of the macvlan network you created

ipv4_address: 192.168.0.245 # the ip address you set in DHCP

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"

environment:

TZ: 'America/Toronto'

WEBPASSWORD: 'Freedom52' # set a secure password

# Volumes store your data between container upgrades

volumes:

- './etc-pihole:/etc/pihole'

- './etc-dnsmasq.d:/etc/dnsmasq.d'

# https://github.com/pi-hole/doc…hole#note-on-capabilities

# cap_add:

# - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed

restart: "unless-stopped"

networks:

my-macvlan:

driver: macvlan

driver_opts:

parent: eth0 # network interface

ipam:

config:

- subnet: 192.168.0.0/24 # subnet ip

- gateway: 192.168.0.1 # router gateway ip

- ip_range: 192.168.0.240/29 # ip range set in dhcp on router

I hit save and tried to start it and I got the following error.

Any idea what I did wrong?

Best way to get OMV and pi-hole to play nice?

Participate now!

Tags