Hi everyone,
I have a NAS and RPis in my local network. They all have a static lease and I can ping them with only their name. My /etc/hosts is as follows:
127.0.0.1 localhost gemini.lan
255.255.255.255 broadcasthost
::1 localhost gemini.lan
One of my PI is called kiwi:
$ ping kiwi
PING kiwi.lan (192.168.1.215): 56 data bytes
64 bytes from 192.168.1.215: icmp_seq=0 ttl=64 time=0.418 ms
64 bytes from 192.168.1.215: icmp_seq=1 ttl=64 time=0.724 ms
If I try http://kiwi:4000 on my browser this leads to ERR_ADDRESS_UNREACHABLE. If I use http://192.168.1.214:4000 I am getting the same error.
However, my router is named router on 192.1.168.1:
$ ping router
PING router.lan (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.735 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.984 ms
And http://router on the same browser opens the Luci web interface of it. Does anybody know why the router would work but not other servers on the local network? This seems to be some transient issue that I can't seem to find the root cause of. For instance, I never use Safari on this machine and trying to reach kiwi from Safari does work.
Thanks!
Try lookups from the desktop. If they work automatic doh breaks browsing
kiwi.lan might be one?
Thanks but I am not sure what you mean. The pings and the rest of the logs above are all done from my machine (the one that can't access the local servers from my browser).
Here's another from my machine:
$ curl http://kiwi:4000
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover">
<title data-suffix=" · TeslaMate">
....
you can add canary domains to prevent browser skipping local dns. It is browser configuration, well documented for years.
I am trying to follow here. It does not work with the IP address either. And it does work with router (both the name and the IP).
If it works from cmd but not the browser, then it's a browser issue.
You could start by temp disabling secure DNS in your browser, and retesting.
But kiwi seems to resolve to .215:
1 Like
It’s a typo. I meant .215
I’ll do that but, for the record this happens with two different browsers so I am wondering about some cache pollution. Not working with the IP is really odd.
If it isn’t working with the ip address and both the server and the client are on the same subnet, the problem is not caused by the router. That is because these connections happen at L2 (switching) and don’t need any routing.
Are you absolutely certain that the pi is running at that address and that the server is actually running and accepting connections?
Yes. I do realize that IP is L2 but this problem is new and I am just trying to figure things out.
To give you another hopeful example that rule out the PI, I have an AP running on openwrt as well on 192.168.1.2 named ap-kitchen:
It didn't help. However, on Chrome I have a way to select the DNS provider. It was on "OS default (when available)". I switched it to cloudflare.
When I did this http://kiwi returned a different error: DNS_PROBE_FINISHED_NXDOMAIN, which makes sense since it doesn't know about my local aliases. But the IP started working!
It looks a bit mysterious to me I must confess and I don't really understand how IP could be blocked like this.
That would def break local name lookups.
chrome://settings/security disable secure DNS.
Please draw a diagram of your network topology.
Also, on the computer(s) that are experiencing this issue, what is the complete IP address information for those devices?
Finally, let's see the complete configs of all of your OpenWrt devices:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
I got what you asked. I did that and it didn't work. However switching to cloudflare allowed me to connect with IP whereas I couldn't before.
I have a second laptop so I gave that a try and from that one it's all good both firefox and chrome. I am really confused.
what is the complete IP address information for those devices?
How do I get that?
So the second computer works properly, but the first does not? Points to an issue with the first computer.
1 Like
