NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

whistleillshoot's avatar
Aug 01, 2020

RAX200 - Using RasPi4 w/ PiHole

Afternoon,

 

I'm currently attempting to set up PiHole via RaspberryPi 4 with my RAX200 router, but I cannot seem to get it quite right.

 

I have disabled DHCP on the router in the LAN settings while adding a Static IP for the RasPi4 to the list, but it still seems as though no conected devices can retain connection after making these adjustments.

 

Do I need to adjust each device's static IP?

 

Am I missing an adjustment in the router's settings?

6 Replies

  • > I'm currently attempting to set up PiHole via RaspberryPi 4 [...]

     

       Running Raspbian?

     

    > [...] I cannot seem to get it quite right.

     

       Are you following some set of instructions or other?  Care to share?
    (A helpful link, perhaps?)

     

    > I have disabled DHCP on the router in the LAN settings while adding a
    > Static IP for the RasPi4 to the list, [...]

     

       Which "the LAN settings", exactly?  Which "the list"?

     

       Terminology: A "static" address is configured on the device itself.
    What you configure on a (DHCP server on a) router is a reserved dynamic
    address, not a static address.

     

       Are you saying that you reserved an address for the R-Pi in the
    router's DHCP server, and then disabled the router's DHCP server?
    What's wrong with this picture?

     

    > [...] but it still seems as though [...]


       "seems"?  Not a useful problem description.  It does not say what you
    did.  It does not say what happened when you did it.  As usual, showing
    actual actions (commands) with their actual results (error messages, LED
    indicators, ...) can be more helpful than vague descriptions or
    interpretations.

     

       I've never played with a Pi-hole, so I know nothing, but, on general
    principles, I'd assign a static IP address to any DHCP server.  Because,
    whom (else) is it supposed to ask for its own address, when it's
    supposed to be Mr. Know-it-all for LAN IP addresses?  (And that's an

    actual _static_ address, configured on the R-Pi itself.

    • whistleillshoot's avatar
      whistleillshoot
      Aspirant

      Running Raspbian?

       

         Yes, Raspberry Pi OS (Previously called Raspbian)

       

      Are you following some set of instructions or other?  Care to share?
      (A helpful link, perhaps?)

       

         I was trying to follow these instructions from PiHole, but it I'm having trouble locating DNSMasq.

       

      Which "the LAN settings", exactly?  Which "the list"?

       

         I have disabled "Use Router as DHCP Server" in the LAN settings of the router itself and added the "static" address I would like for the R-Pi to the "Address Reservation". This, however, did not make any of the devices connected to the network go through the R-Pi before sending info to the servers.

       

      Terminology: A "static" address is configured on the device itself.
      What you configure on a (DHCP server on a) router is a reserved dynamic
      address, not a static address.

       

         Understood.

       

      Are you saying that you reserved an address for the R-Pi in the
      router's DHCP server, and then disabled the router's DHCP server?
      What's wrong with this picture?

       

         I believe that is correct. Stupid move on my part, but I've having trouble fiding other options within the router itself.


      "seems"?  Not a useful problem description.  It does not say what you
      did.  It does not say what happened when you did it.  As usual, showing
      actual actions (commands) with their actual results (error messages, LED
      indicators, ...) can be more helpful than vague descriptions or
      interpretations.

       

         I have to laugh first, as you sound like Sheldon from The Big Bang Theory; very literal. I like literal. I don't mean that in a bad way, but I understand what you're saying. This is my first time trying anything of this nature.

       

      I disabled the "Use Router as DHCP Server" in the LAN settings of the router itself and added the "static" address I would like for the R-Pi to the "Address Reservation".

       

         I've never played with a Pi-hole, so I know nothing, but, on general
      principles, I'd assign a static IP address to any DHCP server.  Because,
      whom (else) is it supposed to ask for its own address, when it's
      supposed to be Mr. Know-it-all for LAN IP addresses?  (And that's an

      actual _static_ address, configured on the R-Pi itself.

      • antinode's avatar
        antinode
        Guru

        > I was trying to follow these instructions from PiHole, [...]

         

           Ok.  Your original problem description threw me off the track.  Sorry
        about the (my) confusion.  (_Your_ original confusion is still your
        fault, however.)  So, anything above which refers to the R-Pi as a DHCP
        server is wrong.

         

        > I have disabled DHCP on the router [...]

         

           Why?  Pi-hole is a _DNS_ server, not a _DHCP_ server.  There's no
        obvious reason to change anything in the router's DHCP configuration,
        except, perhaps, to add the Pi-hole system to the address reservations
        on the router's DHCP server (which should _not_ be disabled).

         

        > [...] I'm having trouble locating DNSMasq.

         

           I doubt that you'll find it on a router which is running typical
        Netgear firmware.  I'd look for the router's DNS settings at: BASIC >
        Internet : Domain Name Server (DNS) Address, where you ought be able to
        specify the (reserved, LAN) IP address of the Pi-hole system (R-Pi).


           Whether that will actually work is another queston, however.  There
        have been many recent reports of various models and/or firmware versions
        which reject a DNS server address which is on the router's LAN address
        subnet.

         

        > [...] This, however, did not make any of the devices connected to the
        > network go through the R-Pi before sending info to the servers.

         

           Again, "DHCP" and "DNS" are spelled differently for a reason.