Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Replaced router, pi-hole no longer works

TrainFan475
 Share

Go to solution Solved by TrainFan475,

Update: I got it running, just had to run pihole -r to reconfigure the ip address

I just upgraded my router from a cisco linksys e1200 to a TP-link AC1750, but it made my pi-hole stop working. I can't get the raspberry pi to connect to the router via ethernet at all, and even on wifi I can't connect to it through the web interface. I don't remember how I set it up in the first place so I would have to learn it all over again.

Main Desktop - CPU: Ryzen 5 5600x  | GPU: GeForce GTX 1070 Founders Edition | RAM: G.SKILL TridentZ RGB 16GB (2 x 8GB) 3200MHz | Motherboard: Gigabyte B450 Aorus M | PSU: EVGA 650 B3 | STORAGE: Boot drive: Crucial MX500 1TB, Secondary drive: WD Blue 1TB hdd | CASE: Phanteks Eclipse P350x | OS: Windows 10 Pro | Keyboard: Redragon K556 | Monitors: Main: ASUS VP249QGR 144Hz, Secondary: Dell E2014h 1600x900

Laptop: Motile M141 - CPU: Ryzen 3 3200U | GPU: Vega 3 igpu | RAM: 8gb DDR4 2400MHz | STORAGE: 120GB SATA M.2 | OS: Windows 10 Home

Link to comment
Share on other sites

Link to post
Share on other sites

Did your Pi have static IP or DHCP configured? Did your subnet change? Define "can't get pi to connect to the router via etherner". Does the link come up?

Skynet: MacBook Pro Late 2016 Space Gray | i7-6820HQ 2.7 GHz | 16 GB LPDDR3 | Radeon Pro 455 2048 MB | 512 GB NVMe SSD | 15" 2880x1800

HAL9000: Intel i5-9600k | Cryorig M9 | 32 GB Corsair Vengeance LPX DDR4 3200 MHz | Gigabyte Z390I AORUS PRO WIFI | MSI GTX 1080 Ti SeaHawk X | 1 TB Samsung 970 Evo Plus + 1 TB Crucial MX500 + 512 GB Samsung 970 Evo Plus | Corsair TX650M | NZXT H210i | LG 34UM95 34" 3440x1440

Hydrogen server: AMD Ryzen 9 3900x | AMD Wraith Prism | 64 GB Crucial Ballistix 3200MHz DDR4 | Asus Prime X570 Pro | Corsair HX1000 | 256 GB Samsung 850 Evo + 1 TB Crucial MX500 + 4x 3 TB + 2 TB WD Red/Seagate/Toshiba  | Fractal Design Define R5 | unRAID 6.8.3

Carbon server: Fujitsu PRIMERGY RX100 S7p | Xeon E3-1230 v2 | 16 GB DDR3 ECC | 60 GB Corsair SSD & 250 GB Samsung 850 Pro | Intel i340-T4 | ESXi 6.5.1

Big Mac cluster: 2x Raspberry Pi 2 Model B | 1x Raspberry Pi 3 Model B | 2x Raspberry Pi 3 Model B+

Link to comment
Share on other sites

Link to post
Share on other sites

Have you tried running sudo raspi-config to see if you aren't able to redo your network settings?

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, jj9987 said:

Did your Pi have static IP or DHCP configured? Did your subnet change?

It has a static ip. DHCP is enabled on router and disabled on pi-hole.

7 minutes ago, jj9987 said:

Define "can't get pi to connect to the router via etherner". Does the link come up?

I ran the ethernet cable from the pi to the router (same as before with old router) and the pi won't connect to the router.

Also what's a subnet?

Main Desktop - CPU: Ryzen 5 5600x  | GPU: GeForce GTX 1070 Founders Edition | RAM: G.SKILL TridentZ RGB 16GB (2 x 8GB) 3200MHz | Motherboard: Gigabyte B450 Aorus M | PSU: EVGA 650 B3 | STORAGE: Boot drive: Crucial MX500 1TB, Secondary drive: WD Blue 1TB hdd | CASE: Phanteks Eclipse P350x | OS: Windows 10 Pro | Keyboard: Redragon K556 | Monitors: Main: ASUS VP249QGR 144Hz, Secondary: Dell E2014h 1600x900

Laptop: Motile M141 - CPU: Ryzen 3 3200U | GPU: Vega 3 igpu | RAM: 8gb DDR4 2400MHz | STORAGE: 120GB SATA M.2 | OS: Windows 10 Home

Link to comment
Share on other sites

Link to post
Share on other sites

13 minutes ago, TrainFan2020 said:

It has a static ip. DHCP is enabled on router and disabled on pi-hole.

I ran the ethernet cable from the pi to the router (same as before with old router) and the pi won't connect to the router.

Also what's a subnet?

How do you know it won't connect to the router? What happens or what does not happen? Do the lights on the Pi ethernet port turn on/start blinking? What is your Pi static IP configured to? What is your router's IP?

 

Subnet (in very simplified and layman terms) is basically your home network. It defines what private IP range is used for your home network. For example 192.168.1.1/24 is the most widely used in home routers. In such case 192.168.1.1 is traditionally (but not always) the gateway/router and /24 indicates the subnet size (254 devices, from 192.168.1.1 to 192.168.1.254).

 

If the Pi IP and router IP do not belong to the same subnet, you run into issues.

Skynet: MacBook Pro Late 2016 Space Gray | i7-6820HQ 2.7 GHz | 16 GB LPDDR3 | Radeon Pro 455 2048 MB | 512 GB NVMe SSD | 15" 2880x1800

HAL9000: Intel i5-9600k | Cryorig M9 | 32 GB Corsair Vengeance LPX DDR4 3200 MHz | Gigabyte Z390I AORUS PRO WIFI | MSI GTX 1080 Ti SeaHawk X | 1 TB Samsung 970 Evo Plus + 1 TB Crucial MX500 + 512 GB Samsung 970 Evo Plus | Corsair TX650M | NZXT H210i | LG 34UM95 34" 3440x1440

Hydrogen server: AMD Ryzen 9 3900x | AMD Wraith Prism | 64 GB Crucial Ballistix 3200MHz DDR4 | Asus Prime X570 Pro | Corsair HX1000 | 256 GB Samsung 850 Evo + 1 TB Crucial MX500 + 4x 3 TB + 2 TB WD Red/Seagate/Toshiba  | Fractal Design Define R5 | unRAID 6.8.3

Carbon server: Fujitsu PRIMERGY RX100 S7p | Xeon E3-1230 v2 | 16 GB DDR3 ECC | 60 GB Corsair SSD & 250 GB Samsung 850 Pro | Intel i340-T4 | ESXi 6.5.1

Big Mac cluster: 2x Raspberry Pi 2 Model B | 1x Raspberry Pi 3 Model B | 2x Raspberry Pi 3 Model B+

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, jj9987 said:

How do you know it won't connect to the router? What happens or what does not happen? Do the lights on the Pi ethernet port turn on/start blinking? What is your Pi static IP configured to? What is your router's IP?

 

Subnet (in very simplified and layman terms) is basically your home network. It defines what private IP range is used for your home network. For example 192.168.1.1/24 is the most widely used in home routers. In such case 192.168.1.1 is traditionally (but not always) the gateway/router and /24 indicates the subnet size (254 devices, from 192.168.1.1 to 192.168.1.254).

 

If the Pi IP and router IP do not belong to the same subnet, you run into issues.

I think it changed from 192.168.1.1 to 192.168.0.1

I'm going to try re configuring the pi-hole's ip address to match the subnet then

Main Desktop - CPU: Ryzen 5 5600x  | GPU: GeForce GTX 1070 Founders Edition | RAM: G.SKILL TridentZ RGB 16GB (2 x 8GB) 3200MHz | Motherboard: Gigabyte B450 Aorus M | PSU: EVGA 650 B3 | STORAGE: Boot drive: Crucial MX500 1TB, Secondary drive: WD Blue 1TB hdd | CASE: Phanteks Eclipse P350x | OS: Windows 10 Pro | Keyboard: Redragon K556 | Monitors: Main: ASUS VP249QGR 144Hz, Secondary: Dell E2014h 1600x900

Laptop: Motile M141 - CPU: Ryzen 3 3200U | GPU: Vega 3 igpu | RAM: 8gb DDR4 2400MHz | STORAGE: 120GB SATA M.2 | OS: Windows 10 Home

Link to comment
Share on other sites

Link to post
Share on other sites

Update: I got it running, just had to run pihole -r to reconfigure the ip address

Main Desktop - CPU: Ryzen 5 5600x  | GPU: GeForce GTX 1070 Founders Edition | RAM: G.SKILL TridentZ RGB 16GB (2 x 8GB) 3200MHz | Motherboard: Gigabyte B450 Aorus M | PSU: EVGA 650 B3 | STORAGE: Boot drive: Crucial MX500 1TB, Secondary drive: WD Blue 1TB hdd | CASE: Phanteks Eclipse P350x | OS: Windows 10 Pro | Keyboard: Redragon K556 | Monitors: Main: ASUS VP249QGR 144Hz, Secondary: Dell E2014h 1600x900

Laptop: Motile M141 - CPU: Ryzen 3 3200U | GPU: Vega 3 igpu | RAM: 8gb DDR4 2400MHz | STORAGE: 120GB SATA M.2 | OS: Windows 10 Home

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×