In the Menu bar at the top of the screen, click settings > Privacy & Security.At the bottom of Safari's settings screen, Select Clear cookies and data or Clear Cookies and Clear Cache.For Safari, from the home screen, Select Settings > Safari.Select the “beginning of time” option and then click Clear Browsing Data.For Chrome, go to the browser toolbar, click More Tools and select Clear Browsing Data.You can follow the instructions below for some popular browsers to clear the cache and try again: NOTE: Some browsers may have cached this page by accident.
The default gateway IP for your router is 192.168.1.1.
If you are using a VPN connection or a customize IP range, type your Gateway IP address on the browser to access your router. If you’d still like to use or, visit the Router login page cannot be displayed. If you are using NETGEAR Business products (any WAC or WAX access points or Orbi Pro), please visit APLogin. 4.Further Troubleshooting for Connecting your Router: 44 even though I was still connected to it from the 192.168.1.4 address. When I switched to PiHole acting as DHCP server it was showing the laptop as having 192.168.1. 4, and I had remotely connected to that machine from my desktop. Maybe this will make sense to those of you more network savvy than I, but one weird thing was while the router was still handling DHCP duties my work laptop was given 192.168.1. PiHole Query Log now shows the specific clients making the request like I wanted. DNS is still set to ‘Get Automatically From ISP’ in the router, but it appears PiHole is still blocking correctly. DHCP disabled in router, and enabled in PiHole. Setting DNS back to the ‘Get Automatically From ISP’ I could turn off DHCP without changing router IP. With DNS manually set to a specific IP it wouldn’t allow me to turn off DHCP duties without changing router IP. I figured out why it wouldn’t let me disable the router as DHCP server without changing the routers IP (I don’t recall the exact error message)… With that said, that brief period where the PiHole was the DHCP server the queries were showing up the way I wanted… even if they weren’t reaching their destination. I ended up pulling power on the modem, and rebooting the router again which ended up fixing the issue with no internet. All the settings I configured were gone… SSID’s, forwarded ports, DNS server, etc. I turned the router off/on and when it finished rebooting it had reset itself (I hadn’t recessed reset button*). And I could no longer access the router at the newly changed 192.168.10.1 address, or it’s previous 192.168.1.1. It then starts handing out IP’s, and is showing all of the connected devices. Router reboots, and then I’m able to reaccess the PiHole again and enabled it as the DHCP server, giving it the new 196.168.10.1 gateway/router IP. 
Before I could disable the router as the DHCP server I had to change it’s gateway IP from 192.168.1.1 to something else, I chose 192.168.10.1. I think I miss understood what you meant and what I’m about to say will confirm that, or not, but I had already set the DNS server in the router to the IP of the PiHole - whose IP was assigned by the router acting as the DHCP server.įast forward to roughly an hour ago, I disabled DHCP on the router and enabled it on the PiHole instead.My router is a Netgear Nighthawk AX4 (RAX35).
0 kommentar(er)
