Issues with Wifi clients (NSwitch and Roomba) #7756
Replies: 10 comments 6 replies
-
|
I wonder if my device use ipv6 now instead of ipv4. I'm not familiar with IPv6.... |
Beta Was this translation helpful? Give feedback.
-
|
And my devices still use 192.168.1.1 (my router's IP) as DNS server instead of using 192.168.1.2 (Pi's IP, running AdGuard Home, DHCP server theoretically...). I guess something is wrong in my settings but I don't understand what. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
my Pi4 is supposed to have a fixed IP address (192.168.1.2). I set that up. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I input 255.255.255.0 for Subnetmask but it auto reverts to "24" ... I don't know what it means (excuse my ignorance) |
Beta Was this translation helpful? Give feedback.
-
|
OK, I made some progress. (2001::1. replaced by 2a04::1) |
Beta Was this translation helpful? Give feedback.
-
|
I don't understand why what I did worked but I did it because all the IPv6 addresses on my devices started with 2a04... |
Beta Was this translation helpful? Give feedback.
-
|
now my devices get an IP from AdGuard but the DNS server is still not the good one... Should be 192.168.1.2 but they use 192.168.1.1 I shouldn't need to manually specify that on each device, right? |
Beta Was this translation helpful? Give feedback.
-
|
after renewing the DHCP lease, some device are now using the good DNS server (192.168.1.2) but others are more stubborn (looking at you NSW)... |
Beta Was this translation helpful? Give feedback.
-
|
OK so the devices that get an IP but cannot resolve DNS names are:
Everything else seems to work OK. 2 PCs, 2 macs, 3 android phones, 1 windows tablet, apple TV, smartTV. Even a connected rice cooker... I don't understand what goes wrong with the Switch and the Roomba, though. ((They probably still try to use 192.168.1.1 (instead of 192.168.1.2) as DNS server...)) EDIT: nope I could confirm Roomba is using 192.168.1.2 for DNS but cannot register on its cloud thing... |
Beta Was this translation helpful? Give feedback.
-
|
On the NSwitch if I specify manually the DNS server and use Google's (8.8.8.8 & 8.8.4.4) then I can reach the internet. If I manually specify 192.168.1.2 (AdGuard on the Pi4) I get the same error message I get when I use "auto" for DNS. Even if AdGuard protection is disabled. weird... I don't know how to run such test on the Roomba though... |
Beta Was this translation helpful? Give feedback.
-
|
yup... roomba can connect to the internet if I give it a static IP and manually input Google's DNS in the connection settings. |
Beta Was this translation helpful? Give feedback.
-
|
so I have the same symptoms on NSwitch and Roomba |
Beta Was this translation helpful? Give feedback.
-
|
I don't understand why I get this issue even when AdGuard is disabled. I would expect that it should have no effect then... |
Beta Was this translation helpful? Give feedback.
-
|
On the NSwitch if I specify manually the DNS server and use the IP of my ISP router (192.168.1.1) then I can reach the internet, even if DHCP server is disabled on the router. If I manually specify 192.168.1.2 (AdGuard on the Pi4, DHCP server enabled) I get the same error message I get when I use "auto" for DNS. Even if AdGuard protection is disabled. Weird... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi :)
I'm a total noob. This is my 1st time with AdGuard and with a Raspberry Pi.
I recently aquired a Raspberry Pi4 and I installed AdGuard Home on it this evening. Since my router won't let me chose the DNS servers I figured I should disable DHCP server on my router and enable DHCP server on AdGuard Home.
my router has the IP 192.168.1.1
the Pi4 has the IP 192.168.1.2 (fixed)
some other clients on the LAN have fixed IPs (192.168.1.15, 19, 21, etc)
most clients on the LAN get their IP from the DHCP server.
When my router was the DHCP server, the pool of IP if would give was from 192.168.1.2 to 192.168.1.254 but all of them were below 50 I believe. At least below 100, for sure.
When I setup the DHCP server in AdGuard Home, I chose the pool of IPs to be from 192.168.1.100 to 192.168.1.200, so I could check if the clients actually change their IP (if they use the new DHCP server). However, I copied the settings so that my clients with fixed IPs keep their current one. I added static leases using the MAC address, the IP (192.168.1.15, 19, 21, etc) and the host names.
After I rebooted my router, I expected that the LAN clients that do NOT have a fixed IP would get a new IP in the range 100-200. but they still get an IP with a lower number (one of them is 7 but most are around 50 now, for some reason). I don't understand who is giving them these IPs.
Some Wifi clients cannot access the internet when connected to the wifi network. Others can but still get an IP that is not between 100 and 200 (basically, my MBP connects to the wifi with the IP 192.168.1.66).
If I go into the admin page of my router, the list of connected devices now has fewer entries and many are "name unavailable" (both LAN and Wireless clients), while some are recognized with their name.
I don't understand what is going on? Is the DHCP server of AdGuard working at all in my network? What did I misconfigured?
Thank you very much in advance for your help and advice.
Best,
-a-
Beta Was this translation helpful? Give feedback.
All reactions