[Solved] Can only ping per IP but not per hostname in LAN

n-tchen · 2019-03-06 16:46:46

Hi guys,

i got a "new" router (Huawei B890 LTE, DHCP) and provider five days ago and since then I'm unable reach my other devices (a raspberrypi with raspbian and a Thinkpad with primary Win10) per hostname. I have/had my samba shares of my raspberry mounted into Arch and these, of course, aren't working anymore - that's the main point.
But i can reach those two (pi and laptop) per hostname when i switch to Windows (dual boot) and I also can ping my arch machine and the pi from my Win10 laptop. So it seems to be a problem with the Linux-Router combination?

My question is, from where Linux/Arch should get the hostnames of the other devices? From the DNS of the router? And where should they be saved/where can i look them up? Fyi: I testwise added the ip and hostname of my pi into /etc/hosts - then it works like it should, but i shouldn't have to do that manually, do I?

/etc/hosts

# Static table lookup for hostnames.
# See hosts(5) for details.
#192.168.1.5     raspberrypi # added manually after I had the problems
127.0.0.1       localhost.localdomain   localhost
::1             localhost.localdomain   localhost

/etc/resolv.conf

# Generated by resolvconf
nameserver 192.168.1.1

...what's matching to the primary DNS IP of my router. At the old router it was 10.0.0.138, so completely different and I did not changed this manually.

Maybe someone can help me with this because other threads i found couldn't...

Thanks in advance
Markus

PS: The machine was updated two or three days ago, so I'm still on Kernel 4.20.13

Last edited by n-tchen (2019-04-28 11:47:19)

Trilby · 2019-03-06 17:04:19

LAN host name resolution would either be done on the local machine (as you have done in your /etc/hosts) or it would be done in the router. So either your old router managed this by default, or you set up the old router to do it. But in either case, you have a new router, so you need to configure the new router (e.g., configure IPs and names by mac address perhaps).

EDIT: oops, I missed that this is working when you boot into Windows - so I gather the router is doing enough already.

Last edited by Trilby (2019-03-06 17:05:29)

progandy · 2019-03-06 17:57:59

Can you manually resolve the IP with dig?

dig raspberrypi @192.168.1.1

Slithery · 2019-03-06 18:10:13

Trilby wrote:

LAN host name resolution would either be done on the local machine (as you have done in your /etc/hosts) or it would be done in the router. So either your old router managed this by default, or you set up the old router to do it. But in either case, you have a new router, so you need to configure the new router (e.g., configure IPs and names by mac address perhaps).
EDIT: oops, I missed that this is working when you boot into Windows - so I gather the router is doing enough already.

I wouldn't discard the idea so quickly - it's the one that I was going to post

It could be that Windows is picking up addresses via AVAHI (or NETBIOS or something similar). If the old router added client names broadcast as DHCP requests to its DNS forwarder but the new one doesn't this could still explain the change in behaviour.

n-tchen · 2019-03-06 19:25:18

Thanks for all your replys.
@Trilby
The router only has a quite basic gui, so i can't alter files directly. I guess?! But there is a table where all devices are listed with the correct hostnames and IPs

@progandy
I just installed bind-tools and the output of your command is the following:

$ dig raspberrypi @192.168.1.1

; <<>> DiG 9.13.7 <<>> raspberrypi @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;raspberrypi.                   IN      A

;; AUTHORITY SECTION:
.                       2538    IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2019030600 1800 900 604800 86400

;; Query time: 79 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mi Mär 06 20:07:46 CET 2019
;; MSG SIZE  rcvd: 104

But i still can't ping the raspberrypi

Slithery wrote:

It could be that Windows is picking up addresses via AVAHI (or NETBIOS or something similar). If the old router added client names broadcast as DHCP requests to its DNS forwarder but the new one doesn't this could still explain the change in behaviour.

I seems to me that it should be something like that. I'm also unable to ping other devices from my raspberry similar to my Arch machine. The question is, because i probably can't configure the router's behavior, if Arch can "pick" the hostnames like Windows does and solve the problem that way?

Last edited by n-tchen (2019-03-06 19:27:50)

Slithery · 2019-03-06 19:45:37

This may work, I'm an old-school guy that runs proper DNS on my home network

https://wiki.archlinux.org/index.php/Avahi

progandy · 2019-03-06 19:59:33

@progandy
I just installed bind-tools and the output of your command is the following:

If you look at the "Got answer" section, you received "NXDOMAIN" which means the domain was not found. So your new router does not perform name resolution for DHCP hostnames (assuming "raspberrypi" is the hostname of your pi).

seth · 2019-03-06 20:06:05

Windows is gonna use https://wiki.archlinux.org/index.php/Sa … host_names - since you use SMB anyway, this might be a reasonable enough choice.
Clients also send their hostname w/ the dhcp request and routers can build those into a DNS table, but the router must provide more than a dumb DNS forwarder (eg. dd-wrt/openwrt provide dnsmasq)

Assuming your name refers to ducks: did you have an AVM router (FRITZ!Box) before?

n-tchen · 2019-03-07 09:21:04

Yes, the hostname of my pi is raspberrypi and thanks for the explanations! I will read the articles and see what suits my needs.

@seth Yeah, it's refering to duck(lings) and mathematics
No, it was a (actually newer) Huawei HA35-22/AM from the austrian carrier A1 (A1 Hybrid Box), but my Ex took the router with her

n-tchen · 2019-04-28 11:46:56

So, took a bit longer than expected Because I had a some problems on the first attempt with both suggestions (samba and avahi), I let the topic be for a couple of weeks. Last week i tried it again and after I figured out, that Windows 10 blocks pings with stock stettings (solved per Group Policys) and I also had to enable the Netzwerkerkennung (i don't know which term is used in the english windows version, maybe network-detection) the last part of the puzzle was that i had to install the samba package (not only the smbclient, that was unclear for me in the wiki) for the winbind service. With this service started, i now can ping the raspberry and also my windows machines per hostname again.

Thanks once more for your help!

Arch Linux

#1 2019-03-06 16:46:46

[Solved] Can only ping per IP but not per hostname in LAN

#2 2019-03-06 17:04:19

Re: [Solved] Can only ping per IP but not per hostname in LAN

#3 2019-03-06 17:57:59

Re: [Solved] Can only ping per IP but not per hostname in LAN

#4 2019-03-06 18:10:13

Re: [Solved] Can only ping per IP but not per hostname in LAN

#5 2019-03-06 19:25:18

Re: [Solved] Can only ping per IP but not per hostname in LAN

#6 2019-03-06 19:45:37

Re: [Solved] Can only ping per IP but not per hostname in LAN

#7 2019-03-06 19:59:33

Re: [Solved] Can only ping per IP but not per hostname in LAN

#8 2019-03-06 20:06:05

Re: [Solved] Can only ping per IP but not per hostname in LAN

#9 2019-03-07 09:21:04

Re: [Solved] Can only ping per IP but not per hostname in LAN

#10 2019-04-28 11:46:56

Re: [Solved] Can only ping per IP but not per hostname in LAN

Board footer